Summary
Sync Person is a Flow action that pushes one Alta prospect into your CRM as a Contact, a Lead, or both — on demand, at any point in a Flow. Unlike Alta's automatic CRM sync (which fires on fixed events like a reply or a status change), Sync Person lets you decide exactly when the push happens and which extra fields go with it.
Who this is for: Alta users who have a CRM connected and want a Flow to push a prospect into it at a specific moment — after a Router branch, once a goal is met, or at the end of a multi-step automation.
Before you start
A connected CRM. Sync Person only works with the CRM your account has connected in Settings → Integrations. See How to connect Your CRM to Alta.
A Flow that already has the prospect. The step needs both a Person ID and a Prospect ID, so an earlier trigger or step has to supply them.
The prospect must be in a campaign. Sync Person resolves the prospect through its campaign to work out which rep owns the record. A prospect that has never been enrolled in a campaign will not sync.
Step 1 — Add the Sync Person action
Open the Flow you want to extend, or create a new one.
Click the + at the point in the Flow where the sync should happen.
Pick your CRM from the integration list.
Choose the Sync Person action.
The step's description reads "Sync an Alta person to the CRM using custom field mappings."
Step 2 — Fill in Person ID and Prospect ID
Two fields are required, and both must point at the same person:
Person ID — the Alta person to sync to the CRM.
Prospect ID — the Alta prospect to sync to the CRM.
Map both from an earlier step's output rather than typing them by hand. A prospect belongs to exactly one person, so pulling both IDs from the same upstream step is the safest approach.
Step 3 — Choose what to create: Push Contact, Push Lead, or both
Below the IDs you'll find one checkbox per record type your CRM supports:
Push Contact
Push Lead — only on CRMs that have a separate Lead object
Both checkboxes start unchecked. A freshly added Sync Person step does nothing at all until you tick at least one. It won't error — it just quietly finishes.
Ticking both on a CRM that supports both will create or update a Contact and a Lead for the same person.
Step 4 — Map the fields you want to send
Checking a box reveals a Contact Field Mapping or Lead Field Mapping panel. It's the same mapping table you know from your CRM settings, with three columns:
Field — the CRM field to write to.
Type — Dynamic (pull a value from the Alta prospect) or Static (always write the same value).
Value — the Alta field to read from, or the fixed value to write.
Click Add Field to add a row. Each row also has a Send On Update toggle:
On — the field is sent when the record is created and every time an existing one is updated.
Off — the field is only sent on creation, so later edits made in your CRM are never overwritten.
This panel starts empty on purpose. Unlike the mapping in your CRM settings, the Sync Person step does not pre-fill recommended fields or required fields, and there is no Add Recommended Fields button. Anything you add here is an extra on top of your default mapping — you don't need to re-list the basics.
How field mapping precedence works
When the step runs, Alta merges three layers of mapping, highest priority first:
The Sync Person step's own mapping — what you configured in Step 4.
Your event mapping — any per-event field mapping set on the CRM integration.
Your default field mapping — the baseline mapping from Settings → Integrations.
If a row you add overrides one of your defaults, Alta marks it with an Overrides default badge. Hover it to see Previous type and Previous value, so you can tell exactly what you're replacing.
Which CRMs support Sync Person
Contact and Lead: Salesforce, Zoho, Bullhorn, Vtiger.
Contact only: HubSpot, Pipedrive, GoHighLevel, Attio, Odoo, Freshsales, Membrain, Nutshell, OnePageCRM, ActiveCampaign, ActiveDEMAND.
On a Contact-only CRM you'll simply see one checkbox — Push Contact — and one mapping panel.
Tips and common pitfalls
An unchecked step is a silent no-op. This is the single most common surprise. If the Flow runs green but nothing lands in your CRM, check whether Push Contact or Push Lead is actually ticked.
The step must match your connected CRM. Alta pushes to your account's main CRM integration. If you add a Sync Person step for a different CRM than the one connected, the step fails with
CRM integration not found— the same message you'd get with no CRM at all. Check Settings → Integrations before assuming the connection is broken.Mismatched IDs fail loudly. If the Person ID and Prospect ID belong to different people, the step throws
Prospect does not match person. Leaving either blank throwsPerson ID is requiredorProspect ID is required.Prospects outside a campaign won't sync. The step needs the prospect's campaign to resolve the owning rep. If there's no campaign, nothing is pushed and no error is raised — so use a trigger that guarantees an enrolled prospect.
Create-vs-update is decided by your CRM settings, not this step. Whether Alta may create new records, and whether it may update existing ones, comes from your CRM integration's push settings. Sync Person controls what is sent, not whether writing is allowed.
Existing records are matched before anything is created. Alta looks for an existing Contact or Lead using your Entity Identifiers settings if you've configured a custom identifier field, and falls back to searching by the prospect's email. A match is updated rather than duplicated.
The company may be pushed first. If company push is enabled on your CRM integration, Alta pushes the prospect's company before the Contact or Lead so the record can be linked. If the company push fails, Alta logs it and continues with the person sync.
Required CRM fields are your responsibility here. Because the step doesn't auto-add required fields, a CRM-side validation error usually means a mandatory field is missing from both your default mapping and this step's mapping.