Connect an outside app to a channel with webhooks

Wire an outside app — a form, a Zapier/Make automation, a support desk, a monitoring alert — into a TeamChat channel without writing any code. Whatever it sends becomes a message in the channel, and you can have the AI or an agent respond automatically.

What you'll use

A channel webhook: a private URL you generate right from the channel. Anything that can send a web request to that URL drops a message into the channel. The secret key in the URL is the credential — the sender needs no login — so treat the URL like a password.

Create a webhook (all in the UI)

1. Open the channel in TeamChat.
2. Open its menu — either the ⋮ (More actions) button at the top of the conversation, or the ⚙ gear on the channel in the left-hand list — and choose Manage Webhooks.
3. Click New Webhook, give it a name that says where it's coming from (e.g. "Zendesk", "CI alerts"), and click Create.
4. Click Copy URL on the new webhook — that's the address your outside app posts to. Use Delete to revoke it anytime; the URL stops working immediately.

Each channel's list shows only its own webhooks, so you can see at a glance what's wired into where.

Use it

Paste that URL into whatever tool is sending the events — the "Webhook URL" or "POST URL" field in Zapier, Make, a support desk, a monitoring alert, and so on. Set the message text to what you want to appear in the channel. Every event becomes a message.

Get the AI or an agent to respond

What you put in the message controls what happens — exactly like typing in the channel yourself:

• @ai … — the channel's default AI replies. e.g. @ai summarize this ticket and suggest a priority
• @ai:<model> … — a specific model replies, named by its identifier. e.g. @ai:haiku keep it short or @ai:sonnet do a careful review
• @AgentName … — wakes that agent to read the thread and act. e.g. @Bug-Triager a prod 500 spike just started

A plain message with no mention just posts into the channel for people to read.

Good to know

• Fire-and-forget. The sending app doesn't get the AI's answer back in its response — the reply shows up in the channel a moment later (and, for connected external channels, is sent back out). Think of it as dropping a note in, not holding a live chat.
• Keep the URL secret. The key in the URL is the whole security boundary — anyone who has it can post to the channel. If it ever leaks, delete the webhook and create a new one.
• Attach files if your tool supports it and they'll ride along with the message.

Result

Your outside tools talk straight to your team and your agents. A new ticket, a failed build, a form submission — each lands in the right channel, and the AI or the right agent handles it automatically. When you're ready to script it directly, see the developer version: Pipe external events to an agent via webhooks.