Zapier is an automation software that uses webhooks to push and pull information between various systems. Using this information, automations can then be created between your CoreBridge system, and a variety of other systems. 

Table of Contents

• Benefits of Integrating with Zapier
• How to Integrate CoreBridge Classic with Zapier
• Available Triggers
• Available Actions

Benefits of Integrating with Zapier

• Easily create automations for all simple tasks
• Create automations that automatically update your CoreBridge system based on outside system updates
  • Example: An automation that creates a new contact in your CoreBridge system when it is added to a spreadsheet
• Create automations that do repetitive outside tasks based off of changes in your CoreBridge system
  • Example: An automation that sends out an email to any new contacts created in your CoreBridge system

How to Integrate CoreBridge Classic with Zapier

To integrate your CoreBridge system with Zapier, navigate to Management / Global Settings / Services.

1. Select Click here for access to the CoreBridge Classic Zapier App. 

This will redirect you to an invitation page that allows you to accept the invitation and begin building your automations.

Note: If the CoreBridge Classic Zapier Integration is not present, please reach out to support@corebridge.net to have it enabled in your system. If the link does not work, or is not present, please reach out to support@corebridge.net for an invitation.

Available Triggers

In Zapier, a Trigger is the event that begins an automation. Once you have access to the CoreBridge Classic Zapier App, Integration Settings will then be available, where you will enable or disable triggers and paste your Zapier Webhook URL's so the two systems can interact with each other. 

To edit these settings, navigate to Management / Global Settings / Services. 

1. Click Integration Settings.

In your CoreBridge Classic Zapier Integration Settings, there are currently four triggers that CoreBridge offers. 

a. Contact Created - fires when a new contact is created in CoreBridge.

    Example: Automatically start workflows when a new contact is added, such as sending welcome emails or updating CRM records. 

b. Contact Updated - fires when an existing contact is updated in CoreBridge. 

    Example: Track changes to contact information and trigger follow-up actions like notifications or data syncing.

c. Customer Created - fires when a new customer is created in CoreBridge.

    Example: Automate tasks that should happen when a new customer record is added, such as a sales notification.

d. Customer Updated - fires when an existing customer is updated in CoreBridge.

    Example: Respond to customer data changes with alerts, updates in other systems, or analytics tracking. 

To connect these triggers with your CoreBridge Classic Zapier App, you will need to create a new Zap in the app.

When creating the Zap, select the CoreBridge trigger you would like to connect as the Zap's Trigger Event, and then navigate to the Test tab. 

Within the Test tab, there will be "Your webhook URL" that can then be copied. 

After copying, you will then need to paste this link in your CoreBridge Classic Zapier Integration Settings in the Zapier Webhook URL field for the appropriate trigger.

Note: Using the checkmark fields next to each trigger, you can select whether or not you would like the trigger to be enabled. Triggers that have a Zapier Webhook URL and are enabled will allow Zapier to pull the appropriate information from your CoreBridge system.

Available Actions

Using CoreBridge Classic Zapier App, you have the ability to perform certain tasks automatically in your CoreBridge system using Actions. These tasks currently include Create Contact, Create Customer, Update Contact, Update Customer, Delete Contact, Delete Customer, Find Contact, and Find Customer. 

Note: All required fields must be referenced by the Trigger or previous Action in Zapier for the action to work correctly. 

Create Contact - creates a new contact in CoreBridge.

Endpoint: ZapierV3Contact/Create

Required Fields:

• FirstName
• LastName
• Email
• AccountId

Optional Fields:

• Position
  
• PrimaryPhoneNumber
• SecondaryPhoneNumber
  

Create Customer - creates a new customer in CoreBridge.

Endpoint: ZapierV3Account/Create

Required Fields:

• CompanyName
• AccountTypeId (1 = Client, 2 = Prospect, 4 = Lead)
• ShippingAddress (must follow valid address structure)

Optional Fields: 

• LocationId
• CompanyPhone
• CompanyFax
• Website
• BillingAddress

Update Contact - updates an existing contact in CoreBridge.

Endpoint: ZapierV3Contact/Update

Required Fields:

• ContactID
• AccountID

Optional Fields:

• FirstName
• LastName
• Position
• Email
• PrimaryPhoneNumber
• SecondaryPhoneNumber
• PrimaryPhoneNumberExtension

Note: Only fields provided in the update will be modified.

Update Customer - updates an existing customer in CoreBridge.

Endpoint: ZapierV3Account/Update

Required Fields:

• AccountID

Optional Fields:

• CompanyName
• CompanyPhone
• CompanyFax
• Website
• BillingAddress
• ShippingAddress

Note: Only fields provided in the update will be modified.

Delete Contact - inactivates an existing contact in CoreBridge.

Endpoint: ZapierV3Contact/Delete

Required Fields:

• ContactId

Note: This is a soft delete that inactivates, but does not permanently remove the contact. The contact can be reactivated in your CoreBridge system.

Delete Customer - inactivates an existing customer in CoreBridge.

Endpoint: ZapierV3Account/Delete

Required Fields:

• AccountId

Note: This is a soft delete that inactivates, but does not permanently remove the customer. The customer can be reactivated in your CoreBridge system.

Find Contact - finds a contact by using one or more identifying fields.

Endpoint: ZapierV3Contact/Get

Accepted Parameters (at least one is required):

• Email (recommended)
• Id
• AccountId
• CompanyName

Note: At least one field must be provided. For best results, we recommend using email when using companyName or accountId.

Find Customer - finds a customer by using one or more identifying fields.

Endpoint: ZapierV3Account/Get

Accepted Parameters (at least one is required):

• CustomerId
• CustomerName

Note: At least one field must be provided.

Frequently Asked Questions