An MSG91 connection uses your own MSG91 account. MSG91 steps send SMS, one-time codes and email from that account, and MSG91 bills it for each one — Bizomate does not resell them.

Who can do this

Workspace Admins and Editors, on any plan — MSG91 is not a premium connection. Viewers see the connection but cannot add or change it.

On MSG91's side, someone who can see the account's auth key — usually the account's owner.

Before you start

  • An MSG91 account with SMS credits.
  • For SMS to Indian numbers, a DLT registration and approved templates — see SMS to India: DLT templates below. Without them, Indian operators do not deliver the message.
  • For email, a sending domain verified in MSG91 Email, and an email template.

Steps

In MSG91, find the auth key:

  1. Sign in to MSG91.
  2. Select your name at the top right, then Authkey.
  3. Copy an existing auth key, or create one and copy it.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Communication, select MSG91. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace MSG91.
  4. Paste the key in Auth key — In MSG91: your name at the top right, then Authkey. It is hidden as you type.
  5. Leave Test the connection before saving ticked. Bizomate asks MSG91 for the account's SMS balance before keeping the key.
  6. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace MSG91” is ready. Every workflow in this workspace can use it."

What happens next

  • MSG91 steps list it under Connection: Send an SMS (Flow), Send an OTP, Verify an OTP and Send an email (MSG91 Email).
  • Test in the connection's panel answers "Reached MSG91" and the balance — for example "Reached MSG91 · 1200 SMS credits".
  • The auth key is stored encrypted and never shown again.

SMS to India: DLT templates

Indian rules (TRAI's DLT system) say every business SMS to an Indian number must come from a registered sender and match a registered template, word for word apart from its variables. Operators drop anything else. This is why the MSG91 SMS and OTP steps take a template id rather than free text.

Once, outside Bizomate:

  1. Register your business as a principal entity on one of the operators' DLT portals (Jio, Airtel, Vodafone Idea, BSNL and others run them). The portal gives you an entity id.
  2. Register a header — the sender id people see, such as CNSLCE.
  3. Register each template: the exact text, with a variable written {#var#} wherever a value changes — for example Dear {#var#}, your order {#var#} has shipped. - Consulace. The portal approves it and gives it a DLT template id.

Then in MSG91:

  1. Add your DLT entity id, header and templates to MSG91 as its panel asks.
  2. Make a Flow for each SMS template, using the approved text with MSG91's own variable names in it — for example ##name## and ##order##. MSG91 shows the Flow's id on its Flow page. That id goes in Flow template id on Send an SMS (Flow), and the names, without the ##, go in its Variables.
  3. For one-time codes, make an OTP template in MSG91 from a DLT-approved OTP template. Its id goes in OTP template id on Send an OTP.

Numbers outside India do not need DLT, but each country has its own sender rules, which MSG91 applies.

Good to know

  • A new auth key. If you delete or change the auth key in MSG91, the connection stops working. In Bizomate, open the connection's panel, select Revoke and Revoke connection, then Reconnect, paste the new key and select Reconnect. With Test the connection before saving ticked, Reconnect tries the key first and changes nothing if MSG91 refuses it.
  • What it costs. MSG91's prices per SMS, OTP and email apply. The test reads the balance of your transactional SMS credits.
  • Email is separate in MSG91. The email step needs MSG91 Email set up — a verified domain and a template — as well as the auth key.

If something goes wrong

What you see Why What to do
"Fill in Auth key." The box is empty. Copy the key from Authkey in MSG91.
MSG91 refused it — "MSG91 refused the auth key: … Nothing was saved." The key is wrong, deleted, or not this account's. MSG91's own words follow. Copy the key again from Authkey in MSG91.
MSG91 refused it — "MSG91 refused: … Check the connection's details on Connections. Nothing was saved." MSG91 turned the key away. Copy the key again. If your MSG91 account limits which addresses may use the key, that limit may be refusing Bizomate.
"The connection has no auth key. Reconnect it on Connections and fill it in." (in a run) The connection's details are incomplete. Revoke it and Reconnect with the key filled in.
"Could not reach MSG91: …" or "MSG91 did not answer within 30 seconds." MSG91 could not be reached. Try again in a few minutes.