Skip to main content

Send SMS through Twilio

Send updates, follow-ups, campaign messages, and workflow SMS through your own Twilio Programmable Messaging account — a supported provider under the SMS integration. Adding the account is two phases — Add (enter credentials, save as a Draft) and Verify (Brixi calls Twilio to confirm the credentials are valid and the account flips to Verified).

Entry pointAutomation → Integrations

Article summaryDetails
RequiresA Twilio account with Account SID, Auth Token, and at least one Twilio phone number or Messaging Service.
Where to goAutomation → Integrations → SMS → Manage → + Add account.
Provider typeProgrammable Messaging (REST API).

Who Can Do This​

  • Account admins add and verify the Twilio account.
  • Growth operators and marketing managers use the verified account inside SMS campaigns and workflow SMS actions.
  • Sales managers read replies and delivery outcomes once messages are sent.

What You Need from Twilio​

Sign in to the Twilio Console and have these four pieces ready:

WhatWhere in the Twilio ConsoleWhat it looks like
Account SIDConsole home → Account InfoAC followed by 32 hex characters
Auth TokenConsole home → Account Info → Show32 hex characters (treat as a password)
From number (or Messaging Service SID)Phone Numbers → Manage → Active numbers, or Messaging → ServicesA phone number with country code (e.g., +1877…) or a Messaging Service SID starting with MG
Base URL (default)n/a — Twilio's API endpointhttps://api.twilio.com/

You also need:

  • The DLT Entity ID issued by your DLT registrar if you send SMS to India and your Twilio sub-account is registered for DLT. Most Twilio accounts outside India can leave this blank.
  • A modern browser signed in to Brixi as an admin user with access to Automation → Integrations.
The Auth Token is a secret.

Treat it like a password — never paste it into chat, never store it in plain text outside Brixi or Twilio's console. If it's ever exposed, rotate it in Twilio first, then update the value here.

Add the Twilio Account​

  1. Open Automation → Integrations. On the Communication tab find the SMS card and turn its toggle on (or confirm it's already on), then click Manage.
  2. The SMS Accounts page opens, showing a stat row (Connected / Verified / Awaiting action) and one card per existing provider account. Click + Add account in the top-right.
  3. The Add SMS Account dialog opens. Pick Twilio in the Provider dropdown — the default form fields shift to Twilio's required ones.
  4. Fill the form (see Field Reference below). Sender ID values shown in the recording are masked for privacy — yours will look like a phone number or Messaging Service SID.
  5. Click Save account. An SMS Account added successfully toast appears, the dialog closes, and the new Twilio card shows on the SMS Accounts page with a grey Draft badge. The stat row updates — Connected goes up by one, Awaiting action goes up by one. The new card has both an Edit and a Verify button.

Add SMS Account dialog for Twilio: fill Provider = Twilio, Sender ID (phone number / messaging service SID), Client ID (Account SID), API Key / Auth Token, Base URL, and optional DLT Entity ID. Sender ID + Client ID values masked.

Field Reference​

The Twilio form has four required fields (*) and three optional fields:

FieldRequiredTwilio value to paste
Provider✓Pick Twilio.
Display Name—A label for your team — e.g., Marketing SMS, India promo. Shows up in the campaign sender picker.
Sender ID✓Your active From number in E.164 format (+1…, +91…) or a Twilio Messaging Service SID starting with MG.
DLT Entity ID—Only for India sub-accounts — the Principal Entity ID registered on the DLT portal. Leave empty otherwise.
Client ID✓The Twilio Account SID (AC… followed by 32 hex chars). The hint reads Account SID (Twilio) / Sender id (MSG91).
API Key / Auth Token✓The Twilio Auth Token from the Twilio Console. The field is masked (••••) with an eye-toggle to reveal it briefly.
Base URL—Leave the pre-filled https://api.twilio.com/ unless Twilio Support has given you a region-specific endpoint. Must start with http:// or https://.

Pick a Display Name that signals the use case, not the provider — e.g., India transactional rather than Twilio 1. The campaign sender picker shows the Display Name, not the SID, so the team that picks it later doesn't need to know which provider is underneath.

Verify the Twilio Account​

A Twilio account in Draft status is not yet usable — campaigns and workflows skip Draft accounts. Verification calls Twilio with the credentials you saved and flips the account to Verified.

  1. On the Twilio card in SMS Accounts, click Verify.
  2. A Verification process started toast appears at the top of the page.
  3. Brixi calls Twilio's GET /Accounts/{AccountSid}.json with your Auth Token. On success the card refreshes to Verified (green badge), the Verify button disappears (only Edit remains), the stat row shifts (Verified up by one, Awaiting action down by one).
  4. On failure the card stays in Draft and the badge changes to Failed. See Common Issues for what to fix.

Twilio card flipping from Draft → Verify pressed → Verification process started toast → Verified badge.

Verification typically completes in under five seconds. If the toast appears but the card doesn't move within 30 seconds, refresh the page — the card was likely updated server-side but the UI hasn't re-fetched.

What You Can Do Once Verified​

A Verified Twilio account is immediately usable from:

  • SMS campaigns — the verified account shows up in the sender picker on Setup → SMS sender. Campaigns can send to any audience type (Contact List, Dynamic Segment, File Upload).
  • Workflow SMS actions — under Automation → Workflows, every SMS action lists the verified account as a sender option.
  • One-off SMS from a contact page (where SMS is enabled for the workspace).
  • Reminders and follow-up tasks that send an SMS to the contact.

Every send is billed to the underlying Twilio account — Brixi is a passthrough. Open the Twilio Console for the usage / billing breakdown.

Edit or Remove a Twilio Account​

  • Edit — click Edit on the Twilio card. The same dialog re-opens with the current values. Update any field (e.g., rotate the Auth Token after rotating it in Twilio first), then Save account. Changes to the Auth Token automatically flip the card back to Draft — re-run Verify.
  • Remove — there is no per-card delete button on the SMS Accounts page in this release. Disable the SMS card from Integrations to stop using every connected SMS account at once, or open a support request to remove a single account.
Don't delete the Twilio number / Messaging Service in Twilio while the account is verified in Brixi.

Deleted numbers cause sends to fail silently for the next send window — always disconnect in Brixi (Edit → blank the Sender ID, Save) or swap to a new From number first.

Common Issues​

IssueWhat to check
+ Add account button missingCheck you're an admin and that the SMS integration card is toggled on under Communication.
Provider dropdown doesn't show TwilioReload the dialog — the provider list loads after the dialog opens. If it still doesn't show, contact support.
Save account stays disabledOne of the four required fields (Provider, Sender ID, Client ID, API Key / Auth Token) is empty.
Verify flips the card to FailedThe Account SID + Auth Token pair is wrong, or the Twilio account is suspended. Sign in to the Twilio Console, copy them fresh, Edit the Brixi card, save, and re-Verify.
Verify returns Failed: Invalid From numberThe Sender ID isn't a number on the same Twilio account, or the number is in Twilio Trial mode and the recipient is unverified. Use a number you own in this account, or verify the recipient in Twilio for trial sends.
Verify returns Failed: Base URLBase URL must start with http:// or https://. Use https://api.twilio.com/ unless Twilio told you otherwise.
Verify works but campaigns still skip the accountWorkflow / campaign caches refresh every few seconds. Wait a minute, then reload the campaign creator.
Twilio sends from the wrong numberTwilio routes by Messaging Service SID when one is set on the account — clear the SID in Twilio if you want the From number to control routing.
DLT rejected (India)Add the DLT Entity ID in the Twilio card, re-Verify, and make sure each template you'll send has a matching DLT Template ID registered with the carrier.
Auth Token leaked / exposedRotate it in Twilio first, then Edit the Brixi card to the new value, save, and re-Verify. Old workflows will resume automatically once verified.

Adding and verifying Twilio accounts is admin-only, so if + Add account or the SMS card isn't visible, ask your admin to check your role first. Credential failures (a Failed badge after Verify) are almost always solved on the Twilio side — copy the Account SID and Auth Token fresh from the Twilio Console before raising anything.

Contact Brixi support when verification fails with credentials you've confirmed in the Console, or when you need a single Twilio account removed from SMS Accounts (there's no per-card delete in this release). Include the account's Display Name and the exact Failed message shown on the card.

Related articlesSMS integration overviewCommunication integrationsCampaigns
Was this article helpful?If something is unclear or out of date, email support@brixi.ai with the article title — or see Getting Help for what to check first.