The SMS integration (via AllMySMS) adds a mobile channel to your pipelines, in both directions: send an SMS (notification, code, follow-up) and receive inbound replies (MO) as well as delivery receipts (DLR).
What you can do with it
- Send an SMS with automatic number normalization to E.164 format and segment counting (GSM-7 / UCS-2).
- Receive inbound replies and delivery receipts to track deliverability.
- Check the balance of your account's SMS credits.
Tools and nodes
- Write tool:
allmysms.send_sms. - Read tool:
allmysms.check_credits. allmysms_outboundnode — send with an exactly-once guarantee (no double send on retry).allmysms_inboundreceiver — reception of inbound messages (MO) and delivery receipts (DLR), with tolerant parsing and deduplication.
Connection (BYO)
- Settings → Services → AllMySMS, Accounts tab.
- Enter your AllMySMS login and API key.
- Point the AllMySMS callback URL to the
allmysms_inboundreceiver (secured by a secret in a parameter). - Credentials stored server-side, never shown again, and scoped to your organization.
Strict BYO connector: you pay for your SMS directly to AllMySMS, with no betool margin. Segment counting saves you from surprises on long or accented messages.
SMS during a call
On the telephony channel, an agent can send an SMS to the person on the call during the call (a link, an address, a summary) with allmysms.send_sms: the recipient is then locked to the caller's number, and sending is refused if that number is withheld.
Already using Brevo? Its SMS sending nodes and its reply receiver are described in CRM, marketing & productivity.
Use cases
- Appointment reminder — a scheduled pipeline sends a reminder SMS a few minutes before the time.
- Two-way confirmation — send a confirmation request, and the inbound reply automatically resumes the pipeline.