

Just set the status in the options of your Zap to "all" like this: You can now trigger off all attendees across all events on the "New Attendee" trigger.


Triggering Off All Attendees Across All Events Double check to make sure that the event is in a published state. I created a new event but it didn't trigger my zapĮvents created in Eventbrite need to be published in order to be picked up by the New Event trigger. This can result in zaps triggering on new items more slowly. My Eventbrite trigger is triggering slowlyįor Eventbrite triggers that are not instant, in order to ensure that we only trigger on new items that have complete information, your zap will make sure that a new item shows up with the same info in consecutive checks for new data. If you're the main account holder, you should just see something like this: (403) Forbidden response and "Invalid permissions." error messageĬonfirm you are not using a sub-user email address, but a main account email address as documented above. If you're a sub-user, you should see the email of the "main account" on the top right, like so: Note: Sub-users can use the single “Find Event” action, but if they select the “Own Events?” checkbox, no events will be returned because they technically can’t own any events. Click "Reconnect" on the Eventbrite account-when you see the popup, confirm the main account holder is logged into Eventbrite.Back in Zapier, go to your Connected Accounts page:.To get around this, you should connect the main administrator’s account to Zapier instead of yours. Sub-users aren’t able to see other events, even if they create the event themselves. Only the main account holder can see the events in the account through Zapier. This usually happens if the user who connected to Zapier is a sub-user in their Eventbrite account. Events aren't showing up in the Events dropdown Once your permission are enabled in Eventbrite, you can try connecting your Eventbrite account to your Zap again. You can fix this by contacting your Eventbrite organization administrator, and requesting they provide you with administrator access so that you can connect your Eventbrite account to Zapier. Generally, it is required that you be an administrator before you're able to connect your Eventbrite app to Zapier and use the New Attendee and other triggers. This often means that your Eventbrite account doesn't have the proper permissions to the event that you're trying to use in your Zap. Receiving “Not Authorized” or “Internal Error” when turning on a Zap
