Skip to main content

Eventbrite to iPaaS.com Order Mapping Documentation

How Eventbrite orders transfer to iPaaS.com as Order transactions, with the buyer as customer and one line per ticket whose status follows the attendee's check-in.

Summary

Eventbrite orders can be transferred to iPaaS.com as Transaction records of type Order through Eventbrite webhooks, an order refresh after an attendee checks in or changes, an initialization run, or Manual Sync. Each order is a registration: one buyer, one event, one or more tickets. The transaction carries the order number, the buyer as its customer, Eventbrite's totals and the event's details, and each ticket becomes one transaction line through the child collection Add/Update Eventbrite Order Ticket TO iPaaS.com, whose status is that attendee's attendance. Answers to the event's custom registration questions become transaction notes through Add/Update Eventbrite Order Answer TO iPaaS.com, and the order's taxes become transaction taxes through Add/Update Eventbrite Order Cost Component TO iPaaS.com.

ID Format

Manual Sync ID Format

Enter the Eventbrite order number, as shown in Eventbrite (example: 16096958843). The integration reads the order, with its tickets, its event and its answers, from Eventbrite and transfers it to iPaaS.com. Ticket lines, notes and taxes cannot be sent on their own: resend the order to update them.

External ID Format

After a successful transfer, iPaaS.com saves the Eventbrite order number as the external ID on a dedicated external ID record (example: 16096958843). That link is how later transfers of the same order update the same transaction instead of creating a new one. The order number is also mapped into TransactionNumber for visibility.

Each ticket line is saved with the order number and the Eventbrite attendee id joined by a vertical bar as its external ID link (example: 16096958843|22902212230), so a later transfer updates the same line.

Deleted Record Support

Delete is not supported: this collection only adds and updates transactions, and no delete mappings are included in the default template. A cancelled or refunded order keeps its transaction, with the matching status (see System Caveats). A transfer for an order that Eventbrite no longer has writes nothing.

Custom Field Support

The default template writes the transaction custom fields Eventbrite Event Id, Eventbrite Event Name, Eventbrite Event Start, Eventbrite Fee, Eventbrite Currency and Eventbrite Order Status; the child collection Add/Update Eventbrite Order Ticket TO iPaaS.com writes the line custom fields Eventbrite Attendee Status, Eventbrite Checked In, Eventbrite Attendee Email, Eventbrite Attendee Name and Eventbrite Ticket Class (see the field tables below). Keep Eventbrite Event Id and its exact name: the exclusion condition for other systems' outbound collections relies on it.

Answers to the event's custom registration questions can be added with a Dynamic Formula mapping that calls the EventbriteAnswer mapping function, for example return EventbriteAnswer(Answers, "Dietary requirements");. On an order, it returns the first answer to that question on the order (the buyer's, then each attendee's); every answer is also written as a note by Add/Update Eventbrite Order Answer TO iPaaS.com. See Eventbrite Mapping Functions for the function.

Mapping Collection Status

  • Status: Enabled. The filter lets every Eventbrite order through and keeps attendance records out.

  • Trigger Events: the order.placed, order.updated and order.refunded webhook scopes, turned on in the subscription's Inbound Data Flows section; an order refresh after attendee.updated, attendee.checked_in or attendee.checked_out (scopes of Add/Update Eventbrite Attendee TO iPaaS.com) when the order is already in iPaaS.com; the transaction/initialize run; and Manual Sync by order number.

When a webhook scope is turned on, the integration registers the matching webhook in Eventbrite itself, and it removes the webhook when the scope is turned off. No automatic transfers occur until the scopes are turned on. Whether a transfer adds or updates the transaction depends on whether the order is already linked by its external ID, not on which scope fired.

Scope

What triggers it

order.placed

A new Eventbrite order

order.updated

An Eventbrite order changed

order.refunded

An Eventbrite order was refunded

transaction/initialize

An initialization run: every order changed in the last Initialization Days days; one run reads at most about 10,000 orders

Duplicate or Conflicting Mappings

Orders and attendance records

Add/Update Eventbrite Attendance TO iPaaS.com also writes iPaaS.com transactions from the same Eventbrite data: one attendance record per person per event. The two collections' filters send each record to exactly one of them (see Mappings). Keep both conditions in any filter you write.

Other systems' order flows

Eventbrite orders are iPaaS.com transactions, so the transaction collections FROM iPaaS.com of your other systems (for example a store, ERP, point of sale or donor database) can pick them up. On any such collection that must not receive event registrations, add this condition to its filter: string.IsNullOrEmpty(Convert.ToString(GetCustomFieldValue(CustomFields, "Eventbrite Event Id"))). For example, an empty filter becomes return string.IsNullOrEmpty(Convert.ToString(GetCustomFieldValue(CustomFields, "Eventbrite Event Id")));. Keep the Eventbrite Event Id mapping in this collection, because the condition relies on it. Attendance records carry Eventbrite Event Id too, so the same condition keeps them out. Subscribers should validate this behavior in a staging environment before relying on it in production.

Important: Review the filters and Add/Update settings of every transaction collection in your company before enabling this collection, and decide which systems are the source of truth for event registrations.

Order lines and attendance lines

Add/Update Eventbrite Attendance Ticket TO iPaaS.com writes the same Eventbrite tickets again, as lines with no amounts on each person's attendance record. Its lines are linked by the event id and the attendee id, so they never share a link with the order's lines. Important: Put the same SKU in the Sku mapping of both collections, and keep UnitPrice and ExtendedPrice at 0 in the Attendance Ticket collection, so each ticket's revenue is counted once, on the order's line.

Record Matching and Duplicates

This collection has no Collision Handling Method, and the integration does no record matching for orders. iPaaS.com saves the order number as the external ID on a dedicated external ID record, which is how later updates find the transaction. The order number is also mapped into TransactionNumber; if another transaction already holds that value, iPaaS.com refuses the transfer as a duplicate rather than linking to it. Keep one Eventbrite subscription per Eventbrite organization. Subscribers should validate this behavior in a staging environment before relying on it in production. Resending an order, a repeated webhook or a second initialization run updates the same transaction and lines and never creates a second one.

Unmapped Field Overwrite Risk

Warning — Unmapped Field Overwrite Risk: An update replaces the whole iPaaS.com transaction, lines included. Every transaction field subscribers can map is mapped in Add/Update Eventbrite Order TO iPaaS.com; the unmapped ones (Id, ParentId and CompanyId) are identifiers iPaaS.com manages. The following line fields are not mapped in Add/Update Eventbrite Order Ticket TO iPaaS.com, so any existing value in them on an Eventbrite ticket line is cleared each time the order transfers again:

  • DiscountAmount

  • DiscountPercent

  • EstimatedTaxAmount

  • LineInfo

  • OriginalUnitPrice

  • QtyShipped

  • SequenceNumber

  • TaxPercent

  • Weight

If another system or a user fills any of these fields on Eventbrite ticket lines, add a Dynamic Formula mapping to the Order Ticket collection that keeps the existing value with the DestinationValue function, in the same form as the order's ShippingAmount mapping, for example return DestinationValue != null ? DestinationValue.DiscountAmount : 0; for DiscountAmount. Subscribers should validate this behavior in a staging environment before relying on it in production.

Supported Child Collections

  • Add/Update Eventbrite Order Ticket TO iPaaS.com: one transaction line per ticket (attendee), with the ticket's attendance as the line status. Each line is saved with the order number and the attendee id as its external ID link.

  • Add/Update Eventbrite Order Answer TO iPaaS.com: one transaction note (type Customer Note) per answer to the event's custom registration questions. Questions nobody answered are skipped by its filter.

  • Add/Update Eventbrite Order Cost Component TO iPaaS.com: one transaction tax per tax on the order. Its filter keeps Eventbrite's fees and shipping charges out of the taxes.

The children always accompany the parent order transfer; they are never transferred on their own.

System Caveats

Eventbrite Caveats

  • Order state: the integration works out the order's state from its tickets: Placed while any ticket is still held, Refunded when every ticket was refunded, and otherwise Cancelled. Cancelling one ticket of a multi-ticket order changes only that ticket's line (to Refunded for a free ticket); the order stays Placed and the transaction Complete.

  • Cancelled free orders: in the orders observed when this documentation was written, Eventbrite recorded a cancelled free order as refunded, so the transaction, Eventbrite Order Status and every line become Refunded. A later order.refunded transfer updates the same transaction.

  • Ticket attendance: a ticket is Refunded when Eventbrite marks it refunded; otherwise Cancelled when it was cancelled or Eventbrite reports it as not attending or deleted; otherwise Attended when it was checked in or its barcode was used; otherwise Registered. After a check-in is undone or the attendee is checked out in Eventbrite's organizer screens, the line returns to Pending and Eventbrite Checked In becomes false; in the check-ins observed when this documentation was written, Eventbrite recorded an undo and a check-out the same way. If Eventbrite still reports the barcode as used after a check-out, the ticket still counts as attended.

  • Amounts: the Total, Subtotal, TaxAmount, DiscountAmount and Eventbrite Fee figures are Eventbrite's own, as Eventbrite reports them, and are 0 on a free order. No payment record is written. Subscribers who sell paid tickets should validate this behavior on a paid order in a staging environment before relying on it in production.

  • Buyer-only events: as the Eventbrite API reference describes (Attendee object), when the event collects details from the buyer only, every ticket line carries the buyer's name and email address.

  • Rate limiting: Eventbrite allows a default of 2,000 API calls per hour per private token, shared by everything that uses the token. When the limit is reached, iPaaS.com holds the transfer and sends it automatically once the hour resets; no subscriber action is required. Use one Eventbrite private token per iPaaS.com subscription.

iPaaS.com Caveats

  • Event-ticket product: every ticket line names an iPaaS.com product by its SKU, and iPaaS.com refuses a line whose SKU is not an existing product. Until the Sku mapping of the Order Ticket collection holds the SKU of an existing product, every order transfer is refused with NFND-1003 ("Product Id: REPLACE with your event ticket SKU does not exist or can not be found."); the buyer and attendees on the order are still sent as customers.

  • Customer: the transaction's customer is the one iPaaS.com customer with the buyer's email address. When several iPaaS.com customers share that email address, no customer is set and the transaction still carries the buyer's email address; merge or correct the customers, then resend the order from Manual Sync. When the buyer has no email address, no customer is set either. Subscribers should validate this behavior in a staging environment before relying on it in production.

  • People on the order: a person without an email address is not sent as a customer, and their ticket still becomes a line; the order transfer logs nothing for them. When that person's own attendee transfer runs, its activity log shows a warning (see Error Handling). A person whose transfer fails does not stop the order (a warning naming the person; see Error Handling).

  • Event Start format: at the time this documentation was written, Eventbrite Event Start appears in iPaaS.com as a US-formatted date and time (for example 03/15/2027 10:00:00), not in ISO 8601 form. It is in the event's local time, with no time zone.

Setup Requirements

For the integration-wide setup (the Eventbrite private token, the Organization Id and Initialization Days settings) see the Eventbrite Installation Instructions and Eventbrite Connections and Settings articles; it is not repeated here.

Eventbrite Configuration

No setup is needed in Eventbrite for this collection: the integration registers its own webhooks in your Eventbrite organization when the scopes are turned on.

iPaaS.com Configuration

  1. Create the event-ticket product in iPaaS.com (for example, SKU EVENT-TICKET, named Event ticket), or choose an existing product, and put its SKU in the Sku mapping of Add/Update Eventbrite Order Ticket TO iPaaS.com and of Add/Update Eventbrite Attendance Ticket TO iPaaS.com.

  2. In the subscription's Inbound Data Flows section, turn on the order.placed, order.updated and order.refunded scopes, and the attendee scopes of Add/Update Eventbrite Attendee TO iPaaS.com so that check-ins update the ticket lines.

  3. To bring in recent orders, turn on the transaction/initialize scope and run the initialization from the subscription.

  4. Add the Eventbrite exclusion condition (see Duplicate or Conflicting Mappings) to every transaction collection FROM iPaaS.com that must not receive event registrations. Subscribers should validate this behavior in a staging environment before relying on it in production.

Integration Flow

When a webhook arrives, an order is refreshed, an initialization run reaches the order, or a Manual Sync is started, the integration processes the order in this order:

  1. Read the order. The integration reads the order from Eventbrite, with its tickets, its event and its answers, always fresh, and works out the order's state (Placed, Cancelled or Refunded) from its tickets and each ticket's attendance (Registered, Attended, Cancelled or Refunded). An order Eventbrite does not know writes nothing (see Error Handling). An order from another Eventbrite organization is skipped, with a warning in the activity log that names both organizations; if the Private Token or Organization Id setting changed, turn every webhook scope off and on again.

  2. Send the people first. The buyer, then each attendee whose email address has not already been seen on the order, is sent to iPaaS.com as a customer through Add/Update Eventbrite Attendee TO iPaaS.com, and each person's transfer then sends that person's attendance record for the event through Add/Update Eventbrite Attendance TO iPaaS.com. Every person transfer, whatever started it (a webhook scope, an initialization, an order's people or a Manual Sync), is followed by that person's attendance record for the event, unless no ticket at the event carries the person's email (cancelled and refunded tickets still count, giving a Cancelled or Refunded record), for example a buyer who bought tickets only for others. This step is skipped when the order transfer was started by an attendee check-in, check-out or change, because that person was just sent, and when the order is being refreshed on behalf of another record.

  3. Map the order. The record passes this collection's filter only when it is an order, not an attendance record. The order is mapped through this collection; the CustomerId formula finds the buyer's iPaaS.com customer by email address.

  4. Map the children. Each ticket is mapped through Add/Update Eventbrite Order Ticket TO iPaaS.com into one line, each answer through Add/Update Eventbrite Order Answer TO iPaaS.com into one note, and each tax through Add/Update Eventbrite Order Cost Component TO iPaaS.com into one transaction tax.

  5. Write to iPaaS.com. The transaction with its lines, notes and taxes is written TO iPaaS.com: as an update when the order is already linked by its external ID, otherwise as a new transaction.

After an attendee check-in, check-out or change, the attendee's own transfer refreshes the order when the order is already in iPaaS.com, so the ticket's line follows. If that refresh cannot be queued, a warning is logged and the line follows with the next change of the order.

Mappings

Add/Update Eventbrite Order TO iPaaS.com

iPaaS.com data type: Transaction

Mapping Filter:

// Orders only: Event Attendance records go to the Attendance collection.return RecordKind != "Attendance";

Filter Description: Eventbrite orders and each person's attendance records reach iPaaS.com through the same Eventbrite data, marked by RecordKind: Order or Attendance. Records whose RecordKind is not Attendance (every order) are processed. Attendance records are skipped by this collection, with no error, and are processed by Add/Update Eventbrite Attendance TO iPaaS.com. Keep this condition in any filter you write. To also skip cancelled orders, skip Refunded too, because, in the orders observed when this documentation was written, Eventbrite recorded a cancelled free order as refunded: return RecordKind != "Attendance" && OrderState != "Refunded" && OrderState != "Cancelled";. With that filter, an order already in iPaaS.com keeps its last status when it is cancelled or refunded, and an order the filter skips also sends none of its people.

Description: Transfers each Eventbrite order to iPaaS.com as a transaction of type Order, with the buyer as customer, Eventbrite's totals and the event's details.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Dynamic Formula

SpaceportSystemId

SystemId

Required. Links the transaction to this iPaaS.com subscription. Do not change it.

Field

Id

TransactionNumber

Required. The Eventbrite order number. iPaaS.com saves it as the external ID on a dedicated external ID record; it is mapped here for visibility and is the value the duplicate check compares (see Record Matching and Duplicates).

Static

"Order"

Type

Required. Every Eventbrite order is a transaction of type Order. Keep it: other systems' outbound transaction collections often select by type. Allowed values: Order, Shipment, Invoice, Hold, Quote, Ticket, Return, Validated Return, Job and Fulfillment.

Lookup Translation

Lookup Translation: Eventbrite Order State -> iPaaS.com Transaction Status

Status

Required. Translates the order's state (Placed, Cancelled or Refunded) to a transaction status. See the translation table below.

Field

BuyerEmail

EmailAddress

Required. The buyer's email address, in lowercase. iPaaS.com needs an email address on a transaction that has no customer.

Dynamic Formula

return await EventbriteCustomerId(BuyerEmail);

CustomerId

Required. Keep this mapping: it links the order to the buyer's own customer in iPaaS.com, found by email. The value can be empty (see CustomerId below the table).

Field

Gross

Total

Recommended. What the buyer paid, including fees and tax, as Eventbrite reports it (0 for a free order).

Field

BasePrice

Subtotal

Recommended. Ticket revenue before fees and tax.

Field

Tax

TaxAmount

Recommended. Tax collected on the order.

Field

TicketCount

TotalQty

Recommended. The number of tickets on the order, including cancelled and refunded tickets.

Field

DiscountAmount

DiscountAmount

Recommended. The order's discount, as Eventbrite reports it in the order's costs (0 when none). A discount entered in iPaaS.com is replaced on the next transfer. Subscribers should validate this behavior on a discounted order in a staging environment before relying on it in production.

Dynamic Formula

return DestinationValue != null ? DestinationValue.ShippingAmount : 0;

ShippingAmount

Required. Keeps the shipping amount the transaction already has (0 on a new transaction); the integration does not carry a shipping amount from Eventbrite. Removing it resets the amount to 0 on every update.

Dynamic Formula

return string.IsNullOrEmpty(Created) ? (DateTimeOffset?)null : DateTimeOffset.Parse(Created, System.Globalization.CultureInfo.InvariantCulture, System.Globalization.DateTimeStyles.AssumeUniversal);

TransactionCreatedDateTime

Recommended. When the order was placed; Eventbrite's UTC date text becomes a date. Empty when Eventbrite sends none.

Dynamic Formula

return string.IsNullOrEmpty(Changed) ? (DateTimeOffset?)null : DateTimeOffset.Parse(Changed, System.Globalization.CultureInfo.InvariantCulture, System.Globalization.DateTimeStyles.AssumeUniversal);

TransactionUpdatedDateTime

Optional. When the order last changed in Eventbrite. Empty when Eventbrite sends none.

Field

EventId

Eventbrite Event Id (Custom Field)

Required. Do not remove or rename it. The Eventbrite event id. It marks the transaction as an event registration; the exclusion condition for other systems' collections relies on it.

Field

EventName

Eventbrite Event Name (Custom Field)

Recommended. The event's name.

Field

EventStart

Eventbrite Event Start (Custom Field)

Recommended. At the time this documentation was written, Eventbrite Event Start appears in iPaaS.com as a US-formatted date and time (for example 03/15/2027 10:00:00), not in ISO 8601 form. It is the event's local start date and time, with no time zone. Add a Field mapping of EventTimezone to a custom field when receiving systems need the time zone.

Field

Fees

Eventbrite Fee (Custom Field)

Optional. Eventbrite's service fee and payment processing fee on the order, added together (0 for a free order).

Field

Currency

Eventbrite Currency (Custom Field)

Optional. The order's currency, for example USD.

Field

OrderState

Eventbrite Order Status (Custom Field)

Recommended. The order's state before translation: Placed, Cancelled or Refunded.

CustomerId: the one iPaaS.com customer with the buyer's email address; the buyer is sent as a customer first. When several iPaaS.com customers share the buyer's email address, the value is empty and the transaction is written with the email address only: merge or correct the customers, then resend the order from Manual Sync. It is also empty when the buyer has no email address. A failed lookup fails the transfer with a message that includes "Looking up the iPaaS.com customer with", and the transfer is retried.

Lookup Translation Tables

Eventbrite Order State -> iPaaS.com Transaction Status (used by the Status mapping)

Source Value (Eventbrite)

Destination Value (iPaaS.com)

Notes

Placed

Complete

At least one ticket is still held.

Cancelled

Cancelled

No ticket is held, and not every ticket was refunded.

Refunded

Refunded

Every ticket was refunded, including a cancelled free order.

The integration produces only these three states. Subscribers or their MiSP may change the destination values to the statuses their other systems expect. The translation has no default row. Keep a row for each of the three values. Status is required on every transaction, so a value with no translation row is refused by iPaaS.com: nothing is written, the transfer is refused, and Dashboard / Integration Monitoring / Error Logs shows an error that includes "VALD-1024 - Required property 'status' not found in JSON" with a link to the iPaaS.com help article Request body errors. To fix it, restore the translation row and resend the order from Manual Sync. Subscribers should validate this behavior in a staging environment before relying on it in production.

Add/Update Eventbrite Order Ticket TO iPaaS.com (Child)

iPaaS.com data type: Transaction Line

Description: Transfers each ticket of the parent order as one transaction line, as part of the parent order's transfer. Lines are never transferred on their own. Each line is saved with the order number and the attendee id as its external ID link. This collection has no mapping filter: every ticket of the order becomes a line, including cancelled and refunded tickets.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Static

"Product"

Type

Required. Every ticket line is a line of type Product, the event-ticket product named in Sku. Allowed values: Product, Gift Card and Donation.

Static

"REPLACE with your event ticket SKU"

Sku

Required. Placeholder value — replace during implementation. Replace with the SKU of the iPaaS.com product you use for event tickets, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product. The product MUST exist before the first transfer, or every order is refused with NFND-1003 (see the note below the table).

Lookup Translation

Lookup Translation: Eventbrite Ticket Attendance -> iPaaS.com Line Status

Status

Required. Translates the ticket's attendance (Registered, Attended, Cancelled or Refunded) to a line status. See the translation table below.

Field

TicketClassName

Description

Recommended. The ticket type's name, for example General Admission.

Field

Quantity

Qty

Required. Always 1: each ticket is one line, so keep this mapping for every line to carry its quantity.

Field

BasePrice

UnitPrice

Recommended. The ticket's price before fees and tax (0 for a free ticket).

Field

BasePrice

ExtendedPrice

Recommended. Equals the unit price, because the quantity is 1.

Field

AttendanceState

Eventbrite Attendee Status (Custom Field)

Recommended. The ticket's attendance before translation: Registered, Attended, Cancelled or Refunded.

Dynamic Formula

return Attended ? "true" : "false";

Eventbrite Checked In (Custom Field)

Recommended. true when Eventbrite reports the ticket as checked in or its barcode as used, else false. Becomes false again after an undo of the check-in or a check-out that resets the ticket (see Eventbrite Caveats).

Field

AttendeeEmail

Eventbrite Attendee Email (Custom Field)

Recommended. The attendee's email address, in lowercase; the buyer's on buyer-only events; empty when the attendee has none.

Field

AttendeeName

Eventbrite Attendee Name (Custom Field)

Recommended. The attendee's full name; the buyer's on buyer-only events.

Field

TicketClassName

Eventbrite Ticket Class (Custom Field)

Optional. The ticket type's name, kept in a custom field.

Placeholder value — replace during implementation: the Sku mapping ships with the instruction text "REPLACE with your event ticket SKU". Replace it with the SKU of the iPaaS.com product you use for event tickets, exactly as it is in iPaaS.com, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product in your iPaaS.com catalog.

Pre-install prerequisite — the transfer fails without it. iPaaS.com refuses a line whose SKU is not an existing iPaaS.com product. EITHER (a) create a product in iPaaS.com with the SKU you choose and put that SKU in the Sku mapping, OR (b) put the SKU of a product that already exists in your iPaaS.com catalog in the mapping. One of these MUST be done at install time. Until then, every order transfer fails with an error of this form in Dashboard / Integration Monitoring / Error Logs: "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found." The buyer and attendees on the order are still sent as customers. Put the same SKU in Add/Update Eventbrite Attendance Ticket TO iPaaS.com.

Lookup Translation Tables

Eventbrite Ticket Attendance -> iPaaS.com Line Status (used by the Status mapping)

Source Value (Eventbrite)

Destination Value (iPaaS.com)

Notes

Registered

Pending

The ticket is held and not checked in.

Attended

Complete

The ticket was checked in or its barcode was used.

Cancelled

Cancelled

The ticket was cancelled, or Eventbrite reports it as not attending or deleted, without a refund.

Refunded

Refunded

Eventbrite marks the ticket refunded, including a cancelled free order or a ticket cancelled on a free event.

The integration produces only these four values. Subscribers or their MiSP may change the destination values to the line statuses their other systems expect. The translation has no default row. Keep a row for each of the four values. Status is required on every transaction line, so a value with no translation row is refused by iPaaS.com: nothing is written, the transfer is refused, and Dashboard / Integration Monitoring / Error Logs shows an error that includes "VALD-1024 - Required property 'status' not found in JSON" with a link to the iPaaS.com help article Request body errors. To fix it, restore the translation row and resend the order from Manual Sync. Subscribers should validate this behavior in a staging environment before relying on it in production.

Add/Update Eventbrite Order Answer TO iPaaS.com (Child)

iPaaS.com data type: Transaction Note

Mapping Filter:

return Source != "question";

Filter Description: The integration sends a record for every answer to the event's custom registration questions, every survey response, and every question on the order form that nobody answered (marked by Source: answer, survey or question). The filter skips the unanswered questions, so a note is written only for a real answer. Remove the filter to also keep an empty note for each question that was not answered.

Description: Transfers each answer as one transaction note, as part of the parent order's transfer. Notes are never transferred on their own. Each note is saved with the order number, the attendee id and the question id joined by vertical bars as its external ID link (example: 16109466973|22904258288|324714990; the attendee id is empty for an answer to a question asked once per order).

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Field

Text

Text

Required. The question and the answer on one line, for example Dietary requirements: Vegetarian. An address answer arrives as one line of text; several choices are separated by commas.

Static

"Customer Note"

Type

Required. Every answer is a note of type Customer Note. Keep it: iPaaS.com refuses a transaction whose note has no type. Allowed values: Gift, Customer Note, Status, Order, Private, Job Note and Job Description.

Add/Update Eventbrite Order Cost Component TO iPaaS.com (Child)

iPaaS.com data type: Transaction Tax

Mapping Filter:

return Kind == "tax";

Filter Description: The integration sends a record for each charge in the order's costs, marked by Kind: fee, tax or shipping. The filter keeps only the taxes, so Eventbrite's fees and shipping charges are not written as taxes. The order's fees stay in Eventbrite Fee.

Description: Transfers each tax on the order as one transaction tax, as part of the parent order's transfer. Each tax is saved with the order number, the kind of charge and its position among the order's charges of that kind as its external ID link (example: 16109466973|tax|1). A free order has no taxes. Subscribers should validate this behavior on a paid, taxed order in a staging environment before relying on it in production.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Field

Amount

Amount

Required. The tax amount, in the order's currency. The order's total tax is also in TaxAmount. For a currency without two decimal places, see the note below the table.

Field

Name

Authority

Recommended. The name Eventbrite gives the tax on the order.

Currencies without two decimal places: Eventbrite reports each charge in the currency's smallest unit (Eventbrite API reference, Cost Component object), and the integration divides that value by 100, which is right for currencies with two decimal places, such as USD or EUR. For a currency with no decimal places, such as the Japanese yen, change the Amount mapping to a Dynamic Formula that multiplies it back: return Amount * 100;. For a currency with three decimal places, such as the Kuwaiti dinar, use return Amount / 10;. Subscribers should validate this behavior in a staging environment before relying on it in production.

Error Handling

Errors from this collection appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs; warnings appear in the transfer's activity log and do not fail the transfer. The full list of the integration's error codes and their resolutions is in the Eventbrite Error Messages article. The messages most often seen with orders (integration error codes are omitted):

  • "VALD-1024 - Required property 'type' not found in JSON. Path 'notes[0]' …": the Order Answer collection has no Type mapping. Restore the Static Type mapping (Customer Note), then resend the order from Manual Sync; nothing was written.

  • "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found.": the Order Ticket collection's Sku mapping does not name an existing iPaaS.com product. Create the event-ticket product and put its SKU in the Sku mapping, then resend the order from Manual Sync.

  • "VALD-1024 - Required property 'status' not found in JSON. …": expected when a state has no row in a status translation (see the translation tables); nothing is written. Resolution: restore the translation row, then resend the order from Manual Sync.

  • "TransferRequest is missing the payload data. This likely means the data no longer exists in the source system.": shown in the activity log, not in Error Logs, when Eventbrite does not know the order number (for example, a deleted order). Nothing is written; no action is needed unless the order number was mistyped.

  • "… is an attendee id; an order is transferred by its order number, an attendance record by "{event id}|{email}"." or "… is not an Eventbrite order id. Use the order number (for example 1234567890) or, for an attendee, "{event id}|{attendee id}".": the Manual Sync id is not an order number. Enter the order number shown in Eventbrite.

  • "Looking up the iPaaS.com customer with … failed (…). The transfer will be retried.": the buyer's customer could not be looked up. No action is needed; the transfer is retried.

  • "… has no email address, so it can't be an iPaaS.com customer; skipped. Its ticket stays on the order." (warning): shown by a person's own attendee transfer when that person has no email address; the order transfer itself logs nothing for them. To include them, add their email address in Eventbrite.

  • "… was not sent TO iPaaS.com as a customer: …. Resend it from Manual Sync." (warning): a transfer the integration started for a person on the order failed. Read the reason in the message, fix what it names, then resend that person from Manual Sync. The order is not affected.

  • "Eventbrite's hourly API limit was reached during …; the transfer resumes at … UTC.": the first gap names what the integration was reading (for example, reading Eventbrite order 16096958843) and the second the date and time, in UTC, when the limit resets (for example, 2026-12-20 15:00). Eventbrite's hourly call limit for the private token was reached. Resolution: no action is needed; iPaaS.com holds the transfer and sends it automatically at the time shown.

Testing & Validation

Test Scenarios

  1. Place a free order with one ticket in Eventbrite. Verify a transaction with the order number in TransactionNumber, Type Order, Status Complete, the buyer's EmailAddress and CustomerId, a Total of 0, Eventbrite Event Id, Eventbrite Event Name and Eventbrite Event Start, Eventbrite Order Status Placed, and one line with your event-ticket Sku, Qty 1 and Status Pending.

  2. Place an order with two tickets. Verify two lines, a TotalQty of 2, and each attendee sent as a customer.

  3. Place an order from a buyer who is new to iPaaS.com. Verify the transaction's CustomerId is set on the first transfer.

  4. Resend the order from Manual Sync by its order number. Verify the same transaction and the same lines, with no new customer.

  5. Check one attendee in. Verify that line becomes Complete with Eventbrite Checked In true and the other line is unchanged. Undo the check-in and verify the line is back to Pending with Eventbrite Checked In false.

  6. Cancel one ticket of the two-ticket order. Verify that line becomes Refunded, the other line is unchanged, and the transaction stays Complete.

  7. Cancel a whole free order. Verify the transaction's Status, Eventbrite Order Status and every line become Refunded.

  8. Add the exclusion condition to another system's transaction collection FROM iPaaS.com, and verify the Eventbrite transaction is not sent there.

  9. Place an order for an event whose order form asks a custom question, and answer it. Verify one transaction note of type Customer Note with the question and the answer, for example Dietary requirements: Vegetarian.

  10. If you sell taxed tickets, place a paid, taxed order. Verify one transaction tax per tax, with its name in Authority, and no tax rows for Eventbrite's fees.

  11. Leave the Ticket Sku as the default value on a test subscription. Verify the order is refused with NFND-1003 while the buyer and attendees are still sent as customers; then set the SKU and resend the order from Manual Sync.

  12. Verify that no attendance record (a transaction whose TransactionNumber is the event id and an email address) was written by this collection.

Validation Checklist

  • The event-ticket product exists in iPaaS.com, and its SKU is in the Sku mapping of both the Order Ticket and the Attendance Ticket collections.

  • This collection's filter keeps the condition RecordKind != "Attendance".

  • The order.placed, order.updated and order.refunded scopes are turned on in Inbound Data Flows, and the attendee scopes too, so check-ins update the lines.

  • Every transaction collection FROM iPaaS.com that must not receive event registrations has the exclusion condition.

  • The Status translations list the statuses your other systems expect, with a row for every value.

  • The ShippingAmount and Eventbrite Event Id mappings, and the Order Answer collection's Type mapping, are in place.

Additional Notes

Other Order fields you can map

Besides the default mappings, these Eventbrite order fields can be added with Field mappings: RecordKind (Order on every record this collection takes), BuyerName, BuyerFirstName, BuyerLastName, EventTimezone (for example America/New_York), EventUrl, ActiveTicketCount (tickets still held), AttendedTicketCount (tickets whose attendee was at the event), Status (Eventbrite's own order status) and EmailOptIn (true or false when the buyer answered Eventbrite's marketing opt-in). On the Order Ticket collection: AttendeeId, TicketClassId, Status (Eventbrite's own attendee status, for example Attending), CheckedIn, Cancelled, Refunded, and the ticket's Gross, Fees and Tax.

Known Limitations

  • Polling: at the time this documentation was written, orders arrive by webhook, order refresh, initialization or Manual Sync; there is no scheduled poll. After an outage, run the initialization again to catch up; it updates the existing transactions and creates no duplicates.

  • Following an initialization: at the time this documentation was written, an initialization run appears in Integration Monitoring as one run; the orders it sends do not appear one by one.

  • Shipping: at the time this documentation was written, the integration does not write a shipping total from Eventbrite. The ShippingAmount mapping keeps the amount the transaction already has in iPaaS.com and writes 0 on a new transaction.

Out of Scope

  • Writing to Eventbrite: the integration never creates, changes, cancels or refunds an Eventbrite order.

  • Deleted orders: deletion is not transferred. A cancelled or refunded order keeps its transaction with the matching status.

  • Payments: no transaction payment is written.

  • Per-ticket products: ticket types are not mapped to separate iPaaS.com products.

  • Fees and tax on the line: the ticket's fees and tax stay on the order, not on the line.

  • Fees and shipping as taxes: Eventbrite's fee and shipping charges are not written as transaction taxes.

Related Documents

Related Mapping Documentation

External References

Did this answer your question?