Choose the right way to send or receive webhooks
Send data to other services, receive webhooks and catch emails with Workflows, and know when the older Automation pages still apply.
- Verified Nov 17, 2026
- Classic builder
On this page
A webhook is an HTTP request one system sends to another when something happens. In Tadabase you can send webhooks when your data changes, receive webhooks that start work in your app, and receive emails the same way. All three are now built with Workflows; the older pages under Automation keep running the setups you already have.
Which one to use #
| You want to | Build it with (current way) | Older setup you may already have |
|---|---|---|
| Send record data to another service when something happens | A workflow with a Trigger Webhook action | Automation › Outgoing Webhooks |
| Let another service start work in your app by calling a URL | A workflow that starts with the Incoming Webhook trigger | Automation › Incoming Webhooks |
| Start work in your app when an email arrives | A workflow that starts with the Email Catcher trigger | Automation › Email Catchers |
A workflow can do more than the older pages: after the trigger it can create or update records in several tables, branch on conditions and call other services in the same run. See Workflows overview.
Outgoing webhooks, incoming webhooks and email catchers are moving into Workflows #
If your app can use Workflows (they are switched on and your plan includes them), the older Automation pages behave like this:
- The app has none of that kind yet: the page says they are no longer managed there, with a Go to Workflows button. You create new ones as a workflow.
- The app already has some: they keep working and you keep managing them on the same page. A short notice says they are moving to Workflows and recommends a workflow for new ones, with an Open Workflows button.
Apps that cannot use Workflows see the older pages unchanged.
Send data to another service #
Create a workflow and add a Trigger Webhook action. The workflow's trigger decides when it sends (for example when a record is created or updated), and the action decides what it sends and where. See Trigger Webhook.
For webhooks set up earlier under Automation › Outgoing Webhooks, see Manage outgoing webhooks under Automation. Every send from those webhooks is recorded in Outgoing webhook logs.
Receive webhooks from another service #
Create a workflow and start it with the Incoming Webhook trigger. Once the workflow is saved it gets its own Webhook URL; another service sends a JSON body to that URL with a POST request and the workflow runs. See Incoming Webhook trigger and Receive data from another service with an incoming webhook.
Start work from an email #
Create a workflow and start it with the Email Catcher trigger. The workflow gets an inbox address, and every email delivered to it runs the workflow with the sender, subject, body and attachments available to its steps. See Create records from incoming emails.
Was this page helpful?
Something wrong or missing on this page? Tell us.