Skip to main content
A webhook lets another tool notify Zite when something happens. For example, a new form submission can start a workflow that saves an enquiry and notifies your team. The other tool must support sending webhooks. You give it a webhook URL from Zite and choose which events to send.
Webhooks are available on all plans. Published workflow executions use your workflow-run allowance. Zite-provided AI can also use credits.

​
How webhooks work

A form submission in another tool sends an event to a Zite workflow, which saves a new record in the Enquiries table

Example: another tool sends a form submission, then a Zite workflow saves the enquiry.

Tell Zite the source tool, the event, and the result you want. Your workflow might save a request, update an order’s status, or send a team notification.

​
Create a webhook

1

Describe the connection

In the editor’s chat, explain what should happen. For example:
When my form tool sends a new enquiry, save the name, email, and message in the Enquiries table. Set its status to New. If the same submission arrives again, don’t create a duplicate.
You can also open Workflows → Webhooks → Add webhook and enter your request there.
2

Connect the source tool

When Zite shows Waiting for next run, copy the Test URL. Paste it into the other tool’s webhook settings and select only the events you need.Setup varies by tool. Tell Zite which service you’re connecting and follow any additional steps it gives you.
3

Send and select a sample event

Use the source tool’s test option, or perform the action that should send an event. If several events arrive, select the one your workflow should handle, then choose Use selected event.Zite uses the sample to understand the incoming information. For a new, unpublished webhook, capturing a sample doesn’t mean the workflow has completed its actions.
4

Publish and verify

Review the workflow, then select Publish. Send another event from the source tool.Open the workflow’s History to check the run, then confirm the expected record or message exists. This checks the whole connection.
Keep the webhook URL private: anyone with it can send events to your workflow. Test with sample data. An already-published webhook can perform real actions while you capture an event.

​
Manage webhooks

Open Workflows → Webhooks to search for a webhook, copy its Inbound URL, or select its name to open the workflow. A Not published badge means the webhook isn’t active yet. Unpublished changes means the published version still has the previous settings.

​
Troubleshooting

  • No sample event arrives: Check that the capture session is active, then check the Test URL, the selected event, and the source tool’s delivery history. You don’t need to publish to capture a sample.
  • The workflow doesn’t run automatically: Confirm the webhook is published and enabled, then check the Inbound URL and the source tool’s delivery history.
  • Capture session expired: Ask Zite to start a new sample capture, then send another test event.
  • The run fails: Open History, filter by Triggered by → Webhook and Status → Error, then ask Zite to inspect the failed run.
  • Duplicate records appear: Ask Zite to recognize repeat deliveries using the source tool’s event or submission identifier.
  • The Webhooks tab is empty: It lists incoming events. Actions that send information from Zite to another tool appear in the workflow instead.
See Workflow Runs for inspecting failures and App Usage for allowances.
Last modified on October 22, 2026