Connect a Webhook (A–Z Guide)

Webhooks let Sally push data to other apps the moment something happens - for example, send a meeting summary into your automation platform as soon as it’s ready.

This guide explains webhooks from the ground up and walks you through a complete example.

Quick Navigation

1. What is a webhook (in simple terms)?
2. Prerequisites
3. Get a webhook URL from your tool
4. Create the webhook in Sally
5. Verify the connection & view logs
   • 5.1. What the logs are for (and why they matter)
   • 5.2. How to find log entries in Sally
   • 5.3. How to read a log entry
   • 5.4. Typical causes & quick fixes
6. FAQ & troubleshooting

1. What is a webhook (in simple terms)?

A webhook is basically an internet address (URL = Uniform Resource Locator) that another tool or system provides to you (for example: Zapier, Make, n8n, Power Automate, or even your own backend).

Whenever something specific happens in Sally – for instance, when a summary is created – Sally will automatically send a message to that URL.

Think of it like this:

• API (Application Programming Interface) = you actively ask another system for data.
• Webhook = the system automatically sends you data when something happens.

Typical examples of how webhooks are used:

• Send summaries into an automation platform for further processing.
• Create tasks automatically in your workflow via Zapier, Make, n8n, or Power Automate.
• Trigger actions in your own backend system whenever a meeting ends.

---

2. Prerequisites

Before you can connect Sally with another tool using webhooks, you’ll need a few things in place:

• Access to the tool where you want Sally to send information
  Example: Zapier, Make, n8n, Power Automate, or your own system.

  info

  You need a user account in that tool, otherwise you won’t be able to set up the connection.

• Permission to create or copy a Webhook URL

  A Webhook URL is a special internet address provided by the destination tool (the place where you want Sally to send data).

  • In Zapier, Make, n8n or Power Automate, you create this in the workflow/scenario settings.
  • In your own system, a developer would usually provide the URL.
  
  
  info

  Check if your account role (e.g. “admin” or “owner”) allows you to create or copy such URLs. If not, you may need help from your administrator or developer.

• Sally account with permission to add integrations
  You must be logged into your Sally account. There are two options:
  • Personal webhooks: You can always create these for your own account, without organisation-wide permissions.
  • Organisation-wide webhooks: If you want the webhook to apply to all users in your organisation, your role must allow adding or managing integrations at the organisation level.

Important

Webhook URLs always come from the destination tool, not from Sally.

This means:

1. Go into the tool you want to connect (e.g. Zapier, Make, n8n, Power Automate, custom system).
2. Create or copy the Webhook URL there.
3. Paste that URL into Sally when setting up the integration.

Without this URL from the other tool, Sally has no place to send the information.

---

3. Get a webhook URL from your tool

The exact steps depend on the destination tool, but the principle is always the same:

1. Go to your tool (e.g., Zapier, Make, n8n, Power Automate, custom system).
2. Create or enable an Incoming Webhook (sometimes also called “listener URL” or “endpoint”).
3. Copy the generated Webhook URL.

Tip

Each tool has its own way of creating webhook URLs. If unsure, search for “Create webhook” + your tool’s name in its documentation.

---

4. Create the webhook in Sally

1. In Sally, go to Settings in the left sidebar.

Open Settings

2. Open Integrations.
3. Click Add Integration (under Your personal integrations).

Go to Integrations

3. Click Add Integration (under Your personal integrations).
4. Choose Webhook and click Create Webhook.

Create a new webhook

5. Fill out the form with this information:

• Name: Pick something readable, e.g., “Summary → Zapier” or “Tasks → n8n”.

• When should the webhook be executed?: Choose the event (e.g., “Summary for appointment has been created”).

  Trigger (event)

  Select when Sally should send data. For example: “Summary for appointment has been created.”
  Available events may evolve; use the dropdown to see what your workspace supports.

• Organization webhook?: Choose whether this webhook should trigger only for your own meetings or for the entire organization.

  Scope

  • Only my appointments/recordings: The webhook fires only for meetings you own.
  • Organization webhook: Fires for all users in the org (useful for central integrations like CRM or reporting).

• Webhook URL: Paste the URL you copied from your destination tool.

• Version: Select 3 (Newest) unless you have a legacy reason to use an older payload format.

  Version

  Defines the payload format Sally sends. Always choose 3 (Newest) unless your system requires a legacy format.

6. Click Create.

Create a new webhook

7. After successful connection, Webhook will appear in your integration list.

Webhook is now active

---

5. Verify the connection & view logs

5.1. What the logs are for (and why they matter)

Logs are your source of truth for what Sally actually sent, when it sent it, and how the destination responded.
They help you:

• Verify delivery: Confirm that events are firing and reaching the right endpoint.
• Debug failures: See precise errors from the destination (e.g., invalid URL, auth missing).
• Inspect content: Check the payload structure your endpoint received (useful when mapping fields in Zapier/Make or custom code).
• Measure performance: Review delivery latency and retry behavior to spot bottlenecks.
• Audit activity: Track who/what triggered which outbound calls for compliance and change management.

5.2. How to find log entries in Sally

1. Go to Integrations in Sally.
2. Find your webhook under Your personal integrations.
3. Click Logs in the Actions column.

Click Logs

4. Here you will find all log entries:

Each webhook request is recorded in the logs

5.3. How to read a log entry

Each entry typically includes:

1. Execution time – When the event was sent.
2. Target endpoint – The exact URL Sally called (useful to catch typos/wrong environments).
3. HTTP status – Outcome from the destination (e.g., 202 Accepted = success).
4. Duration/latency – Time from request start to response (helps identify slow receivers).
5. Event name / trigger – Which Sally event fired (e.g., summary.created).
6. Retries (if any) – Whether Sally retried after a failure and how many times.
7. Request/response details – Payload preview and response body or message (for debugging mappings and auth).

Common statuses (what they mean)

• 2xx Success – Destination accepted the request.
• 4xx Client error – Usually a configuration issue on your side:
  • 400 Bad Request → Endpoint didn’t like the payload format.
  • 401/403 Unauthorized/Forbidden → Missing or invalid auth header/token.
  • 404 Not Found → Wrong path/URL.
  • 410 Gone → Endpoint was removed/rotated.
  • 429 Too Many Requests → Rate limited; consider backoff.
• 5xx Server error – Destination was down or errored; Sally will typically retry.

5.4. Typical causes & quick fixes

• Wrong URL / environment → Compare the logged Target endpoint with your expected URL (prod vs. staging).
• Missing headers/auth → Add the required token or header in your destination (or rotate a new one).
• Payload mismatch → Check the logged payload preview and switch to Version 3 (Newest) or adjust your parser.
• Rate limiting (429) → Reduce event volume or implement queueing on the receiver; allow retries to succeed.
• Timeouts/5xx → Check destination availability; consider making the receiver faster or more resilient.

Best practices with logs

• Validate end-to-end in a test endpoint first, then point the webhook to production.
• Bookmark a successful entry as a golden sample for future field mapping.
• Monitor patterns (e.g., repeated 4xx on a specific event) to catch regressions early.
• Rotate URLs/tokens if you suspect exposure; watch logs to confirm the new credentials work.
• Limit sensitive content in your destination’s responses; logs may include response snippets for debugging.

---

6. FAQ & troubleshooting

Q: My webhook doesn’t send anything.

• Check that the chosen trigger event has actually occurred.
• Verify the webhook is enabled (toggle switch).
• Look in Logs for errors (e.g., invalid URL).

Q: Where do I get the webhook URL?

• Always in your destination tool (e.g., Zapier, Make, n8n, Power Automate, or your own system).
• Sally does not generate this URL.

Q: Which version should I pick?

• Always use Version 3 (Newest) unless you already run an integration with an older version.