What Does a CRM Integration Do?
Alta’s CRM integrations help keep your sales data in sync with your outreach activity automatically.
When you connect a CRM, Alta can create and update records as prospects move through your campaigns. This helps your team maintain a clean and up-to-date view of campaign activity, prospect engagement, and pipeline progress without manual data entry.
With a CRM integration, Alta can sync information such as:
Prospect details
Company information
Email and LinkedIn activity
Calls and replies
Outcomes, such as booked meetings or not interested
Notes and call summaries
Supported CRMs
Alta currently supports the following CRM integrations:
Salesforce
HubSpot
Pipedrive
Zoho
Attio
Odoo
Each CRM has a slightly different setup and sync structure, but the general connection process is similar.
How to Connect Your CRM
Step 1: Go to Settings
From your Alta workspace, go to Settings.
Step 2: Open Integrations
Click Integrations.
Step 3: Select Your CRM
Choose the CRM you want to connect:
Salesforce
HubSpot
Pipedrive
Zoho
Attio
Odoo
Step 4: Click Connect
Click Connect next to your selected CRM.
Step 5: Authorize Alta
Follow the OAuth authorization flow.
You may need to log in to your CRM account and approve Alta’s access.
Make sure the CRM user account you use has permission to create and edit records.
Step 6: Configure DNC Settings
After the CRM is connected, configure your DNC settings.
This controls which prospects Katie should not contact.
You can configure DNC settings at the contact level and/or company level.
Example: At each level, you can include filter rules. For example, you can select the Lifecycle Stage field from your CRM, choose “In” as the operator, and then select the Lifecycle Stage values that you do not want Alta to contact.
Step 7: Configure Push Settings
Push Settings.
Push Settings control what Alta sends to your CRM and when.
Push Settings: What Gets Synced and When
Push Settings control which Alta activities are sent to your CRM.
You can configure Alta to push different types of records and activities depending on your workflow, and decide when to trigger the push.
Push of Contacts and Leads
Alta can create or update CRM records when prospects are added to campaigns.
Depending on your CRM, these records may be created as:
Contacts
Leads
People
Organizations
For example, in Salesforce, you may be able to choose whether Alta creates a Lead or a Contact, while in HubSpot, the Lead option is not available. Only Contacts are supported.
Push of Companies
Enabling Push Companies will create companies in your CRM if Alta does not find an existing company when pushing contacts.
When to Push the contact /leads
There are different trigger options that define when Alta should push newly created contacts or leads to the CRM.
These triggers are based on when Katie’s outbound efforts reach a new stage with prospects.
You can select one or multiple triggers from the available options.
On Prospect Created — Fires the moment a prospect is added to a campaign in Alta. Useful for creating a Contact or Lead record in your CRM immediately.
On First Outreach — Fires when the very first message/call is sent to a prospect (step 1 of the workflow). Great for logging that active outreach has begun.
On LinkedIn Connection Accepted — Fires when a prospect accepts a LinkedIn connection request sent through Alta. Signals a warm relationship milestone.
On Prospect Reply — Fires when a prospect replies to any outreach. Typically used to notify the CRM that a conversation has started.
On Phone Fetched — Fires when Alta successfully enriches/retrieves a phone number for a prospect. Useful for syncing the phone number to the CRM contact record.
On Call Completed — Fires after a call to a prospect ends. Can push call disposition, duration, and summary to the CRM.
On Meeting Booked — Fires when a meeting is booked with a prospect. Often used to create a Deal or move a contact to a new CRM stage. ( You will need to manually tag the prospect in the Inbox with the tag “Meeting Booked,” and this will activate the trigger.)
On Prospect Outcome Changed — Fires when a prospect's outcome is updated in Alta (For example: Qualified, Not Interested, or Booked Meeting outcome from the Reply Assistant). Keeps CRM deal stages in sync.
On Every Prospect Outreach — Fires on every outreach step executed (every email, LinkedIn message, or call). Useful for logging all touchpoints as CRM activities.
On Prospect Outreach Ended — Fires when a prospect's workflow sequence finishes or is terminated (completed, failed, or manually ended). Signals the outreach cycle is over.
On Prospect Status Changed — Fires when the prospect’s status changes mid sequence, for example, paused, resumed, or moved to awaiting reply. This is useful for tracking workflow status in the CRM. This status changes automatically using AI.
Step 8: Configure Field Mapping
Once you select the specific triggers you want to push to your CRM, the next step is to configure your Field Mapping.
Field Mapping controls how Alta fields match the fields in your CRM.
For example, you can map:
First Name
Last Name
Email
Job Title
Company Name
LinkedIn URL
Custom fields
Additional Notes:
Add additional Fields: You can click the Add Field button and add any additional mapping configuration you want. For example, you can configure the lead source to be Alta. To use this option, make sure your CRM includes Alta as one of the available lead source values.
The Type should be Dynamic when each prospect has an individual value. For example, First Name would be dynamic because each prospect has a different value.
Static vs Dynamic: The Type should be Static when you want the same value to be pushed to the field for all prospects.
For example, for the Lead Source field, the Type would be Static and the Value would be Alta. This means the same value will be applied to all prospects.
Another example would be when you want to select one of the dropdown values from your CRM for a specific field. In this case, you would need to select the Type “Static,” which will then allow you to choose a value from the fields you have in your CRM. Once you select the specific value, all prospects being pushed will have that value from the dropdown options in your CRM.
Grey Fields: When a field appears grey, it means that the field is required in your CRM. This means you will need to select a value in order to save it. You will also not be able to delete that field.
Send on Update:
Send on Update is a toggle on each field mapping row. It controls whether Alta should send that field’s value to the CRM when an existing record is updated, not only when the record is first created.
When Alta syncs with the CRM, a field can be sent in two cases:
Moment | What it means |
Create | A new contact, lead, or company is created in the CRM for the first time |
Update | An existing CRM record is updated, such as when a prospect status changes or a new activity is logged |
The Send on Update setting controls what happens during the Update moment:
Setting | What Alta does |
ON | Alta sends and overwrites this field’s value in the CRM every time the record is updated |
OFF | Alta only sends this field when the record is first created. During updates, Alta leaves the field unchanged in the CRM |
Turn it ON: for fields that should stay synced with Alta’s latest data, such as Prospect Status, Last Activity Date, or Outcome. This is best when Alta owns the field and the CRM should always reflect the most current value.
Turn it OFF: for fields that should only be set once, such as Lead Source or Original Campaign. This is also best when the CRM team may manually update the field and you do not want Alta to overwrite their changes.
A simple rule of thumb: if the field changes over time and Alta owns it, turn Send on Update ON. If the field is a one time value or managed by the CRM team, turn it OFF.
Push Activities
Alta can log outreach activity in your CRM, including:
Emails sent
LinkedIn messages
Calls
SMS
WhatsApp
This gives your team visibility into the full engagement history for each prospect.
The triggers you select will determine when activities are pushed to the CRM.
Activity Mapping is where you define how each activity is mapped in the CRM. If you toggle the option to map it manually, you can select where the activity should be pushed, such as a note, task, email, or another available option.
If you map it manually, make sure all important fields are mapped correctly.
Troubleshooting
Manage Connection
Allows you to view and edit the settings of an existing CRM integration (e.g. HubSpot, Salesforce, Pipedrive). This is where you can update field mappings, sync preferences, and other configuration options.
When to use it: When you need to update how Alta syncs with your CRM — for example, changing which fields are mapped, adjusting sync frequency, or modifying pipeline/stage mappings after your CRM setup has changed.
---
Reauthorize Connection
Used to refresh or re-establish the authentication credentials for an existing integration.
When to use it: When the integration stops working or shows an authentication error — this typically happens after a password change, token expiration, or a permissions update in the CRM. Also use it if someone who originally connected the CRM has left the team.
---
CRM Sync Log
Shows a log of past sync activity between Alta and the CRM, including what was synced, when, and whether it succeeded or failed.
When to use it: When you want to verify that data is flowing correctly, troubleshoot a missing record, or confirm that a recent activity (like a reply or meeting) was pushed to the CRM.
---
Disconnect
Removes the active integration between Alta and the CRM.
When to use it: When you're switching to a different CRM, retiring an old connection, or need to fully reset the integration before reconnecting with new credentials or a different account.