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.
IN THIS ARTICLE
Activating the integration
To activate the Zapier integration, you must be the Account Owner and belong to a Security Group with the “Manage Users” Administrative Permission and the “Edit” Permission for Groups, Individuals, and Policies.
Follow these steps to activate the integration:
- In AMS+, go to Settings > 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.
- The integration will be activated in AMS+, and you can start making Zaps with AMS+ in Zapier. During Zap setup, you will need an API key to connect AMS+ to Zapier. You can get your API key from AMS+.
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.
Can I use the Zapier integration for sensitive data?
AgencyBloc 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 AgencyBloc 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.
Creating and managing API keys
To create and manage API Keys, you must belong to a Security Group with the “Manage Users” Administrative Permission and the “Edit” Permission for Groups, Individuals, and Policies.
Once the Zapier integration is activated in AMS+, you can access your API key and generate new ones. 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 > 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.
Deactivating and deleting 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.
Deactivating the integration
You can deactivate the Zapier integration at any time. Before deactivating, please note that all of your API keys in AMS+ will be deleted. Any Zaps that are using these keys will also stop working.
If you reactivate the integration later, you will still need to generate new API keys and plug them into your Zaps to re-authenticate the connection.
Note: If you deactivate the Zapier integration in AMS+, Zapier might continue to allow Zaps 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 turning off any Zaps that are connected to AMS+.