Amelia and Sympla Integration

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

Keep Amelia and Sympla matched by integrating their events and actions. When scheduling events happen in Amelia, update the Sympla automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Amelia and Sympla

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

  • Amelia

    • Scheduling
    • 13 triggers
    • 24 searches
    • 67 actions

    WordPress booking and appointment scheduling for services and events.[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 Amelia to Sympla

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

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

WEXTL exposes actions and triggers for Amelia 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.

Amelia triggersSympla actions

Amelia modules

  • Add a Package Appointment Books an appointment that uses a package, for a Service, a Provider and a Location. Add Bookings for the customers, set Booking Start for the time, and turn on Create Payment Links to create payment links.
  • Add a Package to a Customer Assigns a package to a customer. Output includes the Package customer ID and the Payment ID. Turn on Notify to notify the customer.
  • Cancel a Booking Cancels a booking in Amelia. Output includes the Booking, the Old appointment and whether the Old appointment status changed.
  • Check Calendar Event Conflicts Checks calendar conflicts across Periods for Providers. Use Event IDs to leave events out of the search.
  • Check the Effect of Deleting an Event Asks Amelia what deleting an event would affect and returns Valid with its Message.
  • Create a Booking Books an appointment at a Location ID, for a Provider ID and Service ID, starting at Booking Start Date and Time. Use Recurring Appointments to add the repeat appointments.
  • Create a Category Creates a service category. Use Category Name to name it, Position to place it in the sort order, Color for a hex color and Status to show or hide it.
  • Create a Coupon Makes a discount coupon under a Code with a usage Limit. Fill Discount for a percentage off or Deduction for a fixed amount, narrowed by Services, Events, Packages, Start Date and Expiration Date.
  • Create a Custom Field Adds a custom field of a given Type to the booking form. Use Options for select and radio types, Services or Events to say where it is used, and Required to mark it required.
  • Create a Location Sets up a place where services are offered under a Location Name. Add its Address, Phone, Latitude and Longitude, plus a Pin Icon Path for the map pin.
  • Create a Notification Creates a notification template for email, SMS or WhatsApp, sent to customers or providers. Set Time Before or Time After to send it that many seconds around an appointment or event, and Entity IDs to limit it to certain services or events.
  • Create a Package Creates a package from Bookable Services under a Package Name, Description and Price. Give it Duration Type and Duration Count for the expiry, and Limit Per Customer to cap what each customer buys.
  • Create a Package Booking Books a package for a Location ID, a Provider ID and a Service ID. Use Coupon Code to apply a discount and Run Instant Post Booking Actions to run the post booking actions in this call.
  • Create a Payment Records a payment against a Customer Booking ID, with the Amount, Gateway and Status. Add a Transaction ID for the online gateway reference and a WooCommerce Order ID to link a store order.
  • Create a Payment Link Generates a payment link for a booking or a package purchase. Use Redirect URL to set where the customer goes after paying. Output includes the Payment link.
  • Create a Resource Creates a resource with a Name for internal use and a Quantity. Use Shared to share it by service or location and Entities to tie it to specific entities.
  • Create a Service Defines a bookable service with a Service Name, Category ID, Providers, Service Duration, capacity limits and Price. Attach add-ons through Extras and ask for an upfront part of the price with Deposit.
  • Create a User Registers a customer by First Name, Last Name and a unique Email. Add a Birthday, Gender, Language or Note to complete the profile.
  • Create an Employee Registers a provider by First Name, Last Name, Email and Location ID. Use Service List for the services they offer and turn on Send Employee Panel Access Email to send the access email.
  • Create an Event Creates an event with an Event Name, Periods, Maximum Capacity and Price. Set Booking Opens and Booking Closes for the booking window, and Organizer ID for the employee who organizes it.
  • Create an Event Booking Books a customer onto an event with a payment. Use Coupon Code to apply a discount.
  • Create an Extra Creates an extra for a service with an Extra Name and Extra Price. Use Maximum Quantity to cap the quantity and Aggregated Price to multiply the price by persons.
  • Delete a Booking Deletes a booking in Amelia. Output includes the Booking and the Old appointment.
  • Delete a Category Removes a service category from the Amelia catalog.
  • Delete a Coupon Deletes a discount coupon. Output includes the Code and Discount of the coupon.
  • Delete a Custom Field Removes a custom field that appears on the booking form.
  • Delete a Customer Package Deletes a customer package purchase from Amelia.
  • Delete a Location Deletes a location and returns its Name and Address.
  • Delete a Location Effect Checks whether a location can be deleted. Output includes Valid and a Message.
  • Delete a Notification Removes a notification template and returns its Custom name and Type.
  • Delete a Package Deletes a package from the Amelia catalog.
  • Delete a Package Effect Previews deleting a customer package and returns Valid with a Message.
  • Delete a Payment Removes a recorded payment and returns its Amount and Gateway.
  • Delete a Resource Removes a bookable resource from your Amelia setup.
  • Delete a Service Deletes a service from your Amelia booking setup.
  • Delete a User Removes a customer profile from Amelia.
  • Delete a User Effect Checks whether a customer can be deleted, with a Valid flag and a Message in the output.
  • Delete an Employee Deletes a provider from your Amelia employee list.
  • Delete an Event Deletes an event and returns its Name and Price.
  • Delete an Extra Deletes an extra, returning its Name and Max quantity.
  • Get a Category Fetches one service category by Category ID, showing its Name, Status, Position and Service list.
  • Get a Coupon Loads a coupon by Coupon ID with its Code, Discount, Deduction and the number of times it was Used.
  • Get a Location Looks up one location by Location ID, returning its Name, Address, Phone and Latitude.
  • Get a Service Returns one service by Service ID, including its Name, Description, Color, Price and Deposit.
  • Get a User Shows a customer by User ID with their First name, Last name, Email, Phone and Status.
  • Get an Employee Fetches a provider by Employee ID, returning their First name, Last name, Birthday, Email and Phone.
  • Get an Event Retrieves one event by Event ID with its Name, Description, Color, Price and Deposit.
  • Get an Extra Gets an add-on by Extra ID, giving its Name, Price, Max quantity, Position and Duration.
  • List Categories Returns the service categories, each with its Name, Status, Position and Service list. Use Limit to shorten the list.
  • List Coupons Shows your discount coupons, with the Code, Discount or Deduction, usage Limit and how many times each was Used.

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 Amelia and Sympla integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Amelia and Sympla on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Amelia and Sympla.

How do I connect Amelia and Sympla?

Connect your Amelia 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 Amelia and Sympla?

Example: when the "Watch Categories" trigger in Amelia fires, WEXTL can "Check In a Participant" in Sympla. Amelia has 13 triggers (including Watch Categories, Watch Coupons, and Watch Custom Fields). 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 Amelia trigger actions in Sympla, and Sympla in Amelia?

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 Amelia and Sympla?

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

Does Amelia integrate with Sympla in real time?

Yes. Trigger-based automations start the moment Amelia (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 Amelia + 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 Amelia with Sympla?

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

References

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

  1. Amelia and Sympla integration source code, module specs and credentials implementation.
  2. Our Amelia and Sympla integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Amelia 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. Amelia 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 Amelia and Sympla integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Amelia and Sympla, or get started