Flow · 6 steps

Send text messages under your own name

Send text messages to customers and suppliers under your own sender ID, and see each one in the same record as your mail.

Anything Manifold can email someone it can also text them. Your texts arrive from a sender ID — up to eleven letters and digits, such as Ridgeline — in place of a number. Name the countries you text: the sender ID is registered in each, and a country that takes no sender IDs (the United States, Canada) is texted from Manifold's own number with your name first.

Services involved

A filled dot is a read; a ring is a call that changes something.

  • Notifications: https://notifications.getmanifold.io

Every call carries Authorization: Bearer $MANIFOLD_TOKEN unless its step says otherwise (getting a token). Run a flow in your sandbox, not your live organization: see Before you start.

1 Name the sender

The name a text from Manifold's number starts with, as it is the name your mail goes out under.

PUT /settings/sender Notifications

Request · application/json
{
  "senderName": "Ridgeline Outdoor",
  "accountsEmail": "accounts@ridgeline-outdoor.example"
}

What the answer holds: the operation's example.

Records notifications.sender-saved.

2 Save the sender ID

The sender ID and the countries you text. The answer says where it stands in each: active, still being registered, or texted from Manifold's number.

PUT /settings/sms Notifications

Request · application/json
{
  "senderId": "Ridgeline",
  "countries": [
    "AU",
    "NZ"
  ]
}

What the answer holds: the operation's example.

Records notifications.sms-sender-saved.

3 Save it again

The same sender ID and countries, in any order, are the sender as it stands: nothing is appended.

PUT /settings/sms Notifications

Request · application/json
{
  "senderId": "Ridgeline",
  "countries": [
    "NZ",
    "AU"
  ]
}

What the answer holds: the operation's example.

Records nothing.

4 Send a test text

To a mobile number in international form. Like an email, it is a fact before the provider is called and another when it answers.

POST /notifications/test Notifications

Request · application/json
{
  "notificationId": "ntf_01a15889-0b42-7e6d-8a5c-2f1b0e9d8c7b",
  "channel": "sms",
  "to": "+61 412 345 678"
}

What the answer holds: the operation's example.

Records notifications.requested, notifications.sent.

5 Read the texts in the log

Texts and mail share one log; narrow it to the sms channel, or to one phone number.

GET /notifications?channel=sms Notifications

What the answer holds: the operation's example.

6 Let the sender ID go

Nothing is texted until another is saved.

DELETE /settings/sms Notifications

What the answer holds: the operation's example.

Records notifications.sms-sender-removed.

What a recorded fact is: Facts and the journal. Why a repeated step changes nothing: Idempotency and retries.