May 28, 2026 - Webhook V2.2

Webhook payloads now include Sally user IDs. 🔗

The new V2.2 schema is the default for all newly created Sally webhooks. It adds a userId to every attendee and a new top-level users array, so your automation can unambiguously link a transcript to a Sally account, even when an appointment has no calendar binding and the email is missing.

🚀 What's new?

• attendees[].userId – every attendee whose email matches an active Sally account now carries the directory user ID. External guests stay on name + email only and receive userId: null.
• users (top-level array) – lists every Sally user involved in the appointment: the uploader of the recording plus all technical owners of every appointment sharing the same online meeting ID. Deduplicated by userId, filtered to active users with active directory access.
• Fully additive – existing V2.1 subscriptions keep their previous payload. Nothing breaks.
• Per-webhook version – the schema version is stored on the webhook itself. You can run V2.1 and V2.2 webhooks side by side on the same company account.

Why it matters

If you push transcripts into a CRM, a data warehouse, or a custom automation, you no longer have to guess who hosted a meeting. The user ID is stable across email changes and works even when no calendar invite is attached to the recording.

How to upgrade

There is no automatic upgrade. Existing V2.1 webhooks stay on V2.1 so legacy integrations are not disturbed. Two options to move:

1. Parallel run (recommended) – create a new webhook with the same settings as your existing one; it ships on V2.2 by default. Once your receiving system handles the new fields, deactivate the old V2.1 webhook.
2. In-place upgrade – open the existing webhook and switch the HTTP Body Version dropdown to V2.2. Make sure your receiver handles the new fields before you switch.

👉 Full payload reference, copyable example, and migration steps are in the Webhook guide.