Skip to content
Peak Atlas

Peak Automations / CRM sync

The contact is in HubSpot.Peak doesn't have it.

When a contact is created in HubSpot, Peak creates or updates it in Peak CRM, matched by e-mail. The other way round, a new contact in Peak CRM can create or update the HubSpot contact. Both directions run through your workspace's HubSpot connection. Before you switch on, Peak warns you if two automations could trigger each other.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
See the sync example

Try it with a made-up contact.

One contact, two systems.

Sample contact / fictional data

01Trigger02Match03Guard
Working example / contact sync

What gets synced.

Trigger
New HubSpot contact or new CRM contact in Peak.
Match
By e-mail: existing is updated, new is created.
Guard
Warning about a possible loop before switching on.
Editorial structure sketch · not the product interface

Your sync in three answers

What should flow where?

Fill in the example with a made-up direction. You see which details Peak needs. Nothing is connected or transferred.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Automations / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three questions. A sync without duplicates.

Draft · not yet put together

The direction
Still open
The fields
Still open
The note
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

From two lists to one state

Connect. Match. Check.

The order prevents duplicates and endless loops before the first real contact flows.

  1. 01Connect

    Connect HubSpot in Settings.

    Trigger

    New HubSpot contact or new CRM contact in Peak.

    A person connects the HubSpot account under Integrations. The connection belongs to the workspace, not to one automation.

    Settings → connection
  2. 02Match

    Find by e-mail.

    Match

    By e-mail: existing is updated, new is created.

    A contact with the same e-mail is updated instead of created twice. You see the field mapping in the flow view.

    Contact → found or new
  3. 03Check

    Spot loops before the start.

    Guard

    Warning about a possible loop before switching on.

    Peak reports conflicts and possible loops. The version runs only after the passed test run.

    Sample artifact → check report

The next proof is the product

Sync the next contact.

In Peak Automations you describe the sync in one sentence. Peak shows fields, direction and possible loops, and after the test run you switch it on.

Start with Peak Automations

Peak Automations / Your next step

A contact exists only once.

Try the example with the direction that causes you the most double work right now.

See the sync example
Local working example

Both sides are in the know.

Warning about a possible loop before switching on.

Frequently asked questions

Which CRMs are supported?

HubSpot through your workspace's connection, and Peak CRM. Other CRMs are not connected.

Are deals synced too?

No. Contacts are synced with e-mail, name and company.

What happens if both directions run?

Peak warns about a possible loop before you switch on and detects duplicate events.

More in Peak Automations