Calendly Booking Notify

Keep your team aware of upcoming Calendly bookings without anyone having to open the Calendly dashboard. On each run this workflow pulls the current active scheduled events from the Calendly API and delivers them to the workflow's InTouch subscribers.

Use case

Run on a schedule (for example every morning, or hourly during business hours) to get a recurring notification of who has booked time. Useful for sales, support, recruiting, or consulting teams that take meetings via Calendly and want a single push of the day's agenda.

What it does each run

1. fetch-bookings (calendly tool) — calls the Calendly list_scheduled_events operation (GET /scheduled_events) for active events. The connector publishes two outputs: result (the raw JSON API response as a string) and status (the HTTP status code).
2. notify (message tool) — sends a notification to the workflow's subscribers containing the raw bookings payload ({{fetch-bookings.result}}) and the API HTTP status ({{fetch-bookings.status}}).

Required credentials

• Calendly API key — a Calendly personal access token (or OAuth token). The workflow.yaml sets apiKey: "<set via credential>" as a placeholder; you supply the real value by attaching an InTouch credential to the fetch-bookings task or by providing it through a runtime environment variable. Never hardcode the token in the workflow file.

Calendly's API is OAuth-based; a personal access token from your Calendly account settings (Integrations -> API & Webhooks) is the simplest way to authenticate.

Notes

• The calendly connector returns the raw API response only. This workflow forwards that payload verbatim in the notification. If you want a human-readable digest (counts, one bullet per booking), insert an ai or anthropic task between fetch-bookings and notify that consumes {{fetch-bookings.result}} and publish {{<step>.answer}} into the message body instead.
• alertOnError: true means subscribers are also notified if the API call fails.