> ## Documentation Index > Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations Overview > How Salesfinity connects to your CRM and sales engagement platform, what a connection can do, and how to set one up. Salesfinity is a parallel dialer, so almost every team runs it next to a system of record. An integration connects the two: contacts and call tasks flow **in** from your CRM or sales engagement platform, you dial them in Salesfinity, and every call flows **back out** as an activity on the record it belongs to. Nobody re-keys anything. Import lists and due tasks, log calls as engagements, complete tasks. Import reports and open call tasks, log calls as Tasks, advance cadences. Import sequences and call tasks, log calls with dispositions and purposes. Upload recorded calls for transcription and scoring, work Engage call tasks. ## What an integration does Every CRM and sales engagement integration follows the same three-step loop. Pick a list, report, or sequence in the connected platform, or import everything that is due to you as a call task. Salesfinity pulls those people into a contact list, keeps the link to the original record, and maps their fields onto Salesfinity contact fields using your field mapping. You dial the list with the parallel dialer. Boss Mode, enrichment, dispositions, notes, and recordings all work the same whether the contact came from a CSV or a CRM. When you log a call, Salesfinity queues it and writes it to the platform the contact came from: a call engagement in HubSpot, a completed Task in Salesforce, a call record in Outreach. Open call tasks on that record are marked complete. See [how data moves between platforms](/integrations/data-flow) for the full path. ## Supported platforms Integrations are grouped by what they do. The platforms with dedicated guides on this site are in bold. | Category | Platforms | | ------------------------- | -------------------------------------------------------------------------------- | | CRM | **HubSpot**, **Salesforce** (production and sandbox), Attio, Pipedrive | | Sales engagement | **Outreach**, Salesloft, Apollo, Amplemarket, ActiveCampaign, Lemlist, Smartlead | | Conversation intelligence | **Gong** | | Data providers | Providers you bring your own account for, used by sourcing and enrichment | | Communication | Slack, Gmail | CRM and sales engagement platforms take part in the import, dial, log-back loop above. Data providers and communication tools do not import or log calls. They power sourcing, enrichment, notifications, and email. ## How to integrate In the Salesfinity dashboard go to **Settings → Connections & API**. Each platform shows a card with a short description and a **Connect** button. HubSpot, Salesforce, and Outreach use OAuth. Clicking Connect sends you to the platform's login page, where you approve the permissions Salesfinity asks for. The exact permissions are listed on each platform's guide. Some other platforms use an API key instead, which you paste into the card. After authorizing, the integration opens its configuration. The sections vary a little by platform, but these are the ones you will see most often: * **Call task source** — the user in the connected platform whose call tasks are imported when you import "all tasks" instead of a named list. * **Disposition mapping** — which outcome in the connected platform each Salesfinity disposition becomes when a call is logged. Salesfinity can suggest a full mapping automatically from the platform's outcome names, and you can adjust it. * **Contact field mapping** — which platform property fills each Salesfinity field (name, title, company, phone, email, and so on). * **Custom fields** — extra platform properties to bring across onto the contact, and for some platforms onto the account or deal. Go to the dialer, choose the platform as the list source, pick a list, and import. The first import is the real test of your field mapping, so check a few contacts before dialing. Every person on the team connects their own account. A connection belongs to one Salesfinity user, and calls are logged as that user in the connected platform. The exception is a team-shared integration, described next. ## Sharing an integration with the team A team admin or the team owner can turn on **Share with team** on their own HubSpot, Apollo, or Amplemarket integration. Sharing does two things: * **Mappings are shared.** Every member uses the owner's field and disposition mappings. Members see them read-only with a "Managed by" notice, and only the owner's configuration is editable. * **Members without their own connection use the owner's.** A rep who never connected the platform can still import and log calls through the shared connection. A rep who has connected their own account keeps using it for calls and only inherits the mappings. While a source is shared, each member's **call task source** is set by the admin in the shared configuration under "Call task source per member". A member who has not been assigned one cannot import their due tasks until they are. Only the owner can disconnect a shared integration. Salesforce, Outreach, Salesloft, Pipedrive, and ActiveCampaign are not shareable yet. Each member connects their own account. Team-level platforms such as Gong and Lemlist are connected once for the whole team by design. ## Where to next The full path from import to call log, sync states, and retries. Reconnect prompts, missing permissions, empty imports, and failed syncs. Add, move, and remove people in sequences without leaving Salesfinity. Ask questions of connected platforms and take actions with approval.