Your reps work their outreach in LGM, but your single source of truth lives in Salesforce. Instead of copying connection statuses and conversations across by hand, this integration uses Make to do it for you. Three ready-made Make scenarios listen to your LGM activity and write it straight onto the matching Salesforce Contact, creating the Account and Contact first if they don't exist yet. You set it up once, and your CRM stays in sync on its own.

Key benefits

The integration is built from three Make scenarios. Each one listens to a different LGM event and updates Salesforce accordingly. Run together, they paint the full LinkedIn relationship lifecycle plus the conversation history on every contact.

Tip: The three scenarios are designed to work as a set. Enable all of them so a contact moves cleanly from Connection Request Not Sent → Connection Request Sent → Connected, with every message logged along the way.

Every Make plan comes with a monthly allowance of credits, and each module that runs uses one.

That's easy to absorb on a single campaign, but keep it in mind if you plan to run this across many identities and campaigns at once. Volume scales fast, so check your credit usage in Make once your first campaign has been running for a few days, and size your plan from there.

You'll need three accounts connected, plus your LGM API key and the right Salesforce access:

1. Create your Make account: Free to get started.

2. Retrieve your LGM API key: Go to All settings → Integrations & API → API :

3. Add an LGM module in Make: Choose an LGM trigger or action, click Create a connection, and paste your API key.

The Salesforce side has two requirements:

Note: When you add Salesforce as a connection inside Make, it uses OAuth. You'll log into your Salesforce account and authorize the connection during setup.

Two scenarios write to custom fields on the Contact object, so create these first. Use the exact field names and labels below, so you won't have to change anything inside the Make scenarios.

In Salesforce, go to Setup → Objects and Fields → Object Manager → Contact → Fields & Relationships → New, and create both fields.

Important: Set Connection Request Not Sent as the default so every new Contact starts at the right stage. The scenarios then move the value forward to Connection Request Sent and Connected on their own.

Each scenario comes as a downloadable blueprint at the bottom of this article that you can import into Make. The walkthrough below shows the full import once. The steps are identical for all three.

For each blueprint:

Note: Connections and webhooks never transfer with a blueprint. You'll always re-bind your own Salesforce account and create a fresh LGM webhook on import. That's expected.

Enable them in this order so each contact's record is built before it's updated.

Triggers when: you send a LinkedIn connection request from an LGM campaign.

What it does: looks up the Account by company name (creating it if it doesn't exist), looks up the Contact (creating it if it doesn't exist), then sets LinkedIn Relation to Connection Request Sent. New contacts are created with their name, job title, phone, short bio, and LinkedIn URL.

Before you turn it on: make sure both custom fields from Step 1 exist on the Contact object.

Triggers when: a prospect accepts your LinkedIn connection request.

What it does: finds the matching Contact and updates LinkedIn Relation to Connected. If the contact doesn't exist yet, it's created on the spot.

Note: This scenario assumes the contact already exists from Scenario 1. Running Scenario 1 first keeps your records clean and properly linked to their Account.

Triggers when: any message is sent or a reply is received in an LGM campaign, across LinkedIn and email.

What it does: finds or creates the Account and Contact, then logs a completed Task on the Contact for each message. The task records the channel and direction (e.g. New LinkedIn Reply), the date, and a description containing the message subject, body, campaign name, and identity.

Tip: Open any synced Contact and check the Activity section, and you'll see the full back-and-forth logged as completed tasks, giving reps the entire conversation history without leaving Salesforce.

Accounts are matched on the exact company name, and contacts on first + last name within that account. Keep company names consistent between LGM and Salesforce, otherwise a slightly different spelling will create a separate Account.

Each scenario covers one stage. Together they give you the complete picture: status plus conversation history. On their own, you only get part of the story.

Connect one campaign first, verify the records land correctly in Salesforce, then expand the webhook to your other campaigns.

The scenarios map to LinkedIn_URL and LinkedIn_Relation. If you rename or recreate these fields, update the mapping inside the Make modules to match.

These three scenarios are just a starting point. Once you're comfortable in Make, you can build your own on the same LGM triggers: sync to other objects, trigger when lead status changed, and more. The possibilities are endless.