Deliver leads to Salesforce

What you’ll accomplish

Salesforce is available now. Connect the intended organization, preserve the required Lead fields, and verify a test result in Recent deliveries.

Finish with

A synthetic Salesforce Lead with its delivery record

1. Connect and map SalesforceFollow the CRM connection guide, then expand Salesforce in Integrations.

   Map visitor fields to Lead fields. Defaults are LastName, Email, Phone, and Company. Keep a working path for LastName and Company before saving and selecting Salesforce in the agent’s Lead capture tab.

2. Submit a synthetic leadUse test values such as Taylor Example, Example Works, and `taylor@example.test`.

   Test connection verifies credentials only. Trigger the configured form to test the actual Lead creation path.

3. Read the outcomeInspect Salesforce’s Recent deliveries for the CRM record ID or a specific error.

   A delivered item has a Lead ID. If LastName is not mapped but name is present, Chat4U uses its last space-separated portion as LastName and the first portion as FirstName where present; use explicit fields when your process needs a particular name structure.

Change and recovery rules

• The mapping is shared by every project agent that selects Salesforce. Identify affected agents, save, and repeat a synthetic submission after a Field ID or destination change.
• Chat4U queues the delivery, records the Salesforce record ID, and scrubs lead PII from its lead record.
• Invalid grants or missing refresh tokens mark the integration Needs reconnect. Disconnecting clears tokens and instance URL, stops delivery, and leaves the mapping saved.
• For “OAuth app not found,” authorize against an organization with the Chat4U app. In local development, the Connected App credentials and callback URL must belong to the same organization.

Last updated on