AgencyBloc App Triggers & Actions in Zapier

Overview

In this article, you’ll learn about our supported Zap triggers and actions. "Zap" is the name of workflows in the third-party workflow automation app Zapier. With Zaps, you can send data between AMS+ and other apps.

To send data out of AMS+ to other apps, you would set AgencyBloc as the Zap trigger. To send data from other apps to AMS+, you would set AgencyBloc as a Zap action. Visit the AgencyBloc app page in Zapier for a list of our supported triggers and actions.

IN THIS ARTICLE

---

What is a Trigger?

In Zapier, the Trigger is an event or condition that starts a Zap. Every time the trigger occurs, the Zap will send data out of AMS+ to a third-party app.

The AgencyBloc app has 8 Trigger events in Zapier:

Record Type	Event	What can trigger the event?
Group	...is created in AMS+	Manually creating a new Group anywhere in AMS+; Data import; API; Lead Forms; Other integrations
Group	...is updated in AMS+	Manually making edits to a Group’s Details in AMS+; Data import; API; Other integrations
Individual	...is created in AMS+	Manually creating a new Individual anywhere in AMS+; Data import; API; Lead Forms; Other integrations
Individual	...is updated in AMS+	Manually making edits to an Individual’s Details in AMS+; Data import; API
Policy	...is created in AMS+	Manually creating a new Policy anywhere in AMS+; Data import; API; Other integrations
Policy	...is updated in AMS+	Manually making edits to a Policy’s Details in AMS+; Data import; API; Other integrations
Activity	...is created in AMS+	Manually creating a new Activity anywhere in AMS+; Data import; API; Other integrations
Activity	...is updated in AMS+	Manually making edits to an Activity’s Details in AMS+; Data import; API

 

What's the difference between "Created" versus "Updated"?

AgencyBloc’s app in Zapier has two types of trigger events: Created and Updated. It’s important to understand how exactly these events trigger so you know what to expect when making your Zaps.

• Created - This type of trigger event will activate when you create a new Group, Individual, Policy, or Activity in AMS+. You’ll typically create these records manually in AMS+, but there are other methods (see table above). Any fields that were populated at the time of the record’s creation may be sent over to third-party apps.
  
• Updated - This type of trigger event will activate when there are changes to AMS+ records. You’ll typically update records manually in AMS+, but there are other methods (see table). Any fields that had data at the time the record was updated and saved may be sent over to third-party apps.
  

Masking sensitive data

When making a Zap, you will have the opportunity to choose which pieces of AMS+ data you want to send to the other app. If you’re sending Individual data to a third-party app, you will have the option to mask the Individual SSN or MBI.

---

What is an Action?

In Zapier, the Action is something the Zap does as a result of the trigger. When triggered, the action tells the Zap to do something in AMS+.

The AgencyBloc app has 4 Action events in Zapier:

Record Type	Event	What data can you map to AMS+?
Group	...create in AMS+	See [Zapier] Groups.
Individual	...create in AMS+	See [Zapier] Individuals.
Policy	...create in AMS+	See [Zapier] Policies.
Activity	...create in AMS+	See [Zapier] Activities.

What is a Get?

A Get is another type of action event. Instead of creating new records, a Get allows you to pull in AMS+ data from a previous step in your Zap. Then, you can map to this data in subsequent steps.

For example, say you want your Zap to send out a handwritten card when an Activity is created in AMS+. To send this card, you need the address information of your recipients.

An Activity doesn't hold address information, but its associated Individual/Group record does. Using a Get, you can access the associated Individual/Group’s address information.

Your Zap could look something like this:

1. Trigger - Start the Zap when an Activity is created in AMS+.
2. Get - Find and pull an Individual/Group ID from Step 1.
3. Action - Send a handwritten card using the address obtained from Step 2.

Here are some templates for examples:

What is a Search?

A Search is another type of Get. With a Search, you can pull Individual data directly from AMS+ into your Zaps. This includes Individual IDs and contact information.

For example, if you want Zapier to create Policies in AMS+, your Zap will need Group IDs or Individual IDs. With a Search, you can program your Zap to look for Individual IDs in AMS+ every time it is triggered.

If an Individual ID is found, your Zap will associate it with new Policies. This works for Activities as well.

Here's what your Zap could look like:

1. Trigger - Start the Zap when an Activity is created in AMS+.
2. Get - Find an existing Individual in AMS+ and pull its ID into Step 3.
3. Action - Create an Activity or Policy and associate it with the Individual found in Step 2.

Here are some templates for examples: