Before you begin

  • Create a Salesforce connected app or integration user with permission to create Lead records.
  • Confirm the target org requires `LastName` and `Company` for Lead creation.
  • Create optional custom fields for InstaChime lead ID, lead score, sentiment, source platform, and raw source IDs.
  • Choose middleware, Zapier, or Make to receive InstaChime webhooks and authenticate to Salesforce.

Lead field map

  • `lead.customer_name` -> `FirstName` and `LastName`; if a single name is present, use it as `LastName`.
  • `lead.company` or a fallback such as `Individual` -> `Company`.
  • `lead.email` -> `Email`.
  • `lead.phone` -> `Phone`.
  • `lead.source_platform` -> `LeadSource` or a custom source field.
  • `lead.message` -> `Description`.

Lead create payload

{
  "FirstName": "Jamie",
  "LastName": "Lee",
  "Company": "Acme",
  "Email": "jamie@example.com",
  "Phone": "+15555550123",
  "LeadSource": "InstaChime",
  "Description": "Need pricing today",
  "InstaChime_Lead_ID__c": "lead_uuid"
}

Verify

  • Send a sample `lead.created` webhook through the Salesforce bridge.
  • Confirm a Lead record is created with the correct owner, assignment rule, and source fields.
  • Confirm the Salesforce record ID is saved in the delivery response.
  • Confirm validation-rule failures are visible in `/integrations` so admins can fix the mapping.

Exact Salesforce setup

  • Create or select a Salesforce integration user.
  • Create a Connected App or OAuth flow for API access.
  • Confirm the integration user can create Leads and read assignment-rule behavior if assignment rules are used.
  • Create custom fields such as `InstaChime_Lead_ID__c`, `Source_Platform__c`, `Lead_Score__c`, and `Sentiment__c` if needed.
  • Build a bridge, Zap, or Make scenario that receives `lead.created`.
  • Map the lead to Salesforce Lead fields and call the REST sObject create endpoint.
  • Return the Salesforce Lead ID in the webhook response.

Salesforce required fields

  • Always send `LastName`. If the source has only a company name, use a fallback contact label agreed by sales operations.
  • Always send `Company`. For consumer leads, use a fallback such as `Individual` only if your Salesforce rules allow it.
  • Send `LeadSource` as `InstaChime` or the original ad platform based on your reporting model.
  • Send `Description` with the original lead message and key qualifying answers.
  • Include owner or assignment rule headers only if your Salesforce process requires them.

Salesforce troubleshooting

  • If creation fails with required-field errors, inspect Salesforce validation rules and page-layout required fields.
  • If picklist values fail, use exact API values, not display labels.
  • If assignment is wrong, verify assignment rules, owner mapping, and integration user defaults.
  • If duplicates appear, add a Salesforce duplicate rule or bridge-level search before create.
  • If API access fails, check Connected App policy, token expiry, IP restrictions, and user API permission.

Official references

These vendor-owned pages explain the controls and requirements referenced in this guide.