Back to Overview

n8n Automation

Connect Tymeslot to n8n with a webhook, so any of its six meeting events (a booking, a booking request and its outcome, a reschedule or a cancellation) starts an n8n workflow.

Luka Breitig, Software Engineer & AI Developer
Luka Breitig

Zaktualizowano: 23 czerwca 2026

Workflow Automation

n8n is a self-hostable workflow automation tool. With Tymeslot webhooks feeding n8n, you can:

  • Add new bookings to your CRM, such as HubSpot or Salesforce
  • Send your own notifications to Slack, Discord or Telegram
  • Trigger post-meeting surveys or follow-up email sequences

Pro plan required on tymeslot.app, free for self-hosters.

Webhooks on tymeslot.app are part of the Pro plan. Self-hosted instances have no plan restriction.

1 Create a Webhook in n8n

First, set up the receiving end in n8n:

  1. Create a new workflow in n8n.
  2. Add a Webhook node.
  3. Set the HTTP Method to POST.
  4. Set the Path to something descriptive like tymeslot-bookings.
  5. Copy the Production URL (or the Test URL while you set things up). Tymeslot accepts only HTTPS URLs on a public address, so the n8n instance must be reachable from the internet. A self-hosted Tymeslot can also use plain HTTP and reach an n8n instance on your private network if you set ALLOW_PRIVATE_IPS_FOR_WEBHOOKS=true.

2 Configure Webhook in Tymeslot

Next, tell Tymeslot where to send the data:

  1. Log in to your Tymeslot dashboard.
  2. Go to Automation → Webhooks.
  3. Click Create Webhook.
  4. Name the webhook and paste your n8n Webhook URL into the Webhook URL field.
  5. Select the events you want to receive (for example Meeting Created, sent as meeting.created).
  6. Click Create Webhook.
The Create Webhook form with a name, an endpoint URL and event subscriptions ticked
The Create Webhook form in Tymeslot.

Security Verification

Tymeslot generates a security token for each webhook and sends it in the X-Tymeslot-Token header with every request. Set your n8n Webhook node's authentication to Header Auth, with X-Tymeslot-Token as the header name and the token as its value, so only Tymeslot can trigger your workflow. To copy the token, click the edit (pencil) icon on the webhook card. Where tampering matters, a Code node can also check the X-Tymeslot-Signature header, as described in the Webhook Events Reference. The signature covers the exact bytes Tymeslot sent, so first turn on Raw Body under the Webhook node's Options. n8n then passes the unparsed body on as binary data, which the Code node reads with await this.helpers.getBinaryDataBuffer(0, 'data') ; compute the HMAC over that buffer. Re-serialising the parsed JSON body will not work, because its key order and spacing differ from what was signed. On a self-hosted n8n, the Code node can only load Node's crypto module once you set NODE_FUNCTION_ALLOW_BUILTIN=crypto .

3 Test the Connection

Check that data arrives:

  • In n8n, click Listen for Event on your Webhook node.
  • In Tymeslot, find your new webhook and click the Test button (lightning bolt icon).
  • A test payload with the event webhook.test arrives in n8n straight away. Test calls do not appear in the webhook's logs.

📦 Payload Structure

Every event uses the same JSON envelope. Below is a shortened example of what arrives in n8n. For the full list of event types, all payload fields, and header verification details, see the Webhook Events Reference. 

{ 
  "event": "meeting.created",
  "timestamp": "2026-01-07T12:00:00Z",
  "webhook_id": "123",
  "data": {
    "meeting": {
      "id": "...",
      "title": "Quick Sync",
      "start_time": "2026-01-08T10:00:00Z",
      "attendee": {
        "name": "John Doe",
        "email": "john@example.com"
      },
      "urls": {
        "view": "https://...",
        "meeting": "https://..."
      }
    }
  }
}

🔗 Related Articles

Read Webhook Events Reference

Webhook Events Reference

Tymeslot webhook reference: all six meeting events (created, requested, declined, request expired, cancelled and rescheduled) with payload schemas, X-Tymeslot-Delivery-Id for deduplication, and retry behaviour.