Inbound: from your platform into Salesfinity
An import is a snapshot. Salesfinity reads the list, report, sequence, or due-task queue you chose and copies each person into a Salesfinity contact list. For every contact it stores:- The mapped fields from your field mapping — name, title, company, email, phone numbers, plus any custom fields you configured.
- The source (HubSpot, Salesforce, Outreach, and so on) and the record ID in that source. For task-based imports it also stores the task ID and, where the platform has them, the sequence and step.
- The list name, taken from the platform’s list, report, or sequence name.
During the call
Everything on the call stays in Salesfinity until you log the outcome: the live transcript, recording, AI notes, and the disposition you choose. Nothing is written to the CRM mid-call.Outbound: from the call log to your platform
When you log a call, Salesfinity saves the call log immediately and marks it queued for sync. A background worker then does the rest, so logging never waits on a CRM.1
Wait for the recording and transcript
For calls longer than five seconds that were recorded, the worker waits until the recording
URL and transcript are available before syncing, so the activity written to your CRM carries
the recording link. It retries a few times; if the recording still has not arrived, the call is
synced without it rather than being dropped.
2
Route by source
A contact that came from HubSpot, Salesforce, Outreach, or another integration is logged back
to that platform using the stored record ID. See each platform’s guide for exactly what is
written: HubSpot,
Salesforce,
Outreach.
3
Fan out contacts with no source
A contact from a CSV, a custom list, or a follow-up has nowhere obvious to go, so the call is
logged to every CRM the team has connected among Salesforce, HubSpot, and ActiveCampaign.
Salesfinity matches the person in each CRM by email, phone, or name, and creates the record
if nobody matches. A CSV contact that carries a Salesforce or HubSpot ID (for
example, exported from that CRM) is logged only to that CRM.
4
Complete the task
If the contact was imported from a task, the task is completed in the source platform. In
Outreach the sequence step advances; in Salesforce an active cadence step is marked complete.
5
Record the result
The call log stores the ID and link of the activity created in each platform, and its sync
state is updated. Call history shows the state and, on failure, the reason.
Sync states
Retries are safe. A retry only writes to the platforms that are still missing the call, so a
partial failure never produces duplicate activities.
Other things that flow between systems
- Phone numbers. A number found by enrichment or edited in the dialer can be pushed onto the CRM record, so the next import already has it.
- Sequences. Adding, moving, or removing a person in a sequence from the dialer writes straight to the sequencer. See the sequence section on each platform guide.
- Gong. When Gong is connected, recorded calls of at least ten seconds that were not voicemails are uploaded to Gong after the CRM sync, under the rep’s mapped Gong user. Contacts imported from Gong Engage sync to Gong directly and have their task marked done. See Gong.
- Follow-up sync. Calls made in a connected platform’s own dialer can be pulled into Salesfinity, transcribed, and turned into follow-up tasks, so a rep’s follow-up pipeline covers calls made anywhere.
- Outbound to your own systems. Every logged call is also available to your systems through webhooks configured in the dashboard, the REST API, and the MCP server. Those read from Salesfinity’s call log and do not depend on the CRM sync.