Sessions and Sympla Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build scheduling workflows between Sessions and Sympla 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 trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Sessions and Sympla

Detailed info you need to know about Sessions and Sympla integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Sessions

    • Scheduling
    • 4 triggers
    • 5 searches
    • 6 actions

    Video session platform for bookings, invites, and meeting transcripts.[5]

  • Sympla

    • Scheduling
    • 2 triggers
    • 13 searches
    • 4 actions

    Event ticketing platform for managing events, orders, ticket holders and check-ins.[6]

How to connect Sessions to Sympla

Set up your Sessions and Sympla integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Sessions and Sympla work in WEXTL?

WEXTL exposes actions and triggers for Sessions and Sympla that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Sessions triggersSympla actions

Sessions modules

  • Create a Room Adds a room to Sessions from its Name and Slug. Afterwards the ID, Active flag and Session Template ID of the new room are available to later steps.
  • Create a Session Books a session with a Name, a Start at and a Planned End. Add Participants to invite people straight away, or Reminders to set when they are told. Set Quick Session to mark it as a quick session.
  • Delete a Session Deletes a session entry from the Sessions platform.
  • Get a Session Looks up a single session and gives its Name, Lifecycle, Start at, Planned End, Time Zone and Description.
  • Get a Transcript Retrieves what was said in a session, as entries with a Source Language, Participant ID and Content.
  • Invite to a Session Adds people to a session. Fill Participants with a First Name, Last Name and Email for each person, and turn on Is Assistant to add someone as an assistant.
  • List Bookings Lists bookings with their Name, Session ID, Start at, Planned End and Session Link. Use Limit to cap the number of results.
  • List Session Invitees Gets the participants of a session, each with a Status, an Invite Status and a Has Attended Session flag. Use Limit to choose the count.
  • List Sessions Returns sessions with their Name, Lifecycle, Start at and Planned End. Use Search to run a fulltext search such as John Doe, and Limit to bound how many are fetched.
  • Make an API Call Makes an authorized free-form request to the Sessions REST API with your saved credential.
  • Update a Session Alters a session by editing its Name, Start at, Planned End or Time Zone. Use Reminders and Participants to adjust the invitations and notices attached to it.
  • Watch New Bookings Checks for newly created bookings at each scheduled run and emits every one it finds. Set Limit to cap how many a run handles.
  • Watch New Events Polls on a schedule and fires once for each newly created event, giving its Slug, State and Access Type. Use Limit to bound the batch per run.
  • Watch New Sessions Looks for sessions created since the last scheduled check and emits each with its Name and Start At. Use Limit to restrict how many a run processes.
  • Watch Updated Events Triggers on a schedule for events that are new or updated, including their Session ID. Use Limit to cap the events taken per cycle.

Sympla modules

  • Check In a Participant Marks a ticket holder as arrived at an event, using their Participant ID. It returns the Check In ID and Check In Date.
  • Check In a Participant by QR Code Validates the data of a ticket QR code, that is the Item ID, Wallet ID, Signature, Timestamp and Version, and checks the holder in.
  • Check In a Participant by Ticket Number Marks the holder of a ticket as arrived using the Ticket Number printed on it, with no Participant ID involved.
  • Get a Participant Shows a ticket holder with their Ticket Status, Email and Ticket Number. List Participants gives the IDs to use.
  • Get a Participant by Ticket Number Finds a ticket holder from the Ticket Number printed on the ticket and returns their Ticket Status and Order ID.
  • Get an Event Reads one event with its Name, Start Date, End Date and Address. Set Time Zone to see the dates in your zone.
  • Get an Event Presentation Looks up one session of an event and shows its Start Date, whether it is Enabled and whether it is Closed.
  • Get an Order Retrieves one order of an event, with its Order Status, Order Total Sale Price and Buyer Email. The IDs are listed by List Orders.
  • List Affiliates Shows the affiliates who sell an event, with their Discount Code, Sold Tickets and Sales. The event number comes from the older Sympla API, not from the other modules.
  • List Event Presentations Fetches the sessions of an event. Turn on Published Only or Only Sectors On Sale Online to narrow the list, and use From to list sessions from a date on.
  • List Events Returns the events you organize on Sympla. Use Published to filter by publication status, From for events starting on or after a date and Sort By with Sort to set the order.
  • List Order Participants Gathers the ticket holders that belong to one order. Use Cancelled to include or hide cancelled items.
  • List Orders Pulls the orders of an event. Use From and To to limit them by date and Buyer Email to find the orders of one buyer.
  • List Participants Collects the ticket holders of an event. Use Participant Email to find one person and Updated From and Updated To to limit them by when the ticket changed.
  • List Presentation Orders Retrieves the orders placed for a single session. Use Cancelled to include cancelled items and Buyer Email to narrow them to one buyer.
  • List Presentation Participants Lists the ticket holders of one session. Use Participant Email to look for one person, or Updated From and Updated To to catch recent ticket changes.
  • Make an API Call Runs a free-form request against the Sympla REST API using your saved credential.
  • Watch New Orders Polls an event and runs the workflow once per order added since the last poll. Use Time Zone to read its dates in your zone.
  • Watch Participants Polls an event at your chosen interval. Each ticket holder who is new or updated since the last poll fires its own run.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Sessions and Sympla integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Sessions and Sympla on WEXTL®

Claim your 3-day trial to build Sessions with Sympla integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Sessions and Sympla.

How do I connect Sessions and Sympla?

Connect your Sessions and Sympla 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]

What can I automate between Sessions and Sympla?

Example: when the "Watch New Bookings" trigger in Sessions fires, WEXTL can "Check In a Participant" in Sympla. Sessions has 4 triggers (including Watch New Bookings, Watch New Events, and Watch New Sessions). Sympla has 17 actions (including Check In a Participant, Check In a Participant by QR Code, and Check In a Participant by Ticket Number). Add filters and transforms between steps when you need them.[1]

Can Sessions trigger actions in Sympla, and Sympla in Sessions?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Sessions and Sympla?

No. Sessions-to-Sympla automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Sessions integrate with Sympla in real time?

Yes. Trigger-based automations start the moment Sessions (or Sympla) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Sessions + Sympla integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Sessions with Sympla?

You can build your Sessions + Sympla automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Sessions and Sympla integration.

  1. Sessions and Sympla integration source code, module specs and credentials implementation.
  2. Our Sessions and Sympla integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Sessions and Sympla, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Sessions integration information
  6. Sympla integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Sessions and Sympla integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Sessions and Sympla, or get started