Incoming Twilio texts posted to Slack
Every hour, Leta posts the texts people sent to your Twilio number to a Slack channel, with STOP opt-outs grouped first.
Combine Twilio + Slack and move texts and calls into channels where your team already talks. Just ask Letaido's AI agent and watch it do the work.
Use this Twilio Slack integration to post texts, missed calls and SMS delivery reports, and look up a number.
Every hour, Leta posts the texts people sent to your Twilio number to a Slack channel, with STOP opt-outs grouped first.
Every hour at 15 past, Leta posts last hour's finished calls to your Twilio number that nobody picked up, with caller, time and status.
Every morning, post yesterday's Twilio SMS results to Slack: outbound SMS by status, errors by code, STOP replies and the account's SMS spend.
Mention @Letaido with a phone number and it replies in the thread with that number's texts created in the past 7 days and their status.
Twilio's SMS-to-Slack tutorial forwards each text to Slack. Leta does the jobs that need a summary.
| Option | Texts posted in Slack | Missed calls in Slack | Look up a number from Slack | Daily SMS delivery report | Posts each text the moment it arrives |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Twilio's SMS-to-Slack Studio tutorial | Yes | No | No | No | Yes |
| Zapier, n8n and other recipe tools | Yes | Partly | Partly | Partly | Partly |
| Option | How a run begins | Good at | Keep in mind |
|---|---|---|---|
| Letaido AI agent | A set time, such as every hour or every morning, a mention of @Letaido in Slack, or a request in chat | Grouping the hour's texts with opt-outs first, posting calls nobody picked up, a daily SMS delivery report with error codes, and answering questions about one number in a thread | Twilio has no event trigger in Letaido, so texts and calls are posted on a schedule, not the moment they arrive. Replies typed in Slack are not sent back as texts. The missed call check runs 15 minutes past each hour and skips calls still ringing then; they are not checked again |
| Twilio's SMS-to-Slack Studio tutorial | A text arriving at your Twilio number | Posting each incoming text to one Slack channel as it arrives, using a Studio Flow and a Slack incoming webhook | You build the Flow, create the Slack webhook and write the message payload yourself. As written, the tutorial posts each text as its own Slack message, with no grouping or summary |
| Zapier, n8n and other recipe tools | A new Twilio text, a finished Twilio call or a new Slack message starts a recipe | Forwarding Twilio texts to a Slack channel or DM, posting new Twilio calls, and sending a text when a Slack message is posted. Other Twilio data needs raw API calls (Zapier's API Request action, n8n's HTTP Request node) | Zapier checks for new Twilio texts every 15 minutes on its lowest plan. A simple forwarding recipe posts each text or call as it comes; filtering missed calls, looking up one number or summing up a day needs API calls plus extra filter and count steps you build |
A job can start when someone mentions @Letaido in Slack, like “Check a number's texts from Slack”.
Saved as an automation, like these jobs: every hour, every hour at 15 past or every day at 9am.
Type it once in chat.
Allow all read operations once per app; approve each kind of write once.
Lookup phone number · List available countries · Create application · Delete usage trigger
Make file public · Pin message · Find user by email · Set channel topic
Yes. Twilio's SMS-to-Slack tutorial posts each incoming text to Slack through a Studio Flow and a Slack webhook you set up. With Letaido, Leta posts the texts sent to your Twilio number every hour, with opt-outs like STOP grouped at the top, and a daily SMS delivery report with error codes.
Paste a Twilio API key into Letaido and create the Slack app from Letaido's manifest. Invite the Letaido bot to the channels it should post in, then describe the job in chat, or paste a prompt from a job on this page.
No. Twilio has no event trigger in Letaido, so texts are posted every hour and missed calls every hour at 15 past. Each run covers the previous full clock hour, so back-to-back scheduled runs never overlap. The missed call job only judges calls already finished at its check: a call still ringing or in progress then is skipped and not checked again. An hour with nothing new posts nothing.
Leta replies in the thread with the texts with that number created in the past 7 days, including any that failed before sending, with their status and what any error code means.
Not through these jobs. Replies typed in Slack are not sent back as texts. Reply from your usual texting tool, or ask Leta in chat to send a text.
No. Twilio is only read in these jobs, so they send no texts and place no calls. The only write is the Slack post.
Yes. A simple Zapier forwarding recipe posts each Twilio text or call to Slack as it comes, and Zapier checks for new Twilio texts every 15 minutes on its lowest plan. Lookups and daily reports there need Twilio API calls plus extra filter and count steps. Leta groups the hour's texts, works out which calls nobody picked up, sums up a day of delivery results and answers questions about one number in a thread.
Connect Twilio and Slack, then ask for a job like "Post new texts to our Twilio number in Slack every hour". Leta gets it done on your schedule, or the moment you ask.
Get Letaido