BotPulsar

Home/ Integrations/Salesforce

Integration

Salesforce WhatsApp integration

Upsert contacts and deals into Salesforce, against your own instance and organization.

The Salesforce connector writes contacts and deals into your own Salesforce instance, using your instance and organization identifiers and a separate login URL so sandbox and production environments can be connected independently. Matching fields are configurable, which matters in Salesforce deployments where the meaningful key is a custom external ID.

What it does

What the Salesforce connector supports

Capabilities

  • Create and update contacts
  • Create and update deals

What you'll need to connect

  • base_url
  • login_url
  • instance_id
  • organization_id
  • contact_id_field
  • deal_id_field
Common uses

What teams build with it

Create or update a Salesforce contact from an inbound WhatsApp conversation without duplicating an existing record.

Raise an opportunity when a WhatsApp qualification flow completes, so pipeline reporting stays inside Salesforce.

Connect a sandbox instance first through a separate login URL, and promote the same configuration to production once tested.

FAQ

Salesforce integration: common questions

Can I connect a Salesforce sandbox rather than production?

Yes. The connector takes a separate login URL alongside the instance and organization IDs, so a sandbox can be connected and tested independently of production.

Does it support custom external ID fields for matching?

Yes. Both contact and deal ID fields are configurable, so matching can target a custom external identifier rather than a standard field.

Do I need a developer to connect Salesforce?

No, connecting requires your instance and organization identifiers plus the login URL and matching fields — configuration, not custom code.

What Salesforce objects does the connector write to?

Contacts and opportunities (deals), both created and updated based on WhatsApp activity.

Will a duplicate contact be created if one already exists?

No. Matching runs against the configured contact ID field first, so an existing Salesforce contact is updated instead of duplicated.

Can an agency manage multiple Salesforce orgs from one BotPulsar account?

Each connection is scoped to one instance and organization ID, so an agency managing several client orgs would connect each one separately.

Start on WhatsApp today — from ₹300/month

Unlimited team members on every plan. 14-day trial, no setup fee, no annual lock-in.