MSG91 · Delivery report — When MSG91 reports whether a message was delivered — starts a run each time MSG91 sends a delivery report for a text from your account. Use it to follow up on texts that were not delivered, or to record each one's outcome.
It is an instant trigger. MSG91 only sends reports to an address typed into its own panel, so you paste the trigger's address there once — see How instant triggers work.
Who can do this
Workspace Admins and Editors, on every plan — MSG91 is not a premium connection. The address appears once an Admin or Editor has opened the trigger; Viewers see it after that.
On MSG91's side, someone who can change the account's webhook settings — usually its owner.
Before you start
An MSG91 connection — see Connect MSG91.
Steps
In Bizomate:
Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
Under MSG91, select Delivery report — it reads MSG91 · instant. Or type MSG91 in Search triggers.
In Connection, choose your MSG91 connection — for example Consulace MSG91. The trigger has no other settings.
Under One step in MSG91 — MSG91 sends delivery reports only to an address set in its panel. Copy this into the webhook (delivery report) setting of your MSG91 account, and save. — select Copy beside Webhook address.
A toast says Copied — The address is on your clipboard.
In MSG91:
- Sign in to MSG91 and open the webhook (delivery report) setting of your account.
- Paste the address, and save.
Back in Bizomate:
- The panel reads Waiting for the first event — Send a text through MSG91; its report appears here when MSG91 has it.
- Send a text — with MSG91 · Send an SMS (Flow) and Run this step, say. When MSG91 has the report, the panel reads Listening — instant — Last event 10:45 · Delivery report · ….
- On Output, select Use the last event. Test run starts with that report.
- Add the steps, test, then Publish.
You can paste the address and test before publishing: reports arrive and show on the panel, but start runs only once the workflow is published and switched on.
What the trigger gives
Each report is one item, with MSG91's own fields, as MSG91 sent them. Which fields there are depends on your MSG91 account and the kind of message; select Use the last event and read Output to see yours. The run's name is taken from the report's status (or desc, or report_status) and its number (or mobile, or mobiles) — Delivery report · Delivered · 919800000000.
Use the fields in later steps as {{ trigger.status }} and so on, by the names on Output.
What happens next
- Each report starts one run of the live version, in Production. When MSG91 sends several reports in one call, each is its own run.
- The address stays the same across publishes, so MSG91 is set up once.
- Changing to another trigger and publishing, or deleting the workflow, retires the address: MSG91's calls to it are answered No workflow listens here. Remove it from MSG91 too.
Good to know
- MSG91 does not sign its reports. The 48-character code in the address is the only key — anyone who has the address can send to it. Keep it where MSG91 keeps it.
- Reports come when MSG91 has them. Some take minutes, depending on the operator.
- MSG91 takes one delivery-report address. If something else already used it, that stops when you paste Bizomate's.
- Each workflow has its own address, and MSG91 sends to one. Only the workflow whose address is in MSG91 hears the reports.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| No One step in MSG91 box and no address | The trigger was opened by a Viewer before anyone who can edit. | Ask an Admin or Editor to open the trigger once. |
| Waiting for the first event stays after a text was delivered | The address was not saved in MSG91, or was pasted with a piece missing. | Copy it again, paste it in MSG91, and save. |
| Nothing has arrived yet — make one happen in MSG91, then try again. on Output | No report has reached the trigger yet. | Send a text and wait for the report. |
| Reports show on the panel, but no run starts | The workflow is not published, or is switched off. | Publish it, and switch it on. |