Webhooks and Zapier/Make Integration

Zephyr documentation

How Named Webhooks Work

Zephyr lets you save named HTTPS endpoints and trigger them from workflows. Instead of pasting a URL directly into a workflow, you save it once with a friendly name (like 'My Zapier Automation') and then pick it by name in the WorkflowBuilder. When the workflow runs, Zephyr sends a POST request to that endpoint with the email context and the result of the previous action.

Setting Up Named Endpoints

Go to Settings > Connected Services and find the Webhooks section. Click Add endpoint, enter a name for the endpoint and its HTTPS URL, then click Save. You can save up to 20 named endpoints. To remove an endpoint, click the delete icon next to it. No OAuth or token is needed. The URL must start with https://.

Webhook Payload

When a webhook_named action fires, Zephyr sends a POST request with a JSON body containing: email.subject (string), email.sender (string), result (the output of the previous workflow action, e.g. an AI summary), and timestamp (ISO 8601). Use this payload in Zapier, Make, or your own backend to trigger further automation.

Connecting with Zapier

1) In Zapier, create a new Zap and choose 'Webhooks by Zapier' as the trigger.

2
Select 'Catch Hook' and copy the webhook URL Zapier provides.
3
In Zephyr, go to Settings > Connected Services > Webhooks and add a new endpoint named 'My Zapier Automation' with that URL.
4
In the WorkflowBuilder, add a webhook_named action and select 'My Zapier Automation' from the dropdown.
5
When the workflow runs, Zapier receives the payload and you can map the fields to any Zapier action.

Connecting with Make (Integromat)

1) In Make, create a new scenario and add a Webhooks module as the trigger.

2
Choose 'Custom webhook', create it, and copy the URL.
3
In Zephyr, go to Settings > Connected Services > Webhooks and add a new endpoint named 'My Make Scenario' with that URL.
4
In the WorkflowBuilder, add a webhook_named action and select 'My Make Scenario'.
5
When the workflow runs, Make receives the payload and you can connect it to any Make module.

Named Webhooks vs webhook_out

Zephyr has two webhook action types. webhook_named uses a saved named endpoint: the URL is stored in Settings and referenced by name in the workflow, so you can update the URL in one place without editing every workflow. webhook_out requires a URL pasted directly into the workflow definition. Use webhook_named for recurring automations and webhook_out for one-off or dynamic URLs.