How do you connect Sally AI with Zapier?

To connect Sally with Zapier you use a webhook. Sally sends the results of a meeting to an address of your choice, and your Zap picks up from there.

The setup has two parts. In Zapier you build a Zap with the Catch Hook trigger and copy its webhook URL; in Sally you set up the webhook with that address. If you have not worked with webhooks before, read the webhook guide first, it explains in detail what a webhook is and which fields it carries.

Quick navigation

1. Create your own Zap
   • 1.1. Add a Catch Hook in Zapier
   • 1.2. Configure the webhook in Sally
2. Check the webhook activity in the log
   • 2.1. What do the HTTP status codes mean?

1. How do you create your own Zap?

1.1. Add a Catch Hook in Zapier

First you need a Zap in Zapier that waits for incoming data. That trigger is the entry point for everything Sally sends later.

Check your plan before you start

The Catch Hook trigger belongs to Webhooks by Zapier, which Zapier lists as a premium app. According to Zapier's help, it is not included in the free plan, only from Professional upwards, plus during the free trial.

1. Create a new Zap in Zapier and give it a name.
2. In the Zap editor, click the Trigger step and search for Webhooks by Zapier. Then pick Catch Hook from the Event field and confirm with Continue.
3. Open the Test section of the trigger. The address Zapier generated for this Zap sits under Your webhook URL. Click Copy, this is where Sally will send the results.

Figure 1: Copy the webhook URL in Zapier

4. Then build the rest of your Zap, a message in Slack or an entry in your CRM for instance.

A draft is not enough

As long as the Zap says draft in the top left and the toggle in the top right is set to Off, it does not run permanently. Publish the Zap with Publish and switch it on, otherwise the data from Sally never reaches your Zap.

1.2. Configure the webhook in Sally

Now you put the copied address into Sally.

1. In Sally, open Settings from the bottom-left corner of the sidebar.

Figure 2: Open Settings

2. Under Configuration, select Integrations and open the Webhooks tab. Click Create webhook under Webhooks (Personal).

Figure 3: Create a personal webhook

Personal or organization-wide

Webhooks (Personal) fire after your own meetings are summarized. Webhooks (Organization) apply to the entire organization account and are managed by administrators. For your own Zap, use the personal section.

3. Fill in the upper part of the Create webhook dialog: Name, an optional Description, the Trigger, the Language, the address from Zapier under Webhook URL, and the Authentication.

Figure 4: Enter the name, the trigger and the address

4. Scroll down in the dialog. Body contents defines what Sally sends along, Options defines when the webhook fires. Then click Create.

Figure 5: Choose the body contents and create the webhook

The table below explains every field of the dialog.

Field	What it does
Name	Required. The display name of the webhook. Pick something you will recognize later, for example "CRM entry via Zapier".
Description	Optional. A note on what the webhook is triggered for. Useful once several webhooks run side by side.
Trigger	Required. Defines when Sally sends. Automatically after every summary runs the webhook after every transcription, which means after a video or audio upload and after a meeting Sally attended.
Trigger for all languages	When enabled, the webhook fires no matter which language the summary was created in.
Webhook URL	Required. The address you copied in Zapier.
Authentication	Defines how Sally identifies itself to the target system. For a Catch Hook, None is enough, because the address itself is not public. The webhook guide covers the other methods.
Custom headers (optional)	Add header lets you send extra headers, an API key for instance. A Zap normally does not need this.
Body contents	Defines which fields end up in the POST body: Summary, Section content, Objections, Conversation goals and Transcript. Only enabled fields are sent on each trigger, and the less you send, the smaller and faster the request.
Preview and Copy example body	Shows the body Sally would send with the toggles you set, and copies it. Handy for testing the Zap without running a real meeting.
Re-trigger on re-summarization	When off, the webhook fires only the first time. When on, Sally sends again whenever a summary is regenerated.
Webhook active	Switches the webhook on. Turning it off leaves it in place without deleting it.

From now on Sally sends the selected content to your Zap whenever the trigger fires.

Teaching Zapier the fields

Zapier learns the fields from the first real request. Use Copy example body in the Sally dialog and send that body to the address, or run Test trigger in Zapier once Sally has sent something. After that you can pick the fields in the following steps of your Zap.

Spotting older webhooks

Every webhook in the list carries its body version. Sally creates new webhooks on the current version, older ones are marked Outdated or Expiring. If an old webhook is still running, recreate it with the same settings. The version determines how the body is built, so a recreated webhook may deliver a different body. Check afterwards that the steps in your Zap still work with the fields that actually arrive.

---

2. How do you inspect and debug webhook logs?

Finally, check that Sally is actually sending. Sally logs every trigger, so you can see what went to Zapier and how Zapier answered.

1. Open the Webhooks tab and click the document icon on your webhook.

Figure 6: Open the logs of the webhook

Once the trigger has fired, the entries show up in the log. Every entry shows:

1. Execution time: when Sally sent the event.
2. Endpoint: the webhook URL from Zapier.
3. HTTP status: the answer from Zapier, for example 200 OK.

Details opens the request that was sent, body included.

2.1. What do the HTTP status codes mean?

The status comes from Zapier, not from Sally. It tells you whether the request arrived and where to look when it did not.

Status	What it means	What you can do
200 OK, 204 No Content	Zapier accepted the request.	Nothing, the connection works. If the Zap still does nothing, it is usually unpublished or switched off.
400 Bad Request	Zapier cannot read the body.	Look at the example body from Sally and check that the Catch Hook is still the same one.
401 Unauthorized, 403 Forbidden	Zapier rejects the request.	Check the authentication and the custom headers on the Sally webhook. A Catch Hook needs neither.
404 Not Found, 410 Gone	The address no longer answers, for instance because the Zap was deleted or the trigger was recreated.	Copy the address in Zapier again and put it into the webhook.
429 Too Many Requests	Too many requests arrive in a short time, or your Zapier plan has hit its task limit.	Send less content or check the usage in your Zapier account.
500, 502, 503, 504	Zapier was unreachable, or the Zap failed with an error.	Trigger again later and check the Zap history in Zapier.

Start here when something is wrong

If nothing arrives in Zapier, check the log in Sally first. No entry means the trigger did not fire, which points back at Sally. An entry with 200 OK while the Zap does nothing points at the Zap itself: check whether it is published and switched on, and whether one of the following steps failed.