HubSpot and ActiveCampaign
PieSync’s sync engine helps you create an intelligent connection between HubSpot and ActiveCampaign… and more than 240+ other cloud-based apps in real time.
All HubSpot customers (including free users) are eligible for a 25% discount on any PieSync plan. Sign up for a free trial to receive your discount.
Curious to read more about what objects PieSync can sync? Click here.
Step 1: Select ActiveCampaign and HubSpot
Step 2: Authorize ActiveCampaign
To connect your ActiveCampaign account, we need your API URL and Key. You can find them in your ActiveCampaign account by navigating to 'Settings' → 'Developer'.
If you already authorized Active Campaign List(s) in the past or in any other PieSync integration, you'll be able to skip this step and choose from your CONNECTED ACCOUNTS.
Step 3: Authorize HubSpot
All HubSpot plans are able to set up a PieSync connection.
For HubSpot CRM, we need you to first log in to your HubSpot CRM account in a separate window or tab, and copy your "Hub ID", to be found in the top right corner. When you click 'Authorize HubSpot CRM', a pop-up window appears with a request to enter this ID, followed by a window asking you to authorize your account.
If you already authorized HubSpot CRM in the past or in any other PieSync integration, you'll be able to skip this step and choose from your CONNECTED ACCOUNTS.
Step 4: Select your Customer Data Type
At the moment, PieSync only support Contacts. Therefore this step will be automatically skipped.
When should I select a data type? Some applications support multiple contact objects or company objects. In that case, we'll ask you to select the right object.
Step 5: Configuration
Once you authorized ActiveCampaign and HubSpot, you tell PieSync how we should keep your contacts data in sync. By default, PieSync proposes a two-way sync with a drop-down to allow for one-way syncs (do I need one-way or two-way?).
A two-way sync starts off with 2 rules. Each rule fulfills the conditions of each side of the sync. PieSync looks at all the data stored on each side, so you can define exactly what data needs to move from one side to the other.
If you need a simple all-to-all sync, this is all you need to set up (ie. don't change anything to the default setup). Starter plans are limited to two of these rules, but the Pro plan allows for more.
However, through PieSync you can and you should tweak the sync so that not only contacts get synced, but you also respect the segmentation, tags, owners, person stages, custom attributes, subscription status, ... of the apps that the contacts live in. In a PieSync rule, you can choose to add a filter and add actions to syncs.
What you can do depends from app to app. Typically, in the if-clause you define a segment of your contacts. In the then-clause, you perform actions such as adding the contacts to the counterpart of that same segment in the other app. Combine this with other actions you can perform as a result of a sync, and the possibilities are truly endless.
[IF] Supported Conditions/Filters
- In / Not in List
- Status in List / In None of the Lists (subscribed / not subscribed / unsubscribed / not unsubscribed / bounced / not bounced / unconfirmed)
- Has / Does not have Tag
- Field values (INCLUDING CUSTOM FIELDS)
- Already existing in the app you sync with
[THEN] Supported Actions
- Add to List
- Add / Remove Tag
- Set Status in List (subscribed / unsubscribed / bounced)
- Updating field values (INCLUDING CUSTOM FIELDS)
Connection Field Mapping
Two fields that are kept in sync by PieSync, without explicitly requiring the user to choose them. These are built-in mappings between standard fields that exist in both applications you are keeping in sync, usually fields such as name, phone or email address.
As of the Pro Plan, you are able to customize the default field mappings and you are also able to add your own field mappings. Any user-created mapping is also often referred to as the "Custom (Field) Mapping".
Don't hesitate to let us know if you have any further questions. Reach out to firstname.lastname@example.org