Inbox sync
How Zernio matches inbox contacts to HubSpot contacts and logs every inbox message on the contact's HubSpot timeline.
Once a portal is connected, every message the profile's inbox receives or sends is synced. There is nothing to call: Zernio does it within seconds of each message.
Match a contact
For each message, Zernio finds the HubSpot contact for the sender's Zernio contact, in this order:
- A HubSpot contact with the same email address.
- A HubSpot contact with the same phone number, read from the contact's WhatsApp, SMS, RCS or iMessage channel.
- Otherwise, with
syncContactson, a new HubSpot contact with the contact's name, email and phone.
The match is remembered, so later messages go to the same HubSpot contact. A matched contact is linked as it is: Zernio never overwrites its name or properties.
Log a message
With logMessages on, each message becomes one timeline entry on the contact:
| Channel | Logged as |
|---|---|
| Communication (WhatsApp) | |
| SMS | Communication (SMS) |
| Every other inbox channel | Note |
The entry says the channel and whether the message was received or sent, then the text. Attachments are listed as links. Each message is logged once, even when its sync is retried.
Push a contact from a workflow
Add a hubspot_upsert_contact node to a workflow to write to HubSpot at a chosen step, for example after a qualifying question:
{ "id": "crm", "type": "hubspot_upsert_contact", "config": { "email": "{{answer}}", "properties": { "lifecyclestage": "lead" } } }It finds the contact the same way as inbox sync and writes only the fields the node sets, skipping empty values. A new contact also takes the Zernio contact's name, email and phone.
properties takes HubSpot internal property names. The node follows success, or error when HubSpot is not connected or refuses the write.
How it behaves
- Messages sync for conversations linked to a Zernio contact; others are skipped.
- With
syncContactsoff and no match, the message is skipped rather than creating a contact. - If the HubSpot contact was deleted or merged since, Zernio finds or creates the contact again and logs the message there.
- When HubSpot rate limits the portal, the sync waits and retries, so a busy portal can lag by a few minutes.
- Only messages from after the connection sync. Earlier conversations are not backfilled.