Important! Changes to Zapier integration on the Triggre platform

To improve our performance, we’ve made changes in how we process updates and communicate them to Zapier. This may impact your applications as well. In this email, we’ll cover the following topics:

  1. The disadvantages of the current Zapier implementation within the Triggre platform.
  2. Changes affecting your applications.
  3. Next steps.

Below, these topics are explained in detail.

1. Disadvantages of the Current Zapier Implementation within the Triggre Platform In the current setup, we check every addition, edit, and deletion to determine if it needs to be sent to Zapier. This approach has two major disadvantages:

  • It is time-consuming to check each record.
  • It requires additional resources. To maintain optimal performance, we’ve changed the way Zapier is triggered.

2. Changes Affecting Your Applications
Previously, every record was automatically checked to be sent to Zapier. In the new approach, you will control which record (addition, change, or deletion) is sent to Zapier. This will work similarly to using the WebAPI. You will need to create a connection trigger in a flow part and select the items you’d like to send to Zapier. Zapier will require the updated Zap of Triggre to retrieve and process the data. Configuring the Zap in Zapier is similar to your current configuration. You always start by creating the ZapierAPI in a flow part in Triggre. After that, you create a Zap in Zapier and retrieve the information from Triggre.

3. Next Steps (Before June 1, 2024)
Your current configuration will continue to function until June 1, 2024. However, we’ve changed the status of the Triggre Zap you’re currently using to deprecated. This means that no new Zaps can be created using this old version. We advise you to reconfigure your application as soon as possible and at least before June 1, 2024. After this date, we will disable the old Zap trigger, and you will be unable to use it anymore. Any Zap using this old trigger will fail. Once you’ve migrated your Zaps, we can update the configuration of your application, and you can fully utilize the new Zapier configuration, unlocking all benefits. A list of applications requiring changes can be found in My Triggre under Migration Issues.

4. Finally
If you have any questions about this change or need help implementing it, please contact us at Don’t forget to mention the application that requires our assistance. On, we have indicated if your application has a design error related to this issue. Please mark the design error as completed after you change the configuration of your application.


One way of fixing this issue is is to create an automation flow that gets triggered when the record in a data-item gets added, changed or deleted and send all properties to Zapier.

Follow the steps below to set it up:

  1. Go to your zap and check on which data-item it’s triggered (check the two blue boxes in the screenshot below).
  2. Make a new flow part with the input of the triggered data-item (in this example “Website request”). Create a ‘connection triggre’. Choose type Zapier. Send all properties from “Website request”.
  3. Create a data trigger. This data trigger needs to be triggered when any property in the data-item “Website request” is added, changed or deleted (based on the information in the second blue box in the screenshot)
  4. In this data trigger you add the flow part of step 2. Link the “Website request” to the input.
  5. Publish your application
  6. Go to the zap in Zapier
  7. Change the first step in the broken zap to the newest version of the Triggre zap trigger.
  8. Connect the correct properties
  9. Enable the zap