Connect Swarmtix to Conrad

Both apps 25Swarmtix 24Conrad 1

• Trigger
  New Event

  Triggers when a new event appears in your Swarmtix organisation.

• Action
  Create Access Code

  Creates an access code that unlocks a hidden ticket type on an event at its normal price.

• Action
  Create Checkout Question

  Adds a custom question an event asks buyers during checkout, and returns the stored question.

• Action
  Create Discount

  Creates a discount on a Swarmtix event, either a code buyers type at checkout or a public offer shown on the event page, taking an amount or a percentage off.

• Action
  Create Event

  Creates a new Swarmtix event as an unpublished draft and returns its id and URL slug.

• Action
  Create Ticket Type

  Adds a ticket type (a price tier buyers choose from) to a Swarmtix event and returns it.

• Action
  Delete Checkout Question

  Removes a checkout question from an event so buyers are no longer asked it. Answers buyers already gave stay with their orders.

• Action
  Delete Discount

  Switches off a discount, public discount or access code on an event so it can no longer be used. The offer is kept because orders that used it still point at it.

• Action
  Delete Ticket Type

  Permanently deletes a ticket type nobody has ordered from an unpublished event, and returns the ticket types that remain.

• Action
  Duplicate Event

  Copies an event's setup into a new unpublished draft, without its dates, orders or attendees, and returns the new event.

• Action
  Get Analytics Summary

  Returns an organisation-wide roll-up of events, tickets sold and orders placed, plus the connected organizer account's lifetime gross ticket revenue per currency.

• Action
  Get Event

  Returns one Swarmtix event in full: schedule, location, host, ticket types and publication status.

• Action
  Get Event Analytics

  Returns the sales and traffic figures for one event: revenue, tickets sold, refunds, page visits and the daily series behind them.

• Action
  Get Ticket Sales Summary

  Returns how many tickets were put on sale, sold and checked in for one scheduled date of a Swarmtix event (the earliest date when none is given).

• Action
  List Checkout Questions

  Returns the custom questions an event asks buyers at checkout, with each question's wording, field name, and whether it is enabled and required.

• Action
  List Discounts

  Returns the active discount offers on an event, with their codes, reductions, dates and usage.

• Action
  List Event Dates

  Returns the scheduled dates of a Swarmtix event, earliest first, with each date's id, local and UTC start and end, capacity and active status.

• Action
  List Events

  Returns the Swarmtix events this connection can see, alphabetically by name, with each event's id, slug, name, city, country and scheduled dates.

• Action
  List Ticket Types

  Returns the ticket types an event sells, with price, quantity, remaining availability, per-order limits and sale window.

• Action
  Set Event Dates

  Replaces the full list of dates a Swarmtix event runs on and returns the resulting schedule. Refuses to drop a date that already has tickets sold.

• Action
  Update Checkout Question

  Changes one of an event's checkout questions (wording, answer type, choices, required, enabled, shown on ticket) and returns the question as stored. Only the fields you fill in are changed.

• Action
  Update Discount

  Changes an event's discount code, public discount or access code — its code, name, reduction, ticket type, window or usage limit — and returns the discount as stored.

• Action
  Update Event

  Updates an event's details such as name, description, venue, address, visibility, fees and timezone, and returns the event as stored afterwards. Fields left blank keep their current values.

• Action
  Update Ticket Type

  Changes one of an event's ticket types (name, price, quantity, limits, sale window) and returns it as stored afterwards. Fields left blank keep their current values.

• Action
  Find User

  Finds a Conrad user by ID, username, or email. Supply at least one; priority is ID, then username, then email.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.