CRM Integrations Using Zapier

Updated :

 

 

AgentLocator ↔️ Zapier Integration

We created our own Zapier app so that you can connect your other systems to AgentLocator and automate your workflows even more.

Zapier helps you automate your business by connecting your web applications with triggers and actions. This way, you can set up a Zap that says “If AgentLocator does this, make X do that.” Or, “If X does this, make AgentLocator do that.”

Here are some of the most common CRM's & Business Tools you Can Zap to / from:

zendesk__1_.png

 

** For a Full List of Applications Available on Zapier, go here: https://zapier.com/apps **

 

Who can install this integration?

AgentLocator: Users with LeadGen site.

Zapier: All plans (Zapier offers 5 free NON-premium Zaps)

Make sure you have an account with AgentLocator and with Zapier!

Get AgentLocator API key to integrate with Zapier

The API key is used to authenticate the AgentLocator account when creating a Zap to automate your business.To get the API Key:

  • Go to AgentLocator CRM Administration > Company Administration. Find Zapier and copy the API key.

1.png

2.png

 

How to Create a New Zap with AgentLocator

  1. Click “Make a Zap”
  2. Name your Zap
  3. Choose your Trigger App.
  4. Choose your Trigger Event and follow the prompts to connect your accounts.
  5. Choose your Action App. Then choose your action.

 

mceclip20.png
pasted_image_0.png


Here is a full list of triggers supported by AgentLocator:

  1. New Lead (If you want leads to feed both ways ie leads from Agentlocator feed into an alternate CRM and Leads from Alternate CRM to feed into Agentlocator CRM, you will require Two (2) s

Triggers when lead is created in AgentLocator CRM. Data that will be sent when a new lead is created in AgentLocator CRM is:

    1. First Name - First name of the created lead
    2. Last Name - Last name of the created lead
    3. Phone Number - Phone number of the created lead
    4. Email Address - Email address of the created lead
    5. Status - The current status of the created lead (Open || Qualifying || Qualified || Converted ...)
    6. Pipeline - Pipeline status of the created lead (New Lead || Tried to contact || Made Contact …)
    7. Id - id of the created lead. This can be used later if the lead needs to be updated.
    8. Timestamp - Timestamp when the lead has been createdUpdate Lead

2. Triggers when lead is updated in AgentLocator CRM. Data that will be sent when a new lead is created in AgentLocator CRM is:

    1. First Name - First name of the created lead
    2. Last Name - Last name of the created lead
    3. Phone Number - Phone number of the created lead
    4. Email Address - Email address of the created lead
    5. Status - The current status of the created lead (Open || Qualifying || Qualified || Converted ...)
    6. Pipeline - Pipeline status of the created lead (New Lead || Tried to contact || Made Contact …)
    7. Id - id of the created lead. This can be used later if the lead needs to be updated.
    8. Timestamp - Timestamp when the lead has been created

AgentLocator supports two actions:

  1. Create Lead

Allows for leads to be created inside the AgentLocator CRM system. In order to create a valid lead inside AgentLocator’s CRM system, valid values for Last Name, Email address, Phone Number and Site (LeadGen site) have to be provided. That’s why this values are marked as required on the Zapier application.

It is possible to define the following data set for all the leads that are imported through Zapier integrations:

  1. First Name - First name of the lead that will be created inside AgentLocator CRM
  2. Last Name (required) - Last name of the lead that will be created inside AgentLocator CRM
  3. Email (required) - Email address of the lead that will be created inside AgentLocator CRM
  4. Phone (required) - Phone number of the lead that will be created inside AgentLocator CRM
  5. Source - Source of origination of the lead that will be created inside AgentLocator CRM. If nothing is set inside this field on the Zapier application, the default value that will be shown in the CRM lead record is ‘zapier.com’
  6. Lead Type - lead type that will be set inside the lead data field
  7. Pipeline - Pipeline status that will be set for the lead that will be created inside AgentLocator CRM. All values that are supported will be shown in the drop down list. If nothing is set on the Zapier application, the default value that will be shown in the CRM lead record is “New Lead”
  8. Tags - Tags that will be applied to the lead that will be created inside AgentLocator CRM. only the already created tags that will be shown in the drop down menu are supported to be applied.
  9. Site (required) - LeadGen site that the lead that will be created inside AgentLocator CRM will be associated with.
  10. Status - Status that will be set for the lead that will be created inside AgentLocator CRM. Available values will be shown in the drop down menu on the Zapier application. 

Warning: Requests that do not have a value set for the required fields will not be created on the AgentLocator CRM side. You will see an error log inside Zapier’s Task History.

 

2. Update Lead

Allows updating existing leads inside AgentLocator’s CRM system. It is possible to define the following data set for all the leads that will be updated through Zapier integrations:

  1. LeadId (required) - Id of the lead on the AgentLocator’s CRM system that you want to update. This Id is sent by AgentLocator’s CRM system during Create Lead trigger in the Zapier application. (see New Lead trigger under point g.)
  2. First Name - First name value that will be used to update the First Name value on the existing AgentLocator lead record.
  3. Last Name - Last name value that will be used to update the Last Name value on the existing AgentLocator lead record.
  4. Email - Email address value that will be used to update the Email Address value on the existing AgentLocator lead record.
  5. Phone - Phone number hat will be used to update the Phone Number value on the existing AgentLocator lead record.
  6. ExternalId - Id of the external integration that will be stored on AgentLocator’s backend for support troubleshooting.

 

Warning: Requests that do not have a value set for the required fields will not be updated on the AgentLocator CRM side. You will see an error log inside Zapier’s Task History.

Comments

Powered by Zendesk