In this article, we’ll guide you through the advanced steps needed to get ActiveCampaign and NetSuite to exchange information, including any custom fields within ActiveCampaign.
Tip
This article is intended for readers who are familiar with the Celigo platform and have completed the Understanding Celigo Fundamentals learning path at Celigo University.
This integration demonstrates two (bidirectional) flows:
-
ActiveCampaign contacts to NetSuite contacts (add/update)
-
NetSuite contacts to ActiveCampaign contacts (add/update)
Before continuing, you will need working accounts for both NetSuite and ActiveCampaign and be familiar enough with both platforms to make basic changes.
If you haven’t already done so, create connections to ActiveCampaign and NetSuite.
You must define the custom fields you intend to use for ActiveCampaign. Personalization tags will be needed later during the mapping stage of building the flows.
Define a custom field in the NetSuite contact record to hold the ActiveCampaign ID for a contact. In this example, the custom field name is custentity_ww_activecampaign_id.
If you’re using custom fields in ActiveCampaign, create those fields in NetSuite, too, unless you you will be mapping them later to fields that already exist.
The steps below walk you through setting up the listeners, exports, and imports in Flow Builder.
This flow retrieves contacts from ActiveCampaign and syncs them with NetSuite.
This flow uses an ActiveCampaign webhook to retrieve new and updated contact information in real time. You must define the webhook in ActiveCampaign and the listener in integrator.io, as follows:
Use the following settings when defining a new listener in Flow Builder:
-
Name: ActiveCampaign : Webhook : Contacts (Add / Update)
-
Verification type: Token
-
Custom URL token: Use the API access key from your ActiveCampaign dashboard (under Settings > Developer)
After filling in the details above, click Copy URL to copy the public URL.
Sign into ActiveCampaign, go to Settings > Developer > Manage webhooks, and select Add.
Enter the following information:
-
Name: Contact added / updated
-
URL: Public URL copied previously
-
Type: Contact added, contact updated
-
Initialize from:
-
By a contact
-
By an admin user
-
By the API
-
By system processes
-
Remember the location of the Send sample data button on this page for use when you perform tests troubleshoot this flow.
The flow has two destinations: Add and Update. This example separates these two operations for illustration purposes. You can also combine the imports by defining the operation as add/update in a single NetSuite step.
Create an import with the following settings:
-
Name: NetSuite : Update Contact
-
Record Type: Contact
-
Operation: Update
-
How to find existing records:
["custentity_ww_activecampaign_id","equalto","{{{contact.id}}}"]
Define the data mapping to fit your needs. Here’s an example:
|
ActiveCampaign field |
NetSuite field |
|
contact.comment |
Comments from marketing |
|
contact.lead_source |
Lead Source (last touch) (Name) |
|
contact.job_function |
Job Function (Generalized) (Name) |
|
contact.company |
Company (free text) |
|
contact.contact_status |
Status (Name) |
|
"General" |
Campaign Category (Name) |
Attach response mapping to this update import, such that the NetSuite ID of the updated record can be used as in the input to the add import:
|
Import response field |
Source record field (new/existing) |
|
id |
NSid |
Now, let’s create the add import with the following settings:
-
Name: NetSuite : Add Contact
-
Record type: Contact
-
Operation: Add
Within the new add import, define the data mapping again, similar to before but focused on adding rather than updating.
Finally, add an input filter to this import, as shown below:
And there you have it. You can now test this flow before moving onto the next flow, which handles the opposite direction.
You are all ready to build the flow that takes contacts from NetSuite and syncs them with ActiveCampaign:
The approach chosen for this flow is to use a schedule that exports all contacts from NetSuite and adds/updates them in Active Campaign. However, the source could equally be configured as a real-time listener from NetSuite.
If you plan to use a scheduling mechanism, first create a NetSuite Saved Search to expose the required fields of the Contact record, in particular the ID of the ActiveCampaign field defined in Get started, above.
In Flow Builder, define the export of this flow as outlined below:
-
Name: NetSuite : Get all Contacts
-
Output mode: Records
-
API type: RESTlet
-
Record type: Contact
-
Saved search type: Public or Private (depending on the visibility of the saved search you defined above)
-
Saved search/search ID: Name (if public) or ID (if private) of the saved search
Continue with the ActiveCampaign imports, and test your new integration.
Comments
Please sign in to leave a comment.