Changes in the Zapier Integration

We’ve rebuilt our Zapier integration from the ground up to offer new functionality, improvements on previous features, and to improve the user experience. It also addresses some pesky bugs that were getting in the way. By upgrading to the latest version of our Zapier integration, you will be able to access all of these updates. You will also be able to transition seamlessly to future versions of our Zapier integration as we continue to update existing features and add new ones.

However, please note that this new version of the AddEvent Zapier integration contains breaking changes if you are updating your Zap from an older version. This means that you will need to update each of your Zaps that contain an AddEvent trigger or action manually, and when doing so, you will need to test that the Zap still works as expected. For more information about how to update to the latest version, see our help doc: Update to the New Zapier Version.

Before updating to the new version of our Zapier integration, you should read this doc to find out all about the changes that you should expect, as well as some things to watch out for as you update your Zaps. If you run into any issues while updating your Zaps, if you are missing some input or output fields that you were using previously, or if you run into any bugs, please reach out to [email protected].

The following actions and triggers are available in the new version:

Actions

1. Create Event
2. Update Event
3. Delete Event
4. Find Event
5. Create Automated Add to Calendar Links

Triggers

1. New RSVP Attendee
2. New Calendar Subscriber

Overall updates

• In general, we’ve simplified and reduced the number of input fields and outputs to simplify the user experience and focus on the input fields and outputs that our users care most about.
• We’ve also made greater use of Zapier defaults when it comes to input fields, for example, using datetime input fields more extensively, which allow you to input “tomorrow at 4 pm” as the start time of the event, and Zapier will parse it correctly.
• The formats of dates and times have been standardized across the board. We’re now presenting all dates and times in yyyy-mm-dd hh:mm:ss format and output (e.g. 2023-11-23 10:00), whether for event start and end times, or for internal object create or modify dates.
• We’ve also removed the separate start and end date and time output fields, and instead now just return a single value for start date & time, and for end date & time.
• We’ve added a new ID for events in our system. The old zapier integration was based on an old event id that we will no longer be using going forward. The new event ids can be easily identified because they start with “evt-”. If you are using the old ids in your Zaps to connect with other systems, you’ll need to update it to use the new event id.

Breaking changes

You will experience breaking changes when upgrading your Zaps to the new version of our Zapier integration in the following circumstances:

Recreated/removed actions

To fix some bugs, we needed to delete and recreate some actions entirely or delete some actions/triggers to consolidate them. If this is the case, the action should still be available, you’ll just have to re-select it from the event dropdown on the App & event step in the Zap editor. Please note that the name of the event may have changed

Removed input/output fields

We’ve removed some of the unused/lesser-used input and output fields, as well as the more confusing ones to simplify and streamline the user experience. If you’re missing an input or output field that is causing issues for your zaps, please reach out to [email protected] and we’ll see what we can do to help!

Renamed input/output fields

For most of these the field that you’re looking for will still be available, but you will have to manually reconnect it in the Zap editor. In some cases, the shape of the data may have changed slightly, so be sure to test your zap before publishing it!

Create Event

This action is pretty similar to the previous version - the only changes are simplified input and output fields!

Changes

• Removed input fields
  • Event internal name, Custom data, Reminder
• Renamed input fields
  • Start date & time, End date & time, RSVP Form, Event landing page template, Recurring rule, RSVP enabled,
• Organizer name, Organizer email
  • Renamed output fields
• All output fields have been renamed
  • Removed output fields
• Event internal name, Start date, Start time, Start am/pm, End date, End time, End am/pm, Date format, Reminder,
  • Updated times, Transparent, Custom data
• Added output fields
  • Start datetime, End datetime

Update Event

This action is also pretty similar to the previous version, and again has a reduced number of input and output fields. We’ve also fixed a bug with previously saved values getting overwritten when they weren’t provided in the input fields for the update action. There’s a new “Add a search step” prompt that prompts you to add a Find Event action prior to this step to identify the event that will be updated.

Changes

• Updated to use the new event id
• Removed required input fields on an update action
• Fixed bugs with field values being overwritten on updates
• Added an automatic “Add a search step” button
• Removed input fields
  • Event internal name, Custom data, Reminder
• Renamed input fields
  • Start date & time, End date & time, RSVP Form, Event landing page template, Recurring rule, RSVP enabled, Organizer name, Organizer email
• Added input fields
  • Calendar
• Renamed output fields
  • All output fields have been renamed
• Removed output fields
  • Event internal name, Start date, Start time, Start am/pm, End date, End time, End am/pm, Date format, Reminder, Updated times, Transparent, Custom data
• Added output fields
  • Start datetime, End datetime

Delete Event

This action works the same as the previous version. We’ve fixed a bug where a subsequent action was always required after deleting an event. We’ve also added a new “Add a search step” prompt that prompts you to add a Find Event action prior to this step to identify the event that will be deleted.

Changes

• Updated to use the new ID key
• Recreated the action
• Added an automatic “Add a search step” button
• Renamed output fields
  • All of the output fields have been renamed
• Removed output fields
  • n/a

Find Event

Previously, we had 4 different actions here that behaved in weird and wonderful ways:

1. Find event
2. List Events in a Calendar
3. List Events in Main Calendar
4. List All Events Across All Calendars

We won’t get into all the inconsistencies here, but suffice to say, we’ve replaced this with a single search action that behaves according to Zapier norms (i.e. consistently returning 1 event, which is the expected behavior in Zapier).

This new, unified, action allows users to find an event by providing a search term that searches across the event name, location, and description, while filter for events on one calendar, events on multiple calendars, or events on all calendars, likewise for events, as well as providing a minimum and maximum date and time range to search within.

Changes

• Updated to use the new event id
• Added an automatic “Add a search step” button
• Removed actions
  • List Events in a Calendar, List Events in Main Calendar, List All Events Across All Calendars
• Updated input fields
  • Event(s)
• Added input fields
  • Calendar(s), Minimum date & time, Maximum date & time
  • Search term
• Renamed outputs
  • All output fields have been renamed
• Removed outputs
  • Event internal name, Start date, Start time, Start am/pm, Unix start date, End date, End time, End am/pm, Unix end date, Date format, Reminder, Updated times, Custom data, Transparent
• Added output fields
  • Start datetime, End datetime

Create Automated Add to Calendar Links

Replaces the old Direct URL Method action. This has been completely revamped with more consistent and less way less buggy validation, and simplified input. The output fields are all still the same however!

Changes

• Recreated the action itself
• Fixed bugs with date, time, and date/time format validation
• Removed input fields
  • Duration, Date Format, Organizer, Organizer email, Reminder (alarm), Calname, Attendees
• Renamed input fields
  • Start date & time, End date & time, Recurring rule, Event landing page template
• Renamed outputs
  • All output fields have been renamed

New RSVP Attendee

There were 2 different triggers here previously:

1. New RSVP attendee - which triggered on all new RSVP attendees
2. New RSVP attendee by Event ID - which triggered on all new RSVP attendees for a specific event

We’ve combined both of these old triggers into 1 new trigger and added some additional filtering options. You can now filter by one event, multiple events, or all events, filter by events on one calendar, events on multiple calendars, or events on all calendars, and filter by attendee status (“going”, “not going”, or “maybe”). These new filters should allow you to replace multiple Zaps with a single Zap by combining these filters to only trigger on exactly the events you want!

Changes

• Updated to use the new event Id
• Added input fields
  • Event(s), Calendar(s), Attending
• Renamed outputs
  • All output fields have been renamed
• Removed outputs
  • Internal Id, Event name, Event start date & time, Event end date & time, Event timezone, Event date format, All day event?, Calendar Id, Calendar description, First name, Last name, Ip, City, Region, Country, Latitude & Longitude, Postal, Timezone
• Added outputs
  • RSVP form data, RSVP form labels

New Calendar Subscriber

This trigger is similar to the same over from the old version of the integration. However, we’ve removed the requirement to specify a single calendar and updated that filter to allow you to choose one or multiple calendars to filter on.

1. This trigger now gives you the flexibility to
2. Filter by one calendar to kick off a Zap when a new user subscribes to your AddEvent calendar
3. Filter by multiple calendars to kick off a Zap when a new user subscribes to any of those AddEvent calendars
4. Don’t filter by calendar to kick off a Zap when a new user subscribes to any calendar on your AddEvent account

Change

• Updated input fields
  • Calendar(s)
• Added input fields
  • Subscriber status
• Renamed outputs
  • All output fields have been renamed
• Removed outputs
  • Active, Blocked, Ip, City, Region, Country, Location, Postal
• Added outputs
  • Status, Calendar type, Subscriber form values, Subscriber form labels