The short version of everything — from creating your first event type to wiring webhooks and letting AI agents book on your behalf.
Create an account, set availability, and ship your first booking link in under five minutes.
Sign up at /signup with your name, email, username, and password. A default team and Mon–Fri 9–5 weekly availability are provisioned automatically.
Open Availability to configure your weekly schedule. Toggle days on and off, add multiple time slots per day, and set buffer times between meetings.
Events → New Event Type. Pick a name, duration (15/30/60 min), location (Google Meet, Zoom, In Person), and a URL slug for the public booking page.
Click Share Link in the top nav to copy your public profile URL. Visitors see all active event types and book directly from the calendar.
How public booking pages, team round-robin, and capacity calculation actually work.
Every user has a page at /{username} listing all active event types. Clicking one reveals a calendar with available dates and time slots calculated from availability + existing bookings.
Teams live at /team/{slug}. Shared event types use round-robin — bookings auto-assign to the member with the fewest meetings that day. Owners and Supervisors are never bookable.
Team slots expose capacity (e.g. 3/5 available). As members get booked, the slot decrements. When all bookable members are taken, the slot is removed from the calendar.
View any booking at /meetings/{id}. See attendee info, notes, webhook delivery logs, and actions to reschedule, complete, or cancel.
The five-level role hierarchy, team membership rules, and how managed teams resolve.
Team → New Team. Each team has a name, URL slug, and public booking page. You can create multiple teams (e.g. Mechanics, Inspectors) under one organization.
Click Invite Member and enter an email. The user is created with INVITED status. Developers and Members can only belong to one team at a time.
Owner > Admin > Supervisor > Developer > Member. Owners and Admins manage the organization and are not part of any team. Supervisors manage their assigned teams only.
Create shared event types via POST /api/teams/{slug}/events. These use round-robin assignment across all bookable team members.
Fire emails and actions automatically when bookings change state.
Workflows trigger on booking events — created, cancelled, rescheduled, completed, updated — and run an action, like sending an email to the attendee or host.
Workflows → New Workflow. Choose a trigger, a recipient (Attendee, Host, Custom Email), and customize the subject and body template.
Use {{attendeeName}}, {{hostName}}, {{eventType}}, {{startTime}}, {{endTime}}, {{notes}}, and {{cancelReason}} in subject and body.
Each workflow card shows its execution count and last run status. Failures expose the error for debugging.
15 events, HMAC signatures, and 3× retry logic for rock-solid downstream delivery.
Webhooks POST JSON payloads to your endpoint when events occur. Wire Chronae into n8n, Zapier, or your own backend without polling.
booking.created / cancelled / rescheduled / completed / updated, event_type.created / updated / deleted, availability.updated, team.updated, team.member_invited / updated / removed, api_key.created / revoked.
Each webhook has a signing secret (whsec_…). Every delivery includes an X-Webhook-Signature header (HMAC-SHA256). You can also set a custom Authorization header.
Failed deliveries are retried up to 3 times with backoff. All attempts are logged with status codes and response bodies.
The public v1 surface, API keys, and the MCP server that lets AI agents book for your customers.
Create production (sk_live_) or staging (sk_test_) keys. Keys authenticate all REST and MCP requests via Bearer token.
GET /api/v1/event-types, GET /api/v1/availability, POST /api/v1/bookings, GET /api/v1/bookings/{id}. Full CRUD plus webhook management is available via /api.
Two endpoints: /api/mcp (private, API key) for managing your calendar, and /api/mcp/public (no auth) for customers to browse and book.
AI agents can discover MCP servers via /.well-known/mcp.json, which lists both public and private endpoints and all available tools.
Profile, theme, and the rules that keep multi-team owners from double-booking themselves.
Update your name, username (which drives the public URL), and timezone.
Light, Dark, or System theme. Applied consistently across all dashboard pages.
If you're an Owner or Admin in multiple teams, choose the one you accept bookings through. Prevents double-booking across teams.
The bell in the top nav shows recent bookings, cancellations, and webhook failures.
Start a free trial and explore the full platform for 30 days. No card required.