Activating the Zapier Integration

Overview

In this article, you’ll learn how to activate the Zapier integration in AMS+, and create API Keys. Zapier is a third-party workflow automation tool. In Zapier, you can make workflows (called Zaps) that send data between AMS+ and popular apps like Facebook Lead Ads and Handwrytten.

Once the integration is activated, you can make Zaps with AMS+. See our app page in Zapier for Zap templates.

IN THIS ARTICLE

---

How to activate the integration

Our integration connects your AMS+ account with Zapier using API keys, allowing you to create Zap workflows between AMS+ and third-party applications. There are two types of API keys, and the one you need depends on the data you intend to transfer to or from AMS+.

To get started, you first need to activate the integration in AMS+. Here’s how:

In AMS+, go to Settings > Servicing > Integrations > Zapier.

Select “Add to AgencyBloc”.

Review the terms and conditions.

In particular, make sure you understand how your Zaps can affect your Automated Workflows in AMS+.

If you agree with the terms and conditions, accept.

Once the integration is activated, you can generate API keys on the integration page to use in your Zaps. Keep in mind, the API keys generated on the integration page can only be used to either create Activities, Groups, Individuals, or Policies in AMS+ or send Activity, Group, Individual, or Policy data from AMS+ to third-party applications. Learn more about our app’s Zap Triggers and Actions.

If you want to make Zaps for Sales Records, you will need your account-specific API sid and key.

---

How to generate API keys for AgencyBloc’s Zap Triggers and Actions

During Zap setup, you will need an API key to connect your AMS+ account to Zapier. If the Zapier integration is activated in AMS+, you can generate and manage API keys.

An API key is a unique code that you use to authenticate the connection between AMS+ and Zapier. This allows Zapier to send data into AMS+ and out of AMS+.

Important: API keys grant full access to your AMS+ account, so you should protect them the same way you protect your AMS+ account password. Never email the API key; in the event that your email account becomes compromised, the emailed key would allow hackers to access your AMS+ account as well.

To create an API key:

In AMS+, go to Settings > Servicing > Integrations > Zapier.

Go to the Manage API Keys (Inbound) section and select “Create New API Key”.

Name the API key something that is easy for you to remember and identify and save.

We recommend using the following naming convention when creating API keys: [name of third-party app] - [Username]. For example, “Hubspot - Steve Smith”, or “Bomb Bomb - Jane Monroe.”

You can generate as many API keys as you want. For best practice, we recommend having one API key for every user that is creating Zaps at your agency. This will help you identify and track Zap activity to specific users in AMS+’s data logs.

How to deactivate and delete API keys

In most cases, you shouldn’t need to deactivate or delete your API keys. For things like turning off or editing a Zap, we recommend doing that in Zapier.

However, you might need to delete/deactivate an API key in AMS+ in these scenarios:

• You can temporarily prevent others from using the API key to set up new Zaps by deactivating it.
• If you think an API key has been compromised, you could delete it and generate a new one. You should also contact Zapier support to make sure the API keys aren't still being used.

Note: If you deactivate or delete an API key in AMS+, Zapier might continue to allow Zaps that were using it to run for an unknown period of time. This appears to be a timing issue with Zapier that we can't control. You can prevent this by going into Zapier and replacing the API key in your Zaps or turning those Zaps off.

---

How to activate Zaps for Sales Records

By default, our Zapier integration supports Zap Triggers and Actions for Activities, Groups, Individuals, and Policies. If you want to create Zaps to create, update, or find Sales Records, or create and associate Activities with Sales Records, you will need your account’s Sales Record API sid and key.

To acquire this sid and key, please have your Account Owner reach out to our Support Team at help@agencybloc.com and submit a request.

---

How to deactivate the integration

---

Potential impacts to AMS+ data

As you start making Zaps, it’s important to consider the possible impacts to your AMS+ data.

In particular, Zaps could potentially:

• Create duplicate records.
• Trigger AMS+ Workflows.
• Create endless loops with other Zaps and AMS+ Workflows, which also creates duplicate records.
  • Learn more about Activity loops in AMS+
  • Learn more about loops in Zapier
• Be triggered by other integrations (e.g., Intulse, Ease, a lead vendor, etc.) in your AMS+ account.

If data issues occur, we may be limited in the help we can offer and there may be a fee associated with data cleanup.

---

Common questions

Can I use the Zapier integration for sensitive data?
AMS+ secures the data sent between AMS+ and Zapier. However, Zapier recommends against sending sensitive data through their platform (see Zapier Security and Terms).

Third-party apps you use in your Zaps may not be properly securing your data, and AMS+ can’t prevent you or others at your agency from using third-party apps that aren’t sufficiently secure. It is ultimately your responsibility to ensure you are conscious of the data you are sending between AMS+, Zapier, and third-party apps.