Salesforce setup

Documentation Index

Fetch the complete documentation index at: https://support.artisan.co/llms.txt

Use this file to discover all available pages before exploring further.

​

Connect Salesforce

​

Step 1: Install the Artisan package

​

Step 2: Enter your Salesforce instance URL and connect

1. Go to Settings → Integrations → Salesforce in Artisan.
2. Click Connect Salesforce.
3. Enter your Salesforce My Domain prefix.
4. Click Connect.
5. Authorize Artisan from Salesforce.
6. Return to Artisan after the connection is approved.

​

Permissions and access

• Leads and contacts: read existing people, create or update exported people, and avoid duplicate records.
• Accounts: read and update account records, associate contacts with the right account, and create accounts when needed during export.
• Opportunities: read opportunity data for context, DNC logic, and pipeline awareness.
• Users: match Salesforce users to Artisan team members so ownership and activity attribution are correct.
• List views: read Salesforce list views so they can be used as Artisan audiences or suppression lists.
• Activities: log emails, calls, LinkedIn messages, meetings, notes, and tasks from Artisan back to Salesforce.

​

Revoking access

​

What syncs between Salesforce and Artisan

• Leads and contacts sync between Salesforce and Artisan.
• Accounts sync between Salesforce and Artisan.
• Opportunities sync from Salesforce into Artisan for context, DNC, and pipeline awareness.
• Activities such as emails, calls, LinkedIn messages, meetings, notes, and tasks sync from Artisan into Salesforce.
• Salesforce list views can be used in Artisan as campaign audiences or suppression lists.
• Salesforce users sync from Salesforce so activities can be attributed to the right rep.

​

Recommended Salesforce setup

​

Basic sync

• Import Salesforce data Keep Import your Salesforce data turned on if you want Artisan to stay up to date with Salesforce leads, contacts, accounts, opportunities, and activity context. On first connection, Artisan runs a full backfill. After that, records continue syncing on a schedule.
• Choose how people export to Salesforce Choose how Artisan should create or update people in Salesforce:
  • Export as Leads: Artisan creates or updates Salesforce Lead records.
  • Export as Contacts: Artisan creates or updates Salesforce Contact records and associates them with Accounts.
  • Split by stage: Artisan routes people to Leads or Contacts based on their Artisan status. Use Export as Leads if your team wants new outbound prospects to enter Salesforce as leads. Use Export as Contacts if your team works primarily from accounts and contacts. Use Split by stage if your team wants low-intent prospects to stay as leads but higher-intent prospects to become contacts.
• Split by stage Split by stage lets you decide whether each Artisan status should export to Salesforce as a Lead or a Contact.
  • Positive statuses, such as Interested or Meeting booked, are often exported as Contacts.
  • Neutral, No response, or Negative statuses are often exported as Leads. If a status is not mapped, Artisan will not silently route it to a default object. This helps prevent accidental Account or Contact creation in Salesforce.
• Map a lead source You can map a lead source to stamp exported records with a Salesforce field and value, such as LeadSource = Artisan. This makes it easier to report on pipeline generated from Artisan campaigns.

​

Advanced sync

• Property mapping Use Property mapping to decide how Salesforce fields map to Artisan fields. Salesforce mappings are configured separately for Leads, Contacts, Accounts, and Opportunities because each Salesforce object can have different fields. For each mapped field, you can choose:
  • Artisan field: the field in Artisan, such as first name, email address, company name, or website.
  • Salesforce field: the Salesforce field that should map to that Artisan field.
  • Import priority: which system should win when Salesforce and Artisan both have a value. The winning value appears on the Artisan profile and can be used for personalization.
  • Export behavior: what Artisan should do when sending data back to Salesforce. Use CRM as the import priority when Salesforce should be the source of truth. Use Artisan when Artisan data should take priority. Export behavior options:
  • Fill if empty: Artisan only writes to Salesforce when the Salesforce field is blank. This is the safest default.
  • Overwrite: Artisan replaces the existing Salesforce value.
  • Do not export: Artisan does not write that field back to Salesforce. When a person is exported from Artisan to Salesforce:
  1. Artisan first checks whether that person already exists using their email address.
  2. If a matching Lead or Contact exists, Artisan updates the record based on your mapping settings.
  3. If no matching record exists, Artisan creates a new Lead or Contact based on your export setting. When Artisan exports a Contact:
  4. It also checks whether the person’s Account already exists in Salesforce. Artisan matches Accounts by website, domain, or normalized company name when available.
  5. If the Account exists, Artisan associates the Contact with that Account.
  6. If the Account does not exist, Artisan can create a new Account and associate the Contact with it. Artisan does not create Accounts for freemail domains, such as Gmail or Yahoo, unless the lead has an explicit company website. Manual single-lead exports always export the selected lead. Bulk exports follow the export setting you chose in Basic sync.
• Activity sync Activity sync controls which Artisan activities are logged back to Salesforce. Artisan can sync:
  • Emails
  • LinkedIn messages
  • LinkedIn connection requests
  • Calls and call recordings
  • Meetings booked
  • Notes
  • Tasks Activities are logged to the corresponding Salesforce Lead or Contact record, so the Salesforce activity timeline reflects the outreach Ava has performed. Salesforce stores activities as Tasks, Events, or Notes depending on the activity type. If a person exists as both a Lead and a Contact in Salesforce, Artisan deduplicates the person in Artisan and can associate activity with the relevant Salesforce records.
• Owner mapping Owner mapping links Salesforce users to Artisan team members. This controls who gets credit for records and activity in Salesforce when Ava works on behalf of your team. How it works:
  1. Artisan reads the Salesforce user list.
  2. You map each Salesforce user to the right Artisan team member.
  3. If email addresses match, mapping is usually automatic.
  4. You can set a default fallback owner for records that cannot be matched. If a Salesforce user is not mapped, records or activities may be assigned to a fallback owner based on your workspace setup. We recommend mapping every active Salesforce user involved in outbound, sales, or follow-up workflows.
• Status mapping Status mapping sends Artisan lead statuses back to Salesforce. For Salesforce Leads, Artisan can map statuses to the native Status picklist. For Salesforce Contacts, choose the custom Contact field that should receive Artisan status updates, then map each Artisan status to the matching Salesforce value. Status mapping is useful when your sales team uses Salesforce to prioritize follow-up or report on campaign outcomes.

​

Salesforce list views

• Use a Salesforce Lead list view as an audience for an Artisan campaign.
• Use an Account list view as a target account list.
• Use a list view of customers, competitors, or open opportunities as a suppression list.

​

Frequently asked questions