Webhooks

A webhook posts the submission into a chat channel the moment the form is submitted. It is the fastest way to give a whole team visibility — the sales channel sees every quote request without anyone forwarding an email.

Webhooks are configured per form, not per site. That is the opposite of email and WhatsApp providers, which you set up once on the site and reuse everywhere. Each form carries its own webhook list, so your contact form can post to #sales while your careers form posts to #hiring.

Expeed Relay supports two webhook providers: Slack and Microsoft Teams. They are called providers in the interface, but they are configured on the form, not on the site — unlike the email and WhatsApp providers described in Configuring providers. Both need one thing from you — the incoming webhook URL that the chat tool generates for a specific channel.

Get a Slack webhook URL

In Slack, create (or open) a Slack app for your workspace, turn on Incoming Webhooks, then add a new webhook and choose the channel you want submissions to land in. Slack generates a URL beginning with https://hooks.slack.com/services/. Copy it — that URL is bound to the channel you picked, so choose the channel carefully.

Get a Microsoft Teams webhook URL

In Teams, open the channel you want to post to, go to its connectors or workflows options, and add an Incoming Webhook. Give it a name your team will recognize, such as “Expeed Relay”, and copy the generated URL.

Treat the URL like a password. Anyone holding a webhook URL can post messages into your channel — no login required. Expeed Relay encrypts it before storing it and never shows the full value again. The URL column shows the scheme and host only — https://hooks.slack.com/… — with the secret path withheld, followed by a short id so you can tell two webhooks on the same host apart. Keep a copy in a shared team password manager if you need it later, and if a URL leaks, revoke it in Slack or Teams — that is the only way to stop it — then add the replacement here.

Add a webhook in Expeed Relay

1. Open Forms in the sidebar, click the form, and switch to the Webhooks tab.
2. Click Add webhook.
3. Pick the Provider — Slack or Microsoft Teams.
4. Paste the URL into Webhook URL.
5. Click Add. The webhook appears in the table right away and applies to the next submission.

Screenshot to come

The Webhooks tab of a form, showing the Add Webhook dialog with the Provider dropdown open and the Webhook URL field below it

The table has four columns — Provider, the masked URL, Active, and Actions. There is no edit and no pause — the only control on the row is the delete button. To point a webhook at a different channel, or to stop it posting for a while, delete it and add the replacement URL. The Active tag is a status badge, not a switch.

How delivery works

Every webhook creates its own delivery job for every submission, right alongside the jobs created for your email and WhatsApp recipients. You can watch them on the Jobs page, where the Channel column shows the provider type — slack or teams — rather than an email or WhatsApp channel. A Microsoft Teams webhook therefore appears as TEAMS, not by its full label.

If you tried webhooks before August 2026 and nothing ever arrived, that was a Expeed Relay fault, not your configuration. Webhook delivery was broken for every site — the jobs were created, retried, and died without a message ever being posted. It is fixed. If you gave up on a webhook back then, delete the old entry, add it again with a current URL, and submit the form once to confirm the job reaches delivered.

Because the jobs are separate, they succeed and fail independently. A Slack outage will not stop the email reaching your inbox, and a bad webhook URL shows up as a failed job without affecting anything else. If chat messages stop arriving but emails still do, check the Jobs page first — a run of failures usually means the URL was revoked on the Slack or Teams side.

Related

• Forms & recipients — set up the form and its email and WhatsApp recipients before adding webhooks.
• Submissions & jobs — read delivery jobs, spot failures, and understand retries.