Connect Pretix and Whippy

Both apps 36Pretix 12Whippy 24

• Trigger
  New order

  Triggered when a new order is placed for a Pretix event.

• Action
  Add event

  Creates a new event under a pretix organizer. Events are always created as not live; add quotas and payment methods before going live.

• Action
  Add order

  Creates a new order in a pretix event, e.g. to import attendees from an external source.

• Action
  Add voucher

  Creates a new voucher in a pretix event.

• Action
  Add waiting list entry

  Adds a person to the waiting list for a product of a Pretix event.

• Action
  Get order

  Returns one order of an event, identified by its order code, including positions, fees, payments, refunds and invoice address.

• Action
  Get voucher

  Returns one voucher of an event with its code, usage limit and tag.

• Action
  Get waiting list entry

  Returns one waiting list entry of an event: the email address and the product it waits for.

• Action
  List events

  Returns all events of an organizer, optionally filtered.

• Action
  List items

  Returns the items (products) of a Pretix event, optionally filtered by name, category, active, admission, tax rate or free-price flag.

• Action
  List order positions

  Lists the order positions (tickets and products) within an event, with optional filters.

• Action
  List orders

  /api/v1/organizers/{organizer}/events/{event}/orders/ - list orders of an event.

• Trigger
  Channels

  Triggers when a new channel is added to your Whippy organization.

• Trigger
  List Agents

  Triggers when a new AI agent is added to your Whippy organization.

• Trigger
  List Calls

  Triggers when a new call is logged in Whippy.

• Trigger
  List Users

  Triggers when a new user is added to your Whippy organization.

• Action
  Add Contacts to a Sequence

  Adds contacts to a Whippy sequence, creating any contact that does not exist yet.

• Action
  Create a Contact

  Creates a new contact in Whippy from a phone number, with optional name, email and opt-in preferences.

• Action
  Delete a Contact

  Deletes a contact from Whippy by its ID.

• Action
  Get Agent by ID

  Returns one Whippy AI agent by its ID, including its current version and settings.

• Action
  Get All Campaigns

  Returns the campaigns in your Whippy organization, optionally filtered by title.

• Action
  Get All Channels

  Returns the channels (phone numbers, email addresses and other locations) in your Whippy organization.

• Action
  Get All Contacts

  Returns the contacts in your Whippy organization, optionally filtered by name, email or phone.

• Action
  Get All Sequences

  Returns the sequences in your Whippy organization, optionally filtered by title.

• Action
  Get All Sequence Steps

  Returns all the steps of a Whippy sequence, including each step's message and delivery stats.

• Action
  Get Call by ID

  Returns one Whippy call by its ID, including its recording and transcript links.

• Action
  Get Campaign by ID

  Returns one Whippy campaign by its ID.

• Action
  Get Campaign Contacts

  Returns the contacts a Whippy campaign was sent to, with optional filters for delivery, responses, unsubscribes and link clicks.

• Action
  Get Contact by ID

  Returns one Whippy contact by its ID.

• Action
  Get Contacts in a Sequence

  Returns the contacts enrolled in a Whippy sequence, with optional filters for status, step, responses, unsubscribes and link clicks.

• Action
  Get Sequence by ID

  Returns one Whippy sequence by its ID.

• Action
  List Agents

  Returns the AI agents in your Whippy organization, optionally filtered by name.

• Action
  List Calls

  Returns calls in your Whippy organization, optionally limited to a date range.

• Action
  List Users

  Returns the users in your Whippy organization, optionally filtered by name, email, phone, role or state.

• Action
  Send an SMS

  Sends an SMS text message from one of your Whippy channels to a phone number.

• Action
  Update a Contact

  Updates an existing Whippy contact's details such as name, email, phone or opt-in preferences.

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