Workflows, Analytics, and Files

All routes here need a project API key: Authorization: Bearer gi_live_.... See Authentication.

Workflows#

Manage workflow definitions and their ordered steps, inspect runs, and start manual or test runs. For what triggers and actions do, see Workflows and Webhooks.

• Create a workflow with name, trigger, and an optional triggerConfig. Steps use sortOrder, type, config, and an optional condition; updates are partial.
• Triggers: form_submitted, booking_created, booking_cancelled, booking_pending, booking_confirmed, new_contact_created, tag_added, manual, and scheduled.
• Step types: send_email, ai_research, add_tag, remove_tag, wait, condition, webhook, and update_contact.
• A workflow can have at most 3 send_email steps. Creating a fourth, or changing another step to send_email, returns 400.

Analytics and recent activity#

Read project activity and unique-journey booking and form funnels, and configure the analytics providers your pages send events to.

• Detailed analytics and provider configuration require Pro.
• period is 7d, 30d, 90d, or custom. Custom needs both inclusive start and end ISO dates.
• Filter by resourceSlug, UTM source, medium, and campaign, direct or widget source, and mobile, tablet, or desktop device.
• Booking analytics also need an IANA timezone; dates, weekdays, and times are grouped in it.
• Pick one event type or form for exact stages; without one you get a high-level summary across all of them.
• Detailed reports count unique journeys and include availableSince, stage visitors, continuation and drop-off rates, conditional skips, journey sources, and visitor devices.
• Booking reports add clicked weekdays, slot checks for selected dates, and booked weekday and time distributions. Every booking request counts once whatever its status, including rescheduled originals and replacements. Those booking distributions follow the period and event type filters only; traffic and device filters apply to visitor journeys.
• Reports never return names, emails, raw answers, journey IDs, IP addresses, or raw errors.
• Provider writes accept only public GA4 measurement IDs, numeric Meta Pixel IDs, and PostHog project keys with a US or EU host. Raw scripts and arbitrary URLs are rejected.

Files and project calendars#

Upload project files and list the calendars available through the project's connected Google accounts.

• Uploads use multipart/form-data and return an object key or URL for later use.
• Deleting an upload needs the complete object key, including nested path segments.
• Calendar listing is read-only. Connect or disconnect Google accounts in the dashboard, then pick calendars through the event type calendar endpoints.