MSG91 · Send an SMS (Flow) — Sends an SMS from a DLT-approved Flow template — sends a text through your own MSG91 account. The words come from a Flow template held in MSG91; the step fills in its variables. MSG91 bills the account for each message.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the step's settings but cannot change them.

Before you start

  • An MSG91 connection in this workspace — see Connect MSG91.
  • A Flow in MSG91 for the message. For Indian numbers, its text must be a DLT-approved template — see SMS to India: DLT templates in Connect MSG91.

Steps

  1. Select + where the text should be sent. In the step picker, open Apps, select MSG91, then Send an SMS (Flow). Or search MSG91.
  2. In Connection, choose your MSG91 connection. If it is the only one, it is already chosen.
  3. In Flow template id, paste the Flow's id from MSG91 — Indian SMS needs a DLT-registered template; MSG91 holds it. The id is on MSG91's Flow page.
  4. In Mobile numbers, the number to send to — With the country code. Separate several with commas. Spaces, hyphens and a + are taken off, so +91 98765-43210 goes as 919876543210 (an example number). Or drag in a number from an earlier step.
  5. Under Variables, select Add a field for each of the template's variables. Type its name as the Flow uses it, without the ## — for example name — and in Value what goes in it, such as Rohan or a value from an earlier step. The template's variables and their values, the same for every number.
  6. Select Run this step to send a test.

Output

Field What it is
requestId MSG91's id for the request. Look the messages up with it in MSG91's reports.
type MSG91's answer — success. When MSG91 refuses, the step fails with its words instead.
recipients How many numbers it was sent to.

Later steps read it as, for example, {{ steps.send_an_sms_flow.requestId }}.

Good to know

  • The step succeeds when MSG91 accepts the request, not when the phone receives it. Delivery is in MSG91's reports.
  • Every number gets the same variables. To send each person their own values, give one number per item — the step runs once per item.
  • Runs once per item. Ten items send ten requests.
  • The text cannot be changed here. It is the Flow's text in MSG91, and for India it must match the approved DLT template, apart from its variables.
  • Links are sent as written. MSG91's short links are switched off.

If something goes wrong

What you see Why What to do
MSG91 refused: … naming the template Flow template id is wrong, or not this account's. Copy the id again from MSG91's Flow page.
The step succeeds but nobody receives the text For an Indian number: the template, header or entity is not DLT-approved, or the text does not match the approved template. Check the Flow and its DLT details in MSG91, and the delivery report there.
Flow template id is empty when the step ran — an earlier step may not have given the value it names. Flow template id came out empty. Fill it in, or check the value it reads.
Mobile numbers is empty when the step ran — … The number came out empty. Check the value it reads.
MSG91 refused: … Check the connection's details on Connections. The auth key was changed or deleted in MSG91. Revoke the connection and reconnect it with the new key.
Could not reach MSG91: … or MSG91 did not answer within 30 seconds. MSG91 could not be reached. Set If this step fails to try again, or run it later.