How do I connect Tuco to Slack?

In the Tuco app, open Integrations, choose the Slack tab, click Add to Slack, approve the app for your Slack workspace, and pick the channel where lead conversations should appear. New conversations then show up there as threads.

When I reply in Slack, which number does the lead see?

The same line the lead has been talking to. Tuco sends your Slack reply from that conversation's line, so the lead never sees a new number.

How long does Tuco keep webhook deliveries?

30 days. Each delivery stores the exact body that was sent, the request headers (with secrets redacted), your endpoint's response and every attempt.

Can a webhook event arrive twice?

Each event fires once per webhook. If your endpoint does not answer 2xx within 10 seconds, Tuco retries once after 5 seconds with the same X-Tuco-Delivery-Id, so you can drop the retry if you already processed the first attempt. A manual replay carries X-Tuco-Replay: true and a new delivery id.

New on Tuco: Reply to Leads From Slack, and Webhooks You Can See and Replay

Lead conversations now show up as Slack threads you can reply from, and every webhook delivery is logged for 30 days with one-click replay and test events for every type.

October 16, 20263 min read

Summary

In October 2026 Tuco AI shipped two updates. Tuco for Slack posts every lead conversation into a Slack channel as its own thread: replying in the thread texts the lead from the same line they have been talking to, inbound photos, files and voice notes land in the thread, AI drafts can be sent or edited there, and /tuco new starts a new conversation. Webhooks gained a 30-day delivery log that shows the exact request Tuco sent and the endpoint's response, one-click replay of any delivery, realistic test events for every event type (including photos, PDFs, voice notes, P2P SMS and failures), edit-in-place with secret rotation, and a new call.recording.ready event. Every event fires once per webhook, and every request carries event and delivery ids for de-duplication.

Get Measured Reply Rates with Brand Marketing

Launch iMessage brand marketing campaigns that deliver measured reply rates of 15-65% across customer accounts. Verified branding, rich media support, high-deliverability iMessage.

Get Started See Pricing

Two updates went live this week.

Tuco for Slack

Connect a Slack channel and every lead conversation shows up there as its own thread.

Reply in the thread and Tuco texts the lead from the same number they have been talking to. A status line under your reply shows Sending, Sent, then Delivered.
Their replies land in the same thread, including photos, files and voice notes. Attach a file to your reply to send it to the lead.
One-tap actions on every lead: Call, Open in unibox, History.
AI drafts appear in the thread with Send and Edit buttons.
/tuco new starts a new conversation without leaving Slack.
Messages sent from Unibox, sequences, the API or the AI agent are posted in the thread too, so Slack always has the whole conversation.

To set it up, open Integrations → Slack in the Tuco app, click Add to Slack and pick a channel. More on the Slack integration page.

Reach form-fills on iMessage, not just SMS

iMessage follow-up from Salesforce, HubSpot, GoHighLevel, Clay. Higher response, no carrier throttling.

Get Started Pricing

Webhooks you can see and replay

If you send Tuco events to Zapier, Make, n8n or your own system, you can now see every delivery we made in the last 30 days.

Delivery log. Open any delivery to see the exact request we sent and what your endpoint replied, with latency and retries. Filter by status and event.
Replay. Fix your endpoint, then re-send any delivery with one click. It goes to the webhook's current URL, signed with its current secret.
Test any event. Send a realistic test for every event type: texts, photos, PDFs, links, voice notes, P2P SMS, replies, failures and a heartbeat.
Each event is sent once. Every request carries X-Tuco-Event-Id and X-Tuco-Delivery-Id, and our single automatic retry reuses the delivery id, so a slow endpoint can ignore it.
channel on message.sent tells you whether a text went out as iMessage (imessage) or as SMS from your own line (p2p_sms).
New event: call.recording.ready. Get a signed download link for each call recording, once per call.
Edit in place. Change a webhook's URL, events or Authorization header, pause it with the Active switch, or rotate its signing secret.

Everything here is also in the API: list deliveries, get one, replay, send a test and rotate the secret. See the webhook docs for every payload, or the webhooks page for an overview.

Questions

Email support@tuco.ai if you want a hand setting up either one.

Frequently asked questions

How do I connect Tuco to Slack?
In the Tuco app, open Integrations, choose the Slack tab, click Add to Slack, approve the app for your Slack workspace, and pick the channel where lead conversations should appear. New conversations then show up there as threads.
When I reply in Slack, which number does the lead see?
The same line the lead has been talking to. Tuco sends your Slack reply from that conversation's line, so the lead never sees a new number.
How long does Tuco keep webhook deliveries?
30 days. Each delivery stores the exact body that was sent, the request headers (with secrets redacted), your endpoint's response and every attempt.
Can a webhook event arrive twice?
Each event fires once per webhook. If your endpoint does not answer 2xx within 10 seconds, Tuco retries once after 5 seconds with the same X-Tuco-Delivery-Id, so you can drop the retry if you already processed the first attempt. A manual replay carries X-Tuco-Replay: true and a new delivery id.

About the author

BG View all posts →

Founder at InboxPirates Consulting. Building iMessage automation infrastructure for B2B follow-up.

New on Tuco Slack Webhooks iMessage API