Quick answer

Create an External Client App in Salesforce with the client credentials flow, then open your Pipeline page, click Manage Integrations, open the Salesforce card, paste your My Domain URL, consumer key and secret, and click Save. From then on, qualified meeting requests, identified profile visitors and people who match your ideal customer profile land in your Salesforce as Leads, routed by your own assignment rules, each with a Task for its owner.

What lands in Salesforce

Someone who is already a Contact: we add a Task only. We never change a Contact's fields.
Someone who is an open Lead: we fill in fields that are blank today and add a Task. We never overwrite a value you already have.
Anyone else: we create a Lead with Lead Source Human Cloud, their name, email, company and title, their LinkedIn in the Description, and the answers to your booking questions. Your Lead assignment rules choose the owner.

Each Task is titled Human Cloud: asked to meet, Human Cloud: viewed your profile or Human Cloud: matches your ideal customer profile and lists what they did, what they answered and a link to your profile. It is assigned to the record's owner, or to the integration user when the owner is a queue.

Step 1: Create the External Client App

In Salesforce Setup, create an External Client App (or a Connected App). Turn on OAuth and enable the Client Credentials Flow. Start in your sandbox.

Step 2: Set the run-as integration user

Choose an integration user as the run-as user for the client credentials flow. It needs API Enabled, Create and Edit on Lead, Read on Contact, and Create on Task.

Step 3: Copy three values

Copy the app's consumer key and consumer secret, and your My Domain URL (it looks like https://yourcompany.my.salesforce.com, or https://yourcompany--sandbox.sandbox.my.salesforce.com for a sandbox).

Step 4: Connect it in Human Cloud

Open your Pipeline page, click Manage Integrations and open the Salesforce card. Pick Sandbox or Production, paste the three values and click Save. Before anything is saved, we connect to your Salesforce, check that we can create Leads and Tasks, and check that every field we write exists. If something is missing, the card tells you what in one sentence.

Anyone who can edit your profile can connect Salesforce. The secret is encrypted when you save it, and nobody can see it again: the card only shows that it is set.

Step 5: Send booking answers to your fields

If buyers answer questions when they book (for example Service of interest and Country), open your profile's Meet card, choose Edit how buyers book, and set Field name in Salesforce on each question to the field's API name, for example Service_of_interest__c. Answers without a field name are still listed in the Task.

Step 6: Send a test lead

On the Salesforce card, click Send test lead. Leave the email empty to create a new Lead, or enter the email of an existing Contact to confirm that only a Task is added. The test record is named Test Lead (Human Cloud) and its Task says you can delete it. When both look right, repeat Steps 1 to 6 with your production org.

Does this replace the request emails?

Yes. Once Salesforce is connected, meeting requests stop arriving by email and go to Salesforce instead. Requests that wait for you to accept or decline still email you, because the Accept and Decline buttons are in that email.

What happens if Salesforce blocks a record?

If a duplicate rule or a required field blocks a Lead, we log it as failed and try again on the next run. We never write to a near match. Fix the rule or field and the next run sends it.

How do I disconnect?

Open the Salesforce card and click Disconnect. We delete the stored secret and stop sending. Records already in your Salesforce stay there.