How instant triggers work

Triggers · updated 1 October · 9 min read

An instant trigger starts a run the moment something happens in another service — a Telegram message, a text to a Twilio number, a SendGrid email bounce — because that service calls Bizomate straight away. Other app triggers, such as Email (IMAP) · New email, instead check the service on a schedule. This article explains the difference, what the trigger's panel shows, and how to test with a real event.

Who can do this

Workspace Admins and Editors set up instant triggers and publish them, on every plan. Viewers can see a trigger's status, but not Copy an address that has not been made yet, Reconnect or Use the last event.

Instant, or checked every 5 or 15 minutes

	Instant triggers	Triggers that check
Which	Telegram · New message, New button press · Twilio · New SMS received, Message status changed · MSG91 · Delivery report · SendGrid · Email event · Brevo · Email event, New contact · Mailchimp · New subscriber, Unsubscribed, Profile updated	Email (IMAP) · New email · Google Sheets · New row · Google Calendar · New or updated event
When a run starts	Within seconds of the event	At the next check — every 5 minutes on paid plans, every 15 on Free
In the trigger picker	The app's group, marked · instant — Telegram · instant	The app's group, without the mark
What the panel shows	Listening — instant, or one of the states below	Checking every 5 minutes — see When an app trigger stops checking

How the service finds Bizomate

Each instant trigger has its own web address, which the service calls. It reaches the service in one of two ways.

Bizomate sets it up for you — Telegram, Twilio, Brevo and Mailchimp. Publishing the workflow gives the address to the service through its API: Telegram's bot, a Twilio number or messaging service, a Brevo webhook, a Mailchimp audience webhook. You paste nothing.
You paste it into the service — MSG91 and SendGrid. These services only take an address typed into their own settings. The address is made the first time an Admin or Editor opens the trigger, so you can paste it before publishing.

The articles for each service give the steps on both sides:

Steps

Read what the trigger is doing:

Open the workflow in the designer and select the trigger.
On Settings, below the trigger's fields, read its state:
- One step in SendGrid (or MSG91) — what to do in the service, the Webhook address, and Copy. Only for the services you paste into.
- Publishing sets this up in Telegram; unpublishing takes it away. It starts with what happens after that. — the workflow has not been published with this trigger yet, so nothing is set up in the service.
- Waiting for the first event — the address is in place and nothing has arrived yet. The line under it says how to make one happen — Send the bot a message in Telegram; it appears here within seconds.
- Listening — instant — Last event 10:45 · New message · Order NW-20417 is ready — the time of the latest event, in your time zone, and what it was.
- Not listening — Telegram would not take Bizomate's address: … Fix it, then publish again. — the service refused when publishing tried to set it up. Its own words follow the colon. Admins and Editors see Reconnect beside it.
Leave the panel open to watch for an event. It looks again every 10 seconds.

Test with a real event:

Make the event happen in the service — send the bot a message, text the number, send an email.
Wait until the panel shows Listening — instant with that event.
Open the Output tab. Under Test with a real one — A trigger the app calls has nothing to test with until the first event arrives. Use the last one, and Test run starts with it. — select Use the last event. The button reads Fetching.

A toast says Sample fetched — Test run starts with it. Unpin it on Output to test with something else. The event is now the trigger's pinned output.
Select Test run. The run starts with that event, and later steps can use its fields — see Using what earlier steps found.
To test with a newer event later, unpin the output on Output, make another event happen, and select Use the last event again. See Pin a step's output.

What happens next

Each event starts one run, of the live version, in Production. The run is named after the event — New SMS · +919800000000, delivered · rohan@consulace.com.
Runs count in the month's allowance, like runs from any other trigger.
Several events in one call — SendGrid and MSG91 send them in batches — start one run each.
An event the trigger's filters leave out — another chat, another status — starts nothing and is not shown as the last event.

While a workflow is not running

Switched off, or in an archived workspace: the service still calls Bizomate, and each event still shows on the panel as the last event, but no run starts. Events are not kept for later — switching the workflow back on starts runs only for events from then on.
Not published yet: for Telegram, Twilio, Brevo and Mailchimp nothing is set up in the service, so nothing arrives. For MSG91 and SendGrid, once you have pasted the address, events arrive and show on the panel — so you can Use the last event and test before you publish — but they start no runs.
Changing the trigger — another chat filter, another number, another audience — and publishing takes away what was set up for the old settings and sets up the new.
Changing to another kind of trigger and publishing, or deleting the workflow, takes the address away from the service where Bizomate set it up. A pasted address then answers No workflow listens here.; remove it from MSG91 or SendGrid too.

Good to know

There is no unpublish. The panel says unpublishing takes it away; in practice, switching a workflow off does not take the address away from the service. To stop a service calling Bizomate, change the workflow to another trigger and publish, or delete the workflow.
Publishing again with the same trigger settings does not set the address up again. If someone changes it in the service afterwards — another address on a Twilio number, another webhook on the Telegram bot — Bizomate keeps waiting. See the table below.
One bot, one number, one messaging service. Telegram takes one address per bot, and Twilio one per number or messaging service. Every workflow in the workspace that uses the same one on the same connection shares a single address, and each event reaches all of them; each keeps only what its own settings ask for. When the first of them goes, the address moves to the next; with the last, it is taken away.
Up to 120 calls a minute reach one address; more are answered 429. A call may bring up to 256 KB.
How a call is proved to be from the service: Telegram sends a secret header that only Bizomate and Telegram know; Twilio signs each call with your Auth Token; SendGrid signs each batch when you give the trigger its verification key. MSG91, Brevo and Mailchimp do not sign: the 48-character code in the address is the secret. A call whose signature does not match is answered 401 — The signature does not match. — and starts nothing.

If something goes wrong

What you see	Why	What to do
Not listening — … would not take Bizomate's address: … Fix it, then publish again.	The service refused when publishing tried to set up the address. The service's own words follow.	Fix what it says — most often Reconnect the connection — then publish again. Publishing tries again whenever the last try failed.
Not listening — … would not take Bizomate's address: No connection is chosen for this step. Fix it, then publish again.	The trigger has no connection.	Choose one in Connection, then publish.
Waiting for the first event stays after you made one happen	The event went somewhere else, a filter left it out, or (for a pasted address) it was pasted wrongly.	Check the trigger's filters, and that the address in the service is the one on the panel.
Nothing has arrived yet — make one happen in Telegram, then try again. on Output	No event has reached the trigger yet.	Make one happen, wait for Listening — instant, then Use the last event.
The service was pointed elsewhere after publishing, and nothing arrives	Bizomate sets the address up only when the trigger's settings change, or the last try failed.	Change one of the trigger's settings and publish, then change it back and publish again.
A run did not start for an event the panel shows	The workflow is switched off, or its workspace is archived.	Switch it on — see Switch a workflow on or off. The missed event does not run later.

Was this helpful?

Still stuck? Ask us.

The assistant answers from these articles, and hands you to a person when one is free. Support hours are 9:00 to 19:00 IST, Monday to Friday; outside them, leave a message and we reply by email.

Chat with us