Skip to main content

Trigger from a webhook

Start an automation when another system sends data to a Tape address, then use the values it sends to create records, update data, and run your actions.

Written by Leo

When a webhook is received is a trigger that starts an automation when another system sends data to a web address that Tape gives you (the trigger decides when an automation starts, and the actions decide what happens). It's meant to help you bring data from forms, websites, and other tools into Tape.

You can use this trigger for many things, including:

  • Saving every response from your website's contact form as a new lead.

  • Creating a record when a payment tool reports a new invoice.

Note:

  • There's no current record. A webhook isn't tied to a record, so actions like Update record aren't available. Use Create record or Search for records to work with data.

  • Keep the web address private. Anyone who knows the address can start the automation. Tape doesn't check a signature or password, and you can't reset the address. To get a new address, duplicate the automation or create a new one.

  • Paused automations don't run. While the automation is Paused or Broken, Tape still accepts requests and the sender gets a success response, but no run starts. The request still shows as the last received data in the editor.

Who can use the When a webhook is received trigger?

  • Automations are available on the Free, Plus, and Premium Plans. The number of automation actions per month depends on your plan. Learn more about plans →

  • To create, edit, pause, run, or delete automations, you need to be a Workspace admin in the workspace the database app belongs to. Only workspace admins see Automations in a database app.

Set up the When a webhook is received trigger

To set up the trigger:

  1. Open the database app and click the automations icon at the top right (Create and view automations).

  2. Select New automation.

  3. Select When a webhook is received from the list of triggers.

  4. Select Copy to copy the web address under Send webhook to:.

  5. Send a first test request to the address from your other system. Learn more about testing below →

  6. Select Refresh to load the data you sent.

  7. Select Add action and choose what should happen. Use the values you received in your actions.

  8. Select Create automation.

The trigger card for When a webhook is received, with the web address, Copy, and Refresh

What the trigger shows

Under the trigger, Tape shows a box with the web address of your automation:

  • Send webhook to: shows the address. Send your data to it.

  • Copy copies the address.

  • No webhook received yet shows until the first request arrives. After that, the box shows the data of the latest request.

  • Variables shows the received data as values you can insert in actions. Switch to Payload to see the raw request.

  • Hide webhook hides the box, and Show webhook shows it again.

  • Refresh loads the latest request.

Each new automation gets its own address. To read the data in a larger box, select Open in fullscreen or press cmd/ctrl + enter. The address stays the same when you edit the automation. A duplicated automation gets its own new address. To duplicate an automation, click ••• next to it in the list of automations, then select Duplicate.

Use the received data

Send one test request first. Then select Refresh, and the fields of your request appear under Variables. Insert them into the fields of an action, like any other value. Learn more about values and variables →

Send a POST request with JSON, form data, or plain text. To send files, use multipart/form-data. The files are available as Webhook files, and the whole request as Webhook payload. Tape answers with status 200 and an empty response as soon as it receives the request. If the automation is Active, it runs right after.

Actions without a current record

A webhook isn't started by a record, so it has no current record. Actions that change or read "the current record" don't show up in Add action. That includes:

  • Update record, Delete record, and Restore record

  • Add comment and Get previous values

  • Get related and Update related

  • Create web link and Call automation

Instead, create the record you need with Create record, or find it with Search for records. Then work with the collection. Learn more about collected records →

Let's look at an example

Let's say you want every contact form response to become a lead. Here's how:

  1. Set the trigger to When a webhook is received in Leads.

  2. Select Copy and add the address to your website's form tool as its webhook.

  3. Submit a test form, then select Refresh.

  4. Select Add action → Create record, and choose your Leads app.

  5. Insert the Name and Email values from Variables into the matching fields.

  6. Select Create automation.

The next time someone sends the form, you should see a new lead! For a full walkthrough, see Save form responses with a webhook →.

When a webhook is received errors

  • If No webhook received yet doesn't change after Refresh, the request hasn't arrived. Check the address and the method of your other system. If the address is wrong, the sender gets an error such as 401 Unauthorized. If the request says it's JSON but isn't valid JSON, the sender gets an error, too.

  • If the status next to the automation's name shows Broken in red, part of the automation doesn't fit the trigger, often an action that needs a current record. The part that doesn't fit is shown in red. While the automation is Broken, it doesn't run and you can't start a manual run. Tape then shows Trigger runs manually not possible because of broken automation.

  • If a run fails, you can see each step and its message in the automation's runs. To see the runs of an automation, click the play button next to Manual run at the top right of the editor (View all runs), or press cmd/ctrl + 1. The Runs panel lists the runs of the last 30 days. Select a run to see each step and its message. To see the runs of all automations, select Runs in the Automation Center.

  • Many requests in a short time can delay automations across your organization. The delay is temporary. Tape checks the load again shortly and runs waiting automations automatically. Learn more →

Test, pause, edit, or delete an automation with this trigger

  • Manual run runs the automation once. Choose Last payload to reuse the last request it received, or Custom payload to paste your own test data. To test the full path, send a request from your other system and select Refresh. Learn more about testing →

  • New automations you create in the editor are Active right away. The status, Active or Paused, sits below the automation's name in the editor. To pause one, select the status to switch it to Paused, then select Save changes.

  • To edit an automation, open the app, click the automations icon in the top bar, then select the automation. Select Save changes when you're done.

  • To delete an automation, open it and click ••• at the top right, then select Delete. Confirm with Delete. You can also click ••• next to the automation in the list of automations, then select Delete. Deleting can't be undone.

  • To switch to another trigger, hover over the trigger and click ••• to the right of it, then select Turn into and choose a trigger. The filter and the actions stay. If an action or a filter condition doesn't fit the new trigger, for example Update record after switching to a schedule, or Has changed after switching away from When a record is updated, the status next to the automation's name turns red and shows Broken until you change or remove it.

Learn more

FAQs

How do I get the web address of my webhook?

Set up the trigger. The address appears under Send webhook to:. Select Copy to copy it.

Why can't I see the data from my other system?

Send a test request first, then select Refresh. Until then, the box shows No webhook received yet.

Can I use the data in my actions?

Yes! After the first request, the fields appear under Variables. Insert them like any other value.

Why can't I update the current record?

A webhook isn't started by a record, so there's no current record. Use Create record, or find a record with Search for records.

What's the difference between this trigger and When a web link is clicked?

When a webhook is received starts when another system sends data. When a web link is clicked starts when a person opens a link for a record. Learn more →

Are there other triggers I can use?

Yes! An automation can start when a record is created, updated, or deleted, when a comment is added, when a date arrives, on a schedule, and more. See every trigger in Automation triggers →

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Triggers in the developer docs →

Still have more questions? Find answers and get help from community experts in the Tape community →.

Did this answer your question?