Tour booking webhooks

POST tour events to your automation webhook URL. When the invitee email matches an EchoPM user, bookings can create CONFIRMED TourRequest rows.

Echo JSON format (recommended)#

Create a tour:

{
  "event": "calendly.invitee.created",
  "propertyId": "PROPERTY_CUID",
  "email": "prospect@example.com",
  "scheduledAt": "2026-06-01T15:00:00.000Z",
  "name": "Alex Prospect"
}

Cancel:

{
  "event": "calendly.invitee.canceled",
  "propertyId": "PROPERTY_CUID",
  "email": "prospect@example.com"
}

Event names use a calendly.* prefix for backward compatibility; any HTTP client can send this shape.

Native scheduling payloads#

The handler also accepts common third-party scheduling webhook bodies (e.g. invitee.created / invitee.canceled) when forwarded unchanged to your automation URL. Property resolution uses tracking.utm_content as the EchoPM property ID when present.

Prerequisites#

1. Automation webhook URL configured with your org token
2. Property ID available in the payload (directly or via UTM tracking on embed links)
3. Org showing settings configured in manager Settings → leasing

Important constraints#

• Invitee must have an EchoPM account (email match) for webhook-created tours; others should use in-app Request a time
• Webhook auth uses org organizationId + token query params — keep the token secret
• All requests are logged to IntegrationLog for debugging

Related#

• Automation URL — base URL and auth
• Manager Schedule — tour inbox and status actions