Skip to main content

Eventbrite Mapping Functions

Reference for the Eventbrite-specific functions you can use in Dynamic Formula mappings and mapping collection filters.

Overview

The Eventbrite integration provides two ready-made functions you can call when building mappings. They handle lookups against your Eventbrite records and your iPaaS.com data, so you don't have to build that logic yourself: one reads the answer to an event's custom registration question from the record being transferred, and the other finds the iPaaS.com customer that has a given email address. The default Order and Attendance templates already use the customer function to set each transaction's customer.

Where you can use these functions

These functions are available anywhere you write a formula for the Eventbrite integration:

  • Dynamic Formula mappings: where a destination field's value is produced by a formula rather than mapped directly from a source field.

  • Mapping collection filters: where a formula decides whether a record should be processed.

  • Error filters: a mapping collection's error filter, which sits alongside its collection filter. When the error filter's formula resolves to true, the transfer raises an error that is held in the Error Logs for review and is not retried automatically.

  • Translation collections: where a translation entry uses a formula as its source value.

How to use them

  • Call a function by name and pass the values it needs in parentheses, for example: await EventbriteCustomerId(BuyerEmail).

  • Each function's signature shows its name, the parameters it accepts (with their types), and the type of value it returns. Use it as the reference for exactly how to call the function.

  • Function names and formula syntax are case-sensitive, so type each name exactly as shown. Whether the values a function matches are treated as case-sensitive varies by function, and is called out in the relevant parameter's description.

  • Some of these functions are asynchronous (their signature returns a Task) and must be called with await; the rest are synchronous and are called directly. Each function's How to call it example shows the correct form.

  • Each function runs at sync time, against the data in your connected Eventbrite account and your iPaaS.com subscription.

The functions are grouped below by the area of the integration they support.

Attendees and Registration Answers

Use this when mapping the answers people give to an event's custom registration questions.

EventbriteAnswer

What it does: Returns the answer to one of the event's custom Eventbrite registration questions (for example a dietary requirement, a T-shirt size or "How did you hear about us?") from the record being transferred. Returns an empty value when the question was not asked or not answered.

Signature: string EventbriteAnswer(object answers, string question)

How to call it: EventbriteAnswer(answers, question)

Parameter

Type

Required

Default

Description

answers

object

Yes

N/A

The Eventbrite registration answers on the record being transferred: pass the record's Answers field, which is available in the Attendee, Order and Attendance collections.

question

string

Yes

N/A

The Eventbrite question to read: its text as shown on the event's registration form, for example "Dietary requirements", or its Eventbrite question id. Matching the text is not case-sensitive and ignores spaces before or after it. A question id also ignores spaces before or after it, and must otherwise match exactly, including case.

Returns: string. The person's answer as text, or an empty value when the event did not ask the question, the person did not answer it, the question text or id does not match, or the question is left empty. An address answer is returned on one line with its parts separated by commas; any other answer is returned as text, as Eventbrite gives it.

Example: EventbriteAnswer(Answers, "Dietary requirements") returns the person's answer to that question, for example "Vegetarian".

When to use it: When you want to keep a registration answer in iPaaS.com: create the iPaaS.com custom field first, then add a Dynamic Formula mapping to it, for example return EventbriteAnswer(Answers, "Dietary requirements");. To keep an answer on the person, map it to an iPaaS.com customer custom field in Add/Update Eventbrite Attendee TO iPaaS.com; an attendee's transfer carries that attendee's answers, and an order buyer's transfer carries the answers given for the order as a whole. To keep an answer on the order, map it to an iPaaS.com transaction custom field in Add/Update Eventbrite Order TO iPaaS.com; an order carries the answers given for the order as a whole, then each attendee's answers, and the function returns the first answer to the question, so for a question asked of each attendee it returns the first attendee's answer. Every answer on an order is also written as a transaction note by Add/Update Eventbrite Order Answer TO iPaaS.com, so you do not need this function to keep the answers on the order. To keep an answer on the attendance record, map it to an iPaaS.com transaction custom field in Add/Update Eventbrite Attendance TO iPaaS.com; on an attendance record the answers are those of the person's first ticket for the event. Subscribers should validate this behavior in a staging environment before relying on it in production. If you later rename a question on the Eventbrite registration form, update the text in the formula too, or use the question id instead.

Orders and Attendance Records

Use this when setting the customer of an order or attendance record transferred TO iPaaS.com.

EventbriteCustomerId

What it does: Looks up the iPaaS.com customer whose email address is the one given and returns that customer's iPaaS.com customer id. Returns no value when no iPaaS.com customer has the email, or when several do.

Signature: Task<string> EventbriteCustomerId(object email)

How to call it: await EventbriteCustomerId(email)

Parameter

Type

Required

Default

Description

email

object

Yes

N/A

The email address to look up among your iPaaS.com customers, for example the Eventbrite record's BuyerEmail. Matching is not case-sensitive and ignores spaces before or after the address.

Returns: string. The iPaaS.com customer id when exactly one iPaaS.com customer has that email address, or null when the email is empty, no iPaaS.com customer has it, or more than one iPaaS.com customer has it.

Example: await EventbriteCustomerId(BuyerEmail) returns the id of the one iPaaS.com customer with the buyer's email address, for example "165910".

When to use it: In the CustomerId mapping of Add/Update Eventbrite Order TO iPaaS.com and of Add/Update Eventbrite Attendance TO iPaaS.com, where the default templates already use it as return await EventbriteCustomerId(BuyerEmail);. Keep those mappings as they are: the integration uses them to link each order to the buyer's own customer, and each attendance record to the person's own customer. On an order, the field BuyerEmail is the buyer's email; the buyer and every attendee on the order are sent to iPaaS.com as customers before the order is written, so the buyer's customer is found on the first transfer, including for a brand-new buyer. On an attendance record, the field BuyerEmail holds the attendee's own email address (not the email of whoever bought the ticket), so a guest's record lands on the guest's customer; the person is sent as a customer just before their attendance record, so the customer is normally found. When no single customer matches, the CustomerId is left empty and the transaction is written with its email address only; when several iPaaS.com customers share the email, merge or correct them in iPaaS.com, then resend the record from Manual Sync. If the iPaaS.com customer search itself fails, the transfer fails with a message in Dashboard / Integration Monitoring / Error Logs that includes "Looking up the iPaaS.com customer with", and the transfer is retried. The function searches your iPaaS.com customers each time it runs, so it adds one iPaaS.com call to each record it maps. You can also use it in any other Eventbrite mapping that needs the iPaaS.com customer for an email address.

Related Documents

Did this answer your question?