Salesforce

Teams

Connect your Salesforce org so that leads collected through your team's Lynkle cards are automatically created as records in Salesforce. You can choose to sync them as Leads or Contacts.

When someone shares their contact details through a team member's card, Lynkle creates a record in Salesforce and assigns it to the team member who collected the lead.

Before you start

  • A Lynkle Teams subscription with organization owner role
  • Salesforce admin access to create an External Client App
  • A Salesforce edition that supports API access

Set up the Salesforce app

Before connecting in Lynkle, a Salesforce admin needs to create an External Client App. This is a one-time setup.

  1. Create an External Client App

    In Salesforce, go to Setup > Apps > App Manager and click New External Client App.

    Enter an app name (for example, "Lynkle") and your contact email.

  2. Configure OAuth settings

    Enable OAuth Settings and set the Callback URL to:

    https://lynkle.com/settings/integrations/salesforce/callback

    Add the following OAuth scopes:

    • Manage user data via APIs (api)
    • Perform requests at any time (refresh_token)
  3. Configure flow and security settings

    Under Flow Enablement, enable Authorization Code and Credentials Flow.

    Under Security, enable:

    • Require Secret for Web Server Flow
    • Require Secret for Refresh Token Flow

    Click Create.

  4. Get the Consumer Key and Consumer Secret

    After creating the app, go to the Settings tab. Under OAuth Settings, click Consumer Key and Secret. Salesforce may send you a verification code to confirm your identity.

    Copy the Consumer Key and Consumer Secret. You'll need them in the next section.

    New Salesforce apps can take a few minutes to become active. If you see an "invalid client" error when connecting, wait a few minutes and try again.

Connect Salesforce to Lynkle

  1. Open integrations settings

    In Lynkle, go to Settings > Integrations and click Connect.

  2. Choose the scope

    Select Entire team to set up an organization-wide integration.

  3. Select Salesforce

    Click Salesforce from the list of organization providers.

  4. Enter your credentials

    Paste the Consumer Key and Consumer Secret from the Salesforce app you created, then click Connect.

  5. Authorize in Salesforce

    You'll be redirected to Salesforce's login page. Sign in and authorize Lynkle to access your org.

After authorizing, you'll be redirected back to Lynkle and the integration will appear under the Organization section on the Integrations page.

Choosing the record type

By default, Lynkle syncs leads as Lead records in Salesforce. To change this:

  1. Click Manage on the Salesforce integration.
  2. Choose between Lead and Contact.
  3. Click Save.

When set to Lead, Lynkle populates the Company field using the lead's email domain and sets the LeadSource to "Lynkle". When set to Contact, Lynkle creates a Contact record instead.

How it works

Once connected, the integration works automatically for all team members:

  • When a lead is collected through any team member's card, Lynkle looks up the team member's email in your Salesforce org and creates a record assigned to that Salesforce user.
  • If the team member's email doesn't match an active user in Salesforce, the sync is skipped for that lead.
  • The record includes the lead's first name, last name, email, and phone number.

Disconnecting

To remove the integration, click Manage on the Salesforce integration and then Disconnect. Records that were already created in Salesforce will remain.

If you also want to revoke API access, delete or deactivate the External Client App in Salesforce Setup.

Troubleshooting

  • "Invalid client" error when connecting. Newly created Salesforce apps can take a few minutes to activate. Wait and try again. Also verify that the Consumer Key and Consumer Secret are correct.
  • Integration shows "Disconnected" status. The Salesforce refresh token may have expired or been revoked. Click Reconnect on the integration to re-authorize.
  • Leads not appearing in Salesforce. Verify that the team member who collected the lead has a matching active user in your Salesforce org (same email address). Also check that the External Client App has the "Perform requests at any time" scope enabled.
  • "Perform requests at any time" scope missing. Without this scope, Salesforce won't issue a refresh token and the integration cannot maintain a long-lived connection. Edit the External Client App in Salesforce and add this scope.