GTM Plays + Salesforce integration

The GTM Plays Salesforce integration creates a Lead record in Salesforce for every lead your LinkedIn agents find. It connects through an OAuth app you create in your own org, checks for an existing open lead before creating one, respects your duplicate rules and sends data one way, from GTM Plays to Salesforce.

What the integration does

Salesforce calls itself an AI CRM (salesforce.com, checked October 2026). GTM Plays finds people on LinkedIn who show buying signals, scores their fit and runs outreach from your account. This integration puts those people into Salesforce as Leads, so your sales process starts where your team already works. See all integrations.

What syncs

Data flows one way, from GTM Plays to Salesforce. GTM Plays only queries Salesforce to check for an existing lead.

GTM Plays field	Salesforce Lead field
First name	FirstName
Last name	LastName (falls back to first name or email if missing)
Company name	Company ("[not provided]" if missing, as Salesforce requires it)
Job title	Title
Work email	Email
Phone	Phone
Company website	Website
Company industry	Industry
(fixed value)	LeadSource = GTM Plays
Headline, signal, GTM Plays score with top reasons, LinkedIn URL	Description

Duplicates. Before creating a lead, GTM Plays looks for an unconverted Lead with the same email, or, if there is no email, the same first name, last name and company. If one exists, nothing is created. If your org's own duplicate rules block the insert, GTM Plays treats the lead as already there.

When leads are sent

• New leads, automatically. With "Automatically send new contacts" switched on (it is on by default), every new lead your agents find is sent as it arrives. Contacts you import into an agent count as new leads too.
• One contact at a time. Open any contact's drawer and choose Send to… to send just that person, whether or not automatic sending is on.

Delivery runs in the background after the action that caused it, so finding or importing leads never waits on Salesforce. The result of the last delivery (time, status and any error) shows on the Salesforce card in Settings → Integrations.

How to set it up

You connect through your own Salesforce app, so access stays under your admin's control.

1. Open GTM Plays. Go to Settings → Integrations → Salesforce and copy the Callback URL shown there.
2. Create an app in Salesforce. In Setup → App Manager, create a New External Client App (or a Connected App if your org still allows it). Salesforce restricts new Connected App creation by default from the Spring '26 release and recommends External Client Apps instead (Salesforce).
3. Enable OAuth. Paste the callback URL and add the scopes Manage user data via APIs (api) and Perform requests at any time (refresh_token, offline_access).
4. Copy the consumer key and secret into GTM Plays.
5. Choose your login URL. Use https://login.salesforce.com for production, https://test.salesforce.com for a sandbox, or your My Domain.
6. Connect. You are sent to Salesforce to approve access, then back to GTM Plays. Press Check connection to confirm; it does not create a test lead.

GTM Plays uses the OAuth authorisation code flow with PKCE and keeps the refresh token encrypted, so the connection keeps working without you signing in again.

Use cases

• Lead routing. Leads arrive with Lead Source "GTM Plays", so assignment rules, queues and reports can treat them as their own source.
• Context for reps. The Description field carries the buying signal and score reasons, so a rep knows why the person is worth a call before opening LinkedIn.
• Clean data. Duplicate checks and your own duplicate rules stop the same person landing twice.
• Scoring alignment. Use the GTM Plays score alongside your own lead scoring model.

Good to know

• GTM Plays creates Leads only. It does not create Contacts, Accounts, Opportunities or Tasks, and it does not update existing records.
• Replies are not written to Salesforce. To get reply alerts elsewhere, use the Slack or webhook integrations.
• GTM Plays runs LinkedIn outreach; it does not book meetings by itself.

Security and data handling

• Your client secret, refresh token and access token are encrypted (AES-256-GCM), used only on GTM Plays' servers and never sent back to your browser.
• GTM Plays only calls Salesforce's own domains, checked against the login and instance URLs your org returns.
• Empty fields are left out rather than sent as blanks. Disconnecting from Settings → Integrations stops delivery; Leads already created stay in Salesforce.

Troubleshooting

The integration card in Settings → Integrations shows the last delivery and the error message, if any. The common ones:

• "The key was rejected (401)". The key was revoked, expired or mistyped. Paste a new one and press Verify.
• "The key is missing a permission this needs (403)". Give the key the access listed in the setup steps, then verify again.
• Rate limiting (429). The service asked GTM Plays to slow down. The current delivery stops and the message shows on the card; later leads go out with the next delivery.
• "The service redirected the request". Usually the wrong account region or URL. GTM Plays never follows redirects with your key attached.
• "This Salesforce user can’t create Leads". Connect as a user whose profile can create Leads.
• "No refresh token was issued". Add the refresh_token, offline_access scope to your app and connect again.
• "Reconnect Salesforce". The connection lost its instance URL or token; press Reconnect in the Salesforce card.

Plans and next steps

The Salesforce integration is included in Pro at $149 a month. Start a 7-day free trial, connect your org and let your agent fill the Lead queue with people showing intent on LinkedIn. To read contacts from your own code, see the REST API.