STEP 1
Connect Bookwhen and MotionSoft
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 MotionSoft Integration
Keep Bookwhen and MotionSoft in sync by integrating their events and actions. When scheduling events happen in Bookwhen, update the MotionSoft automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Bookwhen and MotionSoft
Detailed info you need to know about Bookwhen and MotionSoft integrations in WEXTL. Explore which modules apps support and how you connect them.
Bookwhen
Online booking and scheduling for classes, courses, and events — with tickets, attendees, and calendars. [5]
MotionSoft
Club management software for memberships and scheduling. [6]
How to connect Bookwhen to MotionSoft
Set up your Bookwhen and MotionSoft integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Bookwhen and MotionSoft 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 MotionSoft. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Bookwhen and MotionSoft work in WEXTL?
WEXTL exposes actions and triggers for Bookwhen and MotionSoft 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.
MotionSoft triggersBookwhen actions
MotionSoft modules
- Get Employee Config ValuesReturns a single employee config values.
- Get Employee DetailsRetrieve details about a specific employee.
- Get Enterprise Config ValuesReturns a single enterprise config values.
- Get Member DetailsRetrieve details about a specific member.
- Get Member SummaryRetrieves member summary.
- Make an Api CallMakes API call.
- Search Checkin HistorySearches for checkin history by the given criteria.
- Search EmployeesSearch for employees based on the provided criteria.
- Search Employees by LocationGet employees by location and selected service.
- Search MembersRetrieves a list of members.
- Search Scheduler ServicesRetrieves a list of scheduler services.
- Search Service TypesRetrieves a list of service types.
- Update MemberUpdates an existing member.
- Watch CheckinTriggers when new checkin are created.
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 MotionSoft.
Connect your Bookwhen and MotionSoft 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 MotionSoft's "Watch Checkin" 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); MotionSoft has 13 actions (including Get Employee Config Values, Get Employee Details, and Get Enterprise Config Values). 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-MotionSoft 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 MotionSoft) 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 + MotionSoft 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 MotionSoft integration.
- Bookwhen and MotionSoft integration source code, module specs and credentials implementation.
- Our Bookwhen and MotionSoft integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Bookwhen and MotionSoft — 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
- MotionSoft integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library