Introduction

Zapier is a cloud based marketplace that allows you connect other apps with Operate. You can sign up to Zapier here

Connecting Zapier to Operate

Once you have signed up for Zapier, you can search for apps integrated with Zapier on the explore page, here you can find essensys Operate. 

Once Operate is selected, click 'connect account' to login with your existing Operate account.

You will then be prompted to enter you Operate login details before you can use Operate when making a Zap.

Configuring Operate to integrate with other apps

For any apps you want to integrate with Operate, those apps will need to have the necessary triggers and fields registered with Zapier. You will be able to see what fields and triggers that have registered when you add their app.

Operate already has a set of triggers and fields registered with Zapier, however if there are any you wish to add then please contact the Customer Success team via the chat widget.

Please note that Zapier is best used for 'one way', 'one time' actions, when pushing information from one master system into another, rather than to keep two systems in sync as this can lead to duplication of data

Currently available Triggers: 

  • New Account
  • Updated Account
  • New Contact
  • Updated Contact
  • Deleted Contact
  • New Lead
  • Updated Lead
  • New Calendar Event
  • Deleted Calendar Event
  • New Charge Sheet
  • Update Charge Sheet
  • Delete Charge Sheet
  • New Licence
  • New Product

Currently Available Actions

  • Create Account
  • Create Contact
  • Update Contact
  • Create Lead
  • Create Tour
  • Create Opportunity
  • Update Opportunity
  • Create Product
  • Create Charge Sheet
  • Update Charge Sheet

You may want to add a Filter to your triggers. This will allow you to add more conditions around what events will trigger an update, and it will also save you from running through your allotted 'Zaps'.

For instance, if you are using the 'Update Account' trigger, you can filter to only receive updates where Record Type is Account so that you do not get a Zap each time a Broker is updated using LeadDADI. Or, you may want to only get updates related your location.

Zapier applies some deduplication to prevent actions from being repeated for a single trigger. See here for more information.




Did this answer your question?