> ## Documentation Index > Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Salesforce > Connect Salesforce as a Destination and map 1eyeᴬᴵ fields to your Salesforce contact and company properties. Push buyers and companies from your target lists into Salesforce, with full control over which fields go where. ### Before you begin * Admin or app-authorization permissions in the Salesforce account you're connecting * At least one Target List with contacts or companies in it * Admin or Marketer access to your 1eyeᴬᴵ workspace For this guide, we'll use Snowbricks as the example workspace. | Field | Example | | --------------- | ----------------------------------------------- | | Company | Snowbricks | | Domain | snowbricks.io | | Workspace admin | Matt Bru | | Admin email | [matt@snowbricks.io](mailto:matt@snowbricks.io) | ### Connect Salesforce Connecting Salesforce happens inside a destination workflow, at the Destination node. **Step 1: Open the Destination node** If Salesforce isn't connected yet, the node shows: > Salesforce · Not Connected \[Connect] Select Connect. **Step 2: Confirm the connection in 1eyeᴬᴵ** > Allow 1eyeᴬᴵ to access your Salesforce account? Link Salesforce to sync your target lists, deduplicate against existing contacts, and enrich your Salesforce records. Select Yes, continue. **Step 3: Continue to Salesforce** Opens a Salesforce-hosted login screen in a new window. Select Log In if you already have an account. **Step 4: Log in to Salesforce** Enter your Salesforce username and password, or continue with SSO, then select Log In. This is Salesforce's own secure login screen — your credentials are entered directly with Salesforce and never seen by 1eyeᴬᴵ. **Step 5: Choose your Salesforce org, if prompted** If you have access to more than one Salesforce org, choose the one that matches your 1eyeᴬᴵ workspace. **Step 6: Review and allow access** Review the permissions screen, then select Allow. **Step 7: Connection confirmed** The Destination node updates from Not Connected to Connected, and field mapping options appear. ### Field mapping Mapping is organized into four sections — Standard Contact Fields, Custom Contact Fields, Standard Company Fields, and Custom Company Fields. Each standard field has a Push checkbox — uncheck it if you don't want that field sent to Salesforce. Standard Contact Fields (example): | 1eyeᴬᴵ Field | Salesforce Field | Push | | ------------ | ---------------- | ---- | | First Name | FirstName | ✓ | | Last Name | LastName | ✓ | | Title | Title | ✓ | | Work Email | Email | ✓ | | Phone | MobilePhone | ✓ | | City | MailingCity | ✓ | | State | MailingState | ✓ | | Country | MailingCountry | ✓ | Custom Contact Fields — push activity data that doesn't exist as a standard Salesforce field: | 1eyeᴬᴵ Field | Salesforce Custom Field | | --------------------------- | ---------------------------------- | | Persona Name | Buyer\_Persona\_\_c (type=text) | | Target Page Last Visited At | Last\_Visited\_At\_\_c (type=date) | | Target Page | Target\_Page\_\_c (type=textarea) | | Target Page Visit Count | Visit\_Count\_\_c (type=number) | Select + Add more to map additional custom fields. Standard / Custom Company Fields work the same way, for company-level data (industry, description, employee count, revenue, address, and any custom company field). Select Save Destination once your mapping is set. ### Monitor pushed records From the Console, filter Salesforce pushes by All / Pushed / Pending / Failed. Select a contact to see the exact payload sent to Salesforce — contact fields and associated company fields together. ### Disconnect Salesforce * Open the workflow and select the Destination node * Select the menu next to the Connected status * Select Disconnect Disconnecting stops any workflows using Salesforce as a destination until you reconnect. Records already pushed to Salesforce remain there. ### Best practices **Connect with an account that has the right permissions** Use a Salesforce login with admin or app-authorization rights, so the connection doesn't get blocked by a permissions gap. **Review the permissions screen before allowing access** Know what you're granting 1eyeᴬᴵ access to before you select Allow. **Map required fields first** Make sure fields Salesforce requires (like Last Name) are mapped and populated before pushing, so records don't get stuck in Pending. **Re-authenticate if the connection breaks** If Salesforce revokes access (password change, admin policy, expired token), reconnect from the Destination node. ### Troubleshooting | Issue | What to check | | ------------------------------------------ | ----------------------------------------------------------------------------------------- | | Connect button doesn't open a login window | Your browser isn't blocking pop-ups for 1eye.app. | | Wrong Salesforce org connected | Disconnect, then reconnect and choose the correct org when prompted. | | A field isn't showing up in Salesforce | Confirm the field's Push checkbox is checked, and that the Salesforce field exists. | | Custom field mapping isn't saving | Confirm both the 1eyeᴬᴵ Field and the Salesforce Custom Field are selected before saving. | ### FAQ No. Salesforce login happens on Salesforce's own hosted page. 1eyeᴬᴵ never sees your username or password — only the access token Salesforce issues after you approve the connection. Workflows using Salesforce as a destination stop pushing until you reconnect. Records already pushed to Salesforce remain there. Yes. Open the Destination node, update your mapping, and save. New pushes will use the updated mapping. ### Next step Go to [Destinations](/destinations/destination) to build your first Salesforce workflow.