---
title: "Salesforce - Auto-Respond Docs"
description: "Push every Auto-Respond lead into Salesforce as a Lead or Contact, with address, description, and lead source populated."
source: https://auto-respond.com/docs/integrations/salesforce/
---

![Salesforce documentation guide](https://auto-respond.com/assets/docs/integrations-salesforce.svg "Salesforce Documentation")

A visual guide to the Salesforce documentation, covering the setup, configuration, and workflow details explained on this page. Documentation illustration for Salesforce.

# Salesforce

The Salesforce integration creates records in your Salesforce org for every lead Auto-Respond handles. The connection uses OAuth - click **Connect**, authorize on Salesforce, and you’re done. You then choose whether Auto-Respond should create records as **Leads** or **Contacts** depending on how your org is set up.

ℹ️

The Salesforce card is on any source’s **Messaging Settings** → **Integrations** tab.

## What gets synced

Every record pushed into Salesforce includes:

- First name
- Last name
- Company
- Email
- Phone number
- Street, city, state, postal code
- Description (the inquiry details, when the job-description option is on)
- Lead source
- Status

## Connecting Salesforce

### Open the integration

In Auto-Respond, open the source → **Messaging Settings** → **Integrations** tab → **Salesforce** card.

### Click Connect

You’ll be redirected to Salesforce to authorize the connection. Sign in with the Salesforce user that should own the records being created, then approve the permissions.

### You’re returned to Auto-Respond

After authorizing, you land back on the Salesforce integration card. The connection is now set.

### Choose record type - Lead or Contact

On the card, pick whether Auto-Respond should create Salesforce **Leads** or **Contacts** for each inquiry.

- **Leads** - The standard choice for most sales orgs. Every inquiry becomes a new Salesforce Lead that your team can qualify and convert.
- **Contacts** - Use this if your Salesforce setup skips the Lead object and goes straight to Contacts/Accounts.

### Validate

Click **Validate Connection** to confirm everything is wired up.

### Turn on the Enable toggle

Nothing is sent to Salesforce until **Enable** is on.

## Options

### Enable

Turns the integration on or off for this source. Default: **off**.

### Inherit from parent

Only shown on a location with a parent business. When **on**, the location uses the parent’s Salesforce connection and settings. When **off**, it overrides them.

### Record type: Leads or Contacts

Default: **Leads**.

Choose whether new Salesforce records are created as Leads or as Contacts. Switching this only affects _new_ records - records already pushed to Salesforce aren’t moved or duplicated.

### Include job description

Label: **Include job description** (setting: `sendJobDescription`). Default: off.

- **When on** - The description of the inquiry (what the customer is asking about, the job details captured in the conversation) is written into the Salesforce record’s **Description** field.
- **When off** - The Description field is left alone. Only contact info and standard fields are populated.

Turn this on when your sales reps need the context of the inquiry directly on the record. Turn it off if your Salesforce workflow fills the Description field from somewhere else.

### Create customer only when contact info is captured

Default: off.

- **When on** - The Salesforce record is only created after a phone number or email is collected.
- **When off** - The record is created at first contact, even before contact info is shared.

### Create only for new leads

Default: off.

- **When on** - If a matching Salesforce record already exists (on email or phone), it’s left alone.
- **When off** - Existing records are updated with any new info Auto-Respond has.

### Include source name

Default: off.

- **When on** - The source name is added to the Salesforce record. It typically shows up on the Lead Source or within the Description.
- **When off** - Source isn’t included.

### Validate Connection

Tests the OAuth token against Salesforce. If the user’s session has been revoked, you’ll see the error and need to reconnect.

### Disconnect

Removes the OAuth connection. Confirmation required.

## Matching and deduplication

Salesforce records are matched on email and phone. With **Create only for new leads** on, existing matches are skipped.

## Disconnecting

Open the Salesforce card → click **Disconnect** → confirm. The OAuth connection is removed from Auto-Respond. If you want to revoke the access on Salesforce’s side too, do that from your Salesforce user’s connected-apps settings.

## Troubleshooting

- **“Validation failed” / token expired** - The OAuth token is no longer valid. Click **Connect** again and re-authorize.
- **No records appearing** - Confirm **Enable** is on. Check your **Create customer only when contact info is captured** setting. Also confirm the Salesforce user you connected with has permission to create the chosen record type (Leads or Contacts).
- **Records created as the wrong type** - Check the record-type setting on the card. Changing it only affects new records.
- **Description empty** - Turn on **Include job description** if you want the inquiry to populate the Description field.
- **Duplicates** - Enable **Create only for new leads** to skip matches.

***

Questions about the Salesforce integration? Email <support@auto-respond.com>.

Last updated: April 21, 2026