Built-in · Messaging and email

Twilio, in every client’s workflows.

Texts from the client’s own number: the instant reply, the owner’s alert, the reminder, with the client’s own Twilio account.

Do it in Twilio

A step of its own, sent through the client’s Twilio account.

Send a textTexts from the client’s own number: the instant reply, the owner’s alert, the reminder

On the client’s page in Thrum: Add credential, type Twilio (SMS).

The client’s Account SID, auth token and the number to send from, from the Twilio console.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

When Twilio stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Twilio and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Get early access and you’ll be among the first in. Early members get a launch perk.