Skip to content
Zapier

Connect Sessions to thousands of apps with Zapier — no code. Triggers fire your Zaps in near real time off the same domain events as webhooks; an action creates participants from any Zap.

Add the Sessions app in Zapier and click Connect. You'll be sent to Sessions to sign in, choose which business to connect, and approve access — then your Zaps can read and write that business's data.

Triggers

Each trigger subscribes a Zapier webhook to one event type behind the scenes:

New Registration — when an activity registration is confirmed.

activity_registration.confirmed

New Purchase — when a product purchase completes.

product_purchase.completed

New Marketing Consent — when a participant opts in to email marketing.

participant.marketing_consent_granted

Turning a Zap on registers the webhook; turning it off removes it. Deliveries are the same signed envelopes documented under Webhooks.

Actions

Create Participant adds a new person (a lead) to the connected business. It maps to this partner-API mutation:

mutation {
  createParticipant(name: "Jordan Vega", email: "jordan@example.com") {
    participant { id name email }
    errors { message }
  }
}

Authentication

The Zapier app uses OAuth — you approve a specific business and Zapier holds a scoped token. Revoke it any time from the business admin.

Building a custom integration instead of using Zapier? Authenticate the same partner API directly with a Bearer API key created under Settings → API keys:

curl https://go.sessions.website/@<handle>/api/graphql \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{"query":"{ activeBusiness { id name } }"}'

Verifying deliveries

Trigger payloads are signed exactly like webhooks (the `Sessions-Signature` header). See the Webhooks guide for the verification recipe — Zapier verifies them for you.

Zapier