Skip to main content

Salesforce Integration

The Salesforce integration delivers leads. Every person Knock Knock App identifies — through chat, a contact form, a call, or a website form — is created as a Lead in your Salesforce org, matched by email and phone so nobody is duplicated. It is one-way: Knock Knock App writes Leads and reads nothing back.

Connecting Salesforce​

  1. Go to Settings → Integrations and find the Salesforce card.
  2. Choose the Environment — Production, or Sandbox if you want to connect a sandbox org (sandboxes sign in through Salesforce's test login).
  3. Click Connect, sign in to Salesforce, and approve the access request. Knock Knock App asks only for API access and a refresh token, never full-org access.
  4. You land back on the Integrations page with Salesforce connected successfully!

The card then shows Connected (with "(sandbox)" where relevant), your org's host name, and how many Salesforce API calls you have left today. You need the integrations permission in Knock Knock App (owners always have it).

note

If Salesforce reports that authorization is blocked, your Salesforce administrator has to approve Knock Knock App first — under Setup → Connected Apps OAuth Usage — or run the connection themselves. Finish the approval within a few minutes of clicking Connect; if it times out, start again from Connect. A sign-in error on a sandbox org usually means the Environment is still set to Production.

Using your own Salesforce app​

By default you connect through the Knock Knock Salesforce app. If your org policy requires your own, switch on Use my own Salesforce app on the card and:

  1. In Salesforce, create an External Client App (not a legacy Connected App).
  2. Copy the Callback URL shown on the card into the app, exactly as shown.
  3. Paste the app's Consumer Key and Consumer Secret into the card and click Save. Saving disconnects any existing connection, so click Connect again afterwards.

The secret is never shown back to you. Remove switches back to the Knock Knock app and disconnects; reconnect afterwards.

What syncs to Salesforce​

  • A Lead per person, created the moment a visitor is identified by chat, contact form, call, or form submission — never a Contact, and never converted.
  • Matching: an existing open Lead with the same email is updated; failing that, one with the same phone or mobile number. Phone matching is exact, so a number stored in a different format can produce a second Lead. Your org's duplicate rules still run — they flag rather than block.
  • Fields: first and last name, company, email, phone, city, state, country, website, and Lead Source (Knock Knock). Salesforce requires a last name and a company, so when the visitor didn't give one, the company falls back to their email domain (never a free-mail domain) and then [Unknown], and the last name to the email's local part and then Unknown. LinkedIn URLs, tags, and the capture source go into Description.
  • If your org rejects an optional field — a picklist value or a validation rule on state, country, city, website, lead source, or description — that field is dropped and the Lead is saved without it rather than lost.

Lead source, owner, an external-ID field for upserts, and a custom field map can be set for your account by support on request.

What Salesforce doesn't get​

Salesforce is delivery only. Compared with LeadConnector or HubSpot:

  • No chat-transcript or call-summary notes, no tasks, no opportunities or pipeline stages.
  • Nothing flows back — there are no Salesforce webhooks or polling into Knock Knock App.
  • Nox doesn't read Salesforce, so CRM lookups, stage questions, and enrichment need LeadConnector or HubSpot connected alongside it.

Connection health​

Knock Knock App checks the connection every few hours. If Salesforce revokes access — the token was rotated away, or the org's 30-day idle limit passed — the card turns amber with Reconnection needed: "Salesforce rejected our access. Reconnect to resume sending leads." Leads stop syncing until you click Reconnect. A transient failure shows "Last check of your Salesforce connection failed. Leads may not be syncing." instead.

Disconnecting​

Click Disconnect and confirm — "New leads will stop syncing to Salesforce. Existing records stay untouched." The connection is revoked at Salesforce and your credentials are cleared; nothing already in Salesforce is removed.

Next Steps​

  • HubSpot and LeadConnector — CRMs with two-way sync, notes, and pipelines.
  • Webhooks — if you'd rather push lead events into your own automation.
  • Lead API — the API for pulling leads out programmatically.