Before you begin
- The
reliantCLI, v1.21 or later, signed in (Sign in and tokens), and a Reliant project for the repository the workflow lives in. - A Twilio account connected under Settings → Integrations with its Account SID and Auth Token, and a number that can receive SMS, or a WhatsApp sender (Connect your Twilio account).
- In an organization with other members: an organization AI account that can run the
fastmodel.
1
Write the workflow
.reliant/workflows/text-answer.yaml
inputs, so the nodes never read trigger.payload. The reply swaps them: to is whoever texted and from is the number or WhatsApp sender that received it. For WhatsApp both keep their whatsapp: prefix, so the answer goes back over WhatsApp. Replace faq with your own answers; it is an input, so you can also set it when you enable the workflow.To listen to one number only, add match: { to: "+15559870000" } under integration:. A WhatsApp sender is matched as whatsapp:+15559870000.2
Test it with scenarios
.reliant/workflows/text-answer/scenarios/whatsapp_reply_keeps_the_prefix.yaml
terminal
reliant workflow lint reports 0 lint error(s), 0 warning(s).3
Enable it with no machine
Commit the workflow, then enable it. In the app: Workflows → Library → text-answer → Enable, with Runs on set to No machine. From a terminal:It listens through your default Twilio connection;
terminal
--connection twilio=<connection-id> picks another (reliant integrations list --integration twilio prints the ids).4
Point your number at Reliant
Twilio sends a number’s incoming messages wherever that number says. Copy the trigger’s Webhook URL from the app (
https://<your Reliant host>/integrations/twilio/events). In the Twilio Console, open the number under Phone Numbers → Manage → Active numbers and set A message comes in to Webhook, that URL, HTTP POST. For WhatsApp, set the same URL on the sandbox or your approved sender (Point your numbers at Reliant).5
Text it and verify
Text the number “Are you open on Saturday?”. Each message is a firing:The newest row should say
terminal
launched with a chat ID, and your phone should get the answer from the same number. The run’s last message reads Replied to <your number>: <answer>.What this does not do
- It doesn’t know who is texting. Twilio’s signature proves Twilio delivered the message, not who sent it, and caller ID can be spoofed. Give this agent only public answers, and never tools or integrations that act on someone’s account.
- It doesn’t remember the conversation. Each message is a separate run that sees only that text.
- It doesn’t reach WhatsApp users after 24 hours. WhatsApp allows free-form replies only within 24 hours of the person’s last message. This workflow always replies right after one, but a later message from it needs an approved template (
content_sid). - In an organization with other members, runs spend only the organization’s AI accounts. Without one that can serve the model, no answer is sent.
Troubleshooting
Texts start no run
Texts start no run
The number’s A message comes in webhook must be the trigger’s URL, set to HTTP POST, and the Twilio connection’s Auth Token must be current: a connection with a rotated token receives nothing until you reconnect it.
Twilio error 21610
Twilio error 21610
The person replied STOP to your number, so Twilio refuses anything you send them. The run ends at
failed with the error.Twilio error 63015 or 63016
Twilio error 63015 or 63016
63015: the recipient has not joined your WhatsApp Sandbox. 63016: the reply fell outside WhatsApp’s 24-hour window and needs a template.
Next steps
Triage Gmail with an agent
The same pattern for incoming email.
Build a Slack bot agent
Answer questions in Slack threads with web research.
Twilio integration
Actions, error codes, payload fields and how messages are routed.
How automations fire
Event dedupe, filters, funding and no-machine runs.