Integrations
One integration, and it reaches almost everything.
Rather than a short list of native connectors, we ship a Zapier app that is live in the Zapier directory. That puts your texting one step away from the 9,000+ tools Zapier already supports, without waiting for us to build a connector for yours.
Being straight about the trade-off: a native integration is usually tidier, and a Zapier step is one more moving part that needs a Zapier account. What you get instead is coverage.
What it can start and do
Triggers, to start a Zap
-
New incoming message
A contact texts you back.
-
New contact
A contact is added to your organization.
-
New subscriber
A contact opts in to your messages.
-
New opt-out
A contact opts out, by STOP, in the dashboard, or through the API.
Actions, to do something here
-
Send SMS
Texts any number, creating the contact if it does not exist yet.
-
Send broadcast to group
Sends a campaign to a whole group, now or at a scheduled time.
-
Add contact to group
Adds a contact to a group or keyword list, creating it if new.
-
Remove contact from group
Takes a contact out of a group or keyword list.
-
Opt-out a contact
Marks a contact opted out so they stop receiving messages.
Things people actually wire up
-
Text every new form submission
A form tool (Typeform, Google Forms, Jotform) receives a submission, then Send SMS delivers a confirmation.
-
Add new customers to a group automatically
A new row in Google Sheets, or a new customer in your CRM or store, then Add contact to group.
-
Keep your CRM in step with opt-outs
New opt-out fires, then your CRM marks the record so nobody texts or emails them again by mistake.
-
Turn replies into tickets
New incoming message fires, then your help desk (Zendesk, Freshdesk, Help Scout) opens a ticket.
-
Announce a new booking or order
A booking or order lands in your system, then Send broadcast to group tells the relevant list.
-
Log every new subscriber
New subscriber fires, then a row is appended to a Google Sheet or Airtable base for reporting.
Worth knowing before you build one
A Zap that texts people still needs their consent, and an automation makes it easy to forget that. If a Zap adds contacts to a group from a source that did not ask for texts, you have built a compliance problem that runs on a schedule. See the compliance guide.
Messages sent through a Zap draw credits exactly like messages sent from the dashboard, so a loop that fires more often than you expected costs money. Test with a small group first. 100 free credits are enough to prove a Zap works.