Connect Sally with n8n

To connect Sally with n8n, you use webhooks. A webhook lets Sally automatically send information (e.g., meeting summaries, tasks, or decisions) directly into your n8n workflows, so you can continue automating downstream actions.

If you’re new to webhooks, we recommend reading our full Webhook Guide, which explains in detail what they are and how they work.

Quick Navigation

1. Create a workflow in n8n
   • 1.1. Add a webhook trigger in n8n
   • 1.2. Configure the webhook in Sally
2. Inspect and Debug Webhook Logs

1. Create a workflow in n8n

1.1. Add a webhook trigger in n8n

First, you need to create a new workflow and add a webhook trigger. This webhook will act as the entry point for all data Sally sends.

To do this, follow these steps:

1. In n8n, go to the Personal tab and click Create Workflow.

Click Create Workflow

2. Give your workflow a clear name (e.g., sally-webhook) and add your first step.
3. Press the + button in the middle.

Name your workflow and add the first step

3. Search for Webhook and select it.

Choose Webhook as the trigger

4. Configure the webhook:
   • HTTP Method: POST → because Sally always sends data (instead of requesting it).
   • Path: a simple, clear identifier (e.g., sally-webhook) → this will become part of the final webhook URL.
   • Respond: Immediately → ensures Sally gets a quick confirmation that the webhook was received.
5. Switch to Production URL - this is the permanent URL that Sally will call.

Copy your Production URL

You can already copy the Production URL here by clicking the copy button. You’ll need this later when configuring the webhook inside Sally.

Configure the webhook trigger

6. Finally, activate your workflow.

First activation matters

The first activation must be done inside the editor, not from the overview list.

After this initial activation, you can conveniently control the workflow from the overview.

Copy the Production URL for use in Sally

7. At this point, your webhook in n8n has been created. The next step is to configure this webhook in Sally so that events (like meeting summaries) can be sent to it.

Activate the workflow so the webhook can receive data

1.2. Configure the webhook in Sally

Now that your webhook is ready in n8n, you need to tell Sally where to send the data.

To do this, follow these steps:

1. In Sally, open Settings in the left sidebar.

Go to Settings

2. Select Integrations and click + Add Integration.

Click Add Integration

3. From the list, choose Webhook and click Create Webhook.

Select Webhook and create a new one

4. Fill in the form:
   • Name: Give it a clear label (e.g., “Summary → n8n”).
   • Trigger: Select when the webhook should fire (e.g., Summary for appointment has been created).
   • Organization Webhook: Decide if it should apply only to your meetings or the whole organization.
   • Webhook URL: Paste the Production URL you copied from n8n.
   • Version: Always choose 3 (Newest).
5. Click Create.

Paste the Production URL from n8n

✅ Your webhook is now fully registered in Sally. From this point on, Sally will send the selected event data (e.g., meeting summaries, tasks, or decisions) directly to your n8n workflow whenever the chosen trigger occurs.

---

2. Inspect and Debug Webhook Logs

Finally, you should confirm that data is really being sent and received. Sally provides detailed logs that show exactly what was delivered to n8n and whether it succeeded.

To verify this, follow these steps:

1. Go to your personal integrations.
2. Click Logs on your webhook.

Go to Logs

Once your chosen trigger fires, all log entries will appear here – making it easy to confirm that your n8n integration is successfully connected and receiving data.

Webhook is active – open Logs for details

Each entry shows:

1. Execution time – when Sally sent the event.
2. Target endpoint – the n8n webhook URL.
3. HTTP status – response from n8n (e.g., 200 OK).

Logs are your best friends

Use logs to confirm delivery, inspect payloads, and debug errors. If something doesn’t work in n8n, check the Sally logs first to ensure the event was sent correctly.