STEP 1
Connect Bookwhen and Sessions
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Bookwhen and Sessions Integration
Build scheduling workflows between Bookwhen and Sessions on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Bookwhen and Sessions
Detailed info you need to know about Bookwhen and Sessions integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Bookwhen to Sessions
Set up your Bookwhen and Sessions integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Bookwhen and Sessions nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Bookwhen and Sessions. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Bookwhen and Sessions work in WEXTL?
WEXTL exposes actions and triggers for Bookwhen and Sessions that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Sessions triggersBookwhen actions
Sessions modules
- Create a RoomCreates a new room (booking).
- Create a SessionCreates a new session.
- Delete a SessionDeletes an existing session by id.
- Get a SessionRetrieves details for an existing session.
- Get a TranscriptRetrieves a transcript for an existing session.
- Invite to a SessionAdds invitees to an upcoming session.
- List BookingsRetrieves a list of bookings from account.
- List Session InviteesRetrieves a list of session participants.
- List SessionsRetrieves a list of sessions from account.
- Make an API CallPerforms an arbitrary authorized API call.
- Update a SessionUpdates a single session by id.
- Watch New BookingsWatches whether new bookings are created.
- Watch New EventsWatches whether new events are created.
- Watch New SessionsWatches whether new sessions are created and returns them.
- Watch Updated EventsTriggers when events are updated.
Bookwhen modules
- Get a Class PassRetrieves the details of a single class pass by its ID.
- Get a LeaderRetrieves the details of a single leader by its ID.
- Get a LocationRetrieves the details of a single location by its ID.
- Get a TicketRetrieves the details of a single ticket by its ID.
- Get an AttachmentRetrieves the details of a single attachment by its ID.
- Get an EventRetrieves the details of a single event by its ID.
- List AttachmentsRetrieves a list of attachments, with optional filtering.
- List Class PassesRetrieves a list of class passes, with optional filtering.
- List EventsRetrieves a list of events, with optional filtering.
- List LeadersRetrieves a list of leaders, with optional filtering.
- List LocationsRetrieves a list of locations, with optional filtering.
- List TicketsRetrieves a list of tickets, with optional filtering.
- Make an API CallPerforms an arbitrary authorized API call to the Bookwhen API.
Frequently asked questions
Common questions about connecting Bookwhen and Sessions.
Connect your Bookwhen and Sessions accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Sessions's "Watch New Bookings" fires, WEXTL can "Get a Class Pass" in Bookwhen. Bookwhen has 13 actions (including Get a Class Pass, Get a Leader, and Get a Location); Sessions has 11 actions (including Create a Room, Create a Session, and Delete a Session). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Bookwhen-to-Sessions automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Bookwhen (or Sessions) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Bookwhen + Sessions automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Bookwhen and Sessions integration.
- Bookwhen and Sessions integration source code, module specs and credentials implementation.
- Our Bookwhen and Sessions integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Bookwhen and Sessions — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Bookwhen integration information
- Sessions integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library