Skip to main content
Connect Salesforce and you can dial any contact or lead report, or all your open call tasks, straight from the dialer. Every call you log becomes a completed Task on the record, and an active cadence step moves forward. Nothing is installed in your org. Each rep signs in as themselves, so your sharing rules and field security apply to Salesfinity exactly as they apply to the rep.

​
Before you start

  • The Salesfinity connected app is allowed in your org, if your org limits which apps users may sign in to.
  • Reps have API Enabled on their profile or a permission set.
  • Reports to import from, with the Contact ID or Lead ID column included.

​
Set up your org (admins, once)

1

Allow the Salesfinity connected app

If your org limits which apps users may authorize (Setup › Connected Apps OAuth Usage, or “Admin approved users are pre-authorized”), approve Salesfinity. Then assign it to the profiles or permission sets your reps use. Reps who are not assigned are refused at sign-in.
2

Give reps API access

The rep’s profile or a permission set needs API Enabled. Salesfinity does everything through the API, so a user without it cannot connect.
3

Check object permissions

Salesfinity acts as the rep, so the rep needs the access in objects and access. A standard sales profile usually has it. The one most often missing is Run Reports, with access to the report folders reps import from.
4

Prepare the reports reps will import

Use a contact report or a lead report, and include the Contact ID or Lead ID column. That is how Salesfinity finds the records. An import reads the first 2,000 records of a report, so split bigger territories into several reports.
5

Map a custom task process, if you have one

If your org uses custom Task statuses, a custom call type value or a custom due date field, set them under Task import in the integration’s settings. Orgs on the standard Task process can keep the defaults.
6

Decide on Sales Engagement

With Sales Engagement turned on, a logged call completes the current cadence step. Reps can also add, move and remove people in cadences from the dialer. Without it, everything else still works.

​
Connect your account (every rep)

1

Open the Salesforce card

Go to Settings › Connections › Integrations and find the Salesforce card.
2

Sign in and allow access

Click Connect, sign in with your own Salesforce login and click Allow.
3

Test with one call

Import a small report, dial one record and log the call. In Salesforce, the record should now have a completed call Task under your name.
Each rep must connect with their own login. If an admin connects once for everyone, every call is logged under the admin’s name. Salesforce cannot be shared with the team yet.
You are done when a test call shows as a completed Task on the Contact or Lead, under the rep who made it.

​
Permissions Salesforce asks for

Salesfinity is a Salesforce connected app. When you connect, Salesforce asks you to allow these scopes. Salesfinity only ever acts as the connected user. It cannot read a record or run a report that the rep’s Salesforce user cannot. There is no managed package, Apex, trigger, custom object or custom field.

​
Production and sandbox

The Salesforce card connects to production through login.salesforce.com. The Salesforce Sandbox card connects through test.salesforce.com. They are separate integrations with their own mappings, so you can test in a sandbox while dialing against production.

​
What Salesfinity imports

Pick a contact report or a lead report. Salesfinity runs it and imports the Contacts or Leads it returns, up to 2,000. The list is named after the report.
Contacts use the contact field mapping and Leads use the lead field mapping. Every record keeps its Salesforce ID and object type, so the call goes back to the right object. A field the rep cannot see is left out of the import rather than causing an error.
  1. Collect record IDs. For a report, Salesfinity runs it and reads the Contact or Lead ID from each row. For “All call tasks”, it queries your open call Tasks by due date and takes the record each one is related to.
  2. Load the records. It queries Contacts and Leads 100 IDs at a time. It selects only the fields in your mappings and custom fields, including relationship fields such as the account name.
  3. Build the list. Each record becomes a contact with its Salesforce ID, object type and a link back to the record. Task imports also keep the task ID and due date.

​
What Salesfinity writes back

When you log a call on a Salesforce Contact or Lead, Salesfinity creates a Task. If the record is in a Sales Engagement cadence and its current step is active, Salesfinity marks that step complete so the cadence moves on. Without Sales Engagement, the call is still logged and nothing else changes.

​
Calls on records that did not come from Salesforce

If you dial someone from a CSV or a custom list, the call still reaches Salesforce when it is connected. Salesfinity looks for the person among Contacts and Leads by LinkedIn URL, email or phone number. If nobody matches, it creates a Contact from your field mapping, skipping any mapped field the Contact object does not have, and then logs the call. Phone numbers found by enrichment or edited in the dialer can also be written to the Contact or Lead.

​
The full round trip

​
Objects and access

What Salesfinity reads and writes, and the access the rep needs for each. Field level security applies. The dialer never deletes a Salesforce record. It creates one only in the case above: a CSV contact with no match.

​
Cadences from the dialer

Sales Engagement cadences show in the dialer’s sequence controls. You can add a Contact or Lead to a cadence, remove it, and move it to another cadence. All three need Sales Engagement in your org.

​
Settings reference

Two separate maps, one for Contacts and one for Leads, from Salesforce fields to Salesfinity fields. Relationship fields such as the account name are available for Contacts.
Extra Contact, Lead, Account and Opportunity fields to bring across. Contact and Lead fields land on the contact in the dialer. Account and Opportunity fields feed the account view and Ari.
Maps each Salesfinity disposition to a Salesforce call disposition value. The automatic suggestion fills the table from your org’s picklist values.
Controls what “All call tasks” pulls and how tasks are closed. Map three Task fields:
  • Status: the field that says a task is open, and the values that count as open. Defaults to Status and “not Completed”.
  • Task type / call type: the field and values that mark a task as a call. Defaults to Task Subtype equal to Call.
  • Due date: the field used to find tasks due today or earlier. Defaults to Activity Date.
Orgs with a custom task process should map these to their own fields, so the import matches what reps see in Salesforce.

​
Staying connected

Salesfinity refreshes the Salesforce session on every request with your refresh token, so reps are not asked to sign in again. They only need to reconnect if the refresh token is revoked. That happens when an admin revokes the connected app, when a password change also revokes sessions, or when the org’s refresh token policy expires it. The card then reads as disconnected, and the rep reconnects from the same card.

​
Questions admins ask

No. Each rep connects with their own Salesforce login and every action runs as that user. A shared integration user would log every call under one name and skip your sharing rules, so Salesfinity does not support it.
Salesfinity stores each connected user’s access token, refresh token and instance URL in its credential store. It never stores passwords. Tokens are never shown in the app or returned by the API. Disconnecting deletes them, and revoking the connected app in Salesforce makes them useless right away.
An import costs one report run plus one SOQL query per 100 records. A logged call costs a short identity check and one Task insert. With Sales Engagement, add one cadence query and one action call.
Yes, in Salesforce. Salesfinity only sees what the connected user sees, so profiles, permission sets, sharing rules and field level security all apply.
Contacts and Leads are supported. Custom fields on either work through the custom field pickers, and a custom Task process works through Task import. Custom objects are not imported.
Yes. Connect the Salesforce Sandbox card to a sandbox org. It has its own mappings, so nothing from testing touches production.
Ari can look up Salesforce records for you. When it wants to create or update a record, it shows you the change and waits for your approval. Ari is available on Enterprise and Enterprise+ plans. See Ari.

​
Next steps

How a call gets back to your CRM

What happens after you log a call, and what each sync status means.

Fix integration problems

Reconnect prompts, empty imports and failed syncs.