How to Connect Help Scout with Salesforce (2026)

How to Connect Help Scout with Salesforce

Connecting Help Scout with Salesforce brings your support inbox and CRM together, giving both teams a complete picture of every customer. Help Scout's shared inbox and knowledge base handle customer conversations, while Salesforce manages accounts, opportunities, and the sales pipeline. With this integration, support agents see Salesforce account data alongside conversations, and sales reps see support history alongside deals.

Help Scout does not offer a native Salesforce integration out of the box. The primary connection methods are Zapier, Make, or a custom API integration using Help Scout's Mailbox API 2.0 and Salesforce's REST API. There are also third-party connector apps on Salesforce AppExchange that bridge the two platforms. This means the integration requires more setup than a one-click marketplace install, but the flexibility of API-based connections allows you to build exactly the workflow your team needs.

This combination is popular with teams that prefer Help Scout's human-focused approach to support — its clean shared inbox feels more like email than a traditional ticketing system — while using Salesforce as their system of record for all customer and revenue data.

Integration Methods

Native Integration Setup

Step 1: Choose Your Connection Method

Since there is no native one-click integration, decide between Zapier (fastest to set up), Make (more flexible scenarios), or a custom API build (most control). For most teams, Zapier provides the best balance of speed and functionality. Sign in to Zapier and create a new Zap.

Step 2: Configure Help Scout as the Trigger

In Zapier, select Help Scout as the trigger app. Connect your Help Scout account using an API key from Help Scout > Your Profile > Authentication > API Keys. Choose your trigger event — "New Conversation" is the most common starting point. Select the mailbox to monitor.

Step 3: Set Up Salesforce as the Action

Add Salesforce as the action step. Connect your Salesforce account via OAuth. Choose an action like "Create or Update Contact" or "Create Case." Map Help Scout conversation fields to Salesforce fields: customer email to Contact Email, conversation subject to Case Subject, mailbox name to Case Origin.

Step 4: Add Field Mapping and Filters

Map additional fields: Help Scout tags to Salesforce Case fields, conversation status to Case status, and assigned agent to Case Owner. Add Zapier filter steps if you want to only sync certain conversations — for example, only conversations tagged "sales-related" or from customers in a specific Help Scout mailbox.

Step 5: Test and Activate

Run a test by creating a sample Help Scout conversation and verifying the Salesforce record is created correctly. Check field mapping accuracy, especially for custom fields. Once validated, turn on the Zap. Consider creating a reverse Zap (Salesforce trigger, Help Scout action) for bidirectional workflows.

Step 6: Set Up Salesforce Sidebar in Help Scout (Custom App)

Help Scout supports custom sidebar apps that can display external data. Build a simple sidebar app using Help Scout's App Framework that queries the Salesforce API to display account details, open opportunities, and deal values alongside Help Scout conversations. This requires development effort but dramatically improves agent context.

What Data Syncs

Use Cases

Automatic Case Creation for Enterprise Accounts

When a Help Scout conversation is created by a customer who exists in Salesforce as an Enterprise-tier account, a Zapier workflow automatically creates a Salesforce Case with high priority. The Salesforce account owner receives a notification, ensuring that high-value customers get immediate visibility from both support and sales teams.

Support-Influenced Pipeline Reporting

By syncing Help Scout conversation data to Salesforce Cases linked to Accounts, you can build Salesforce reports showing the correlation between support interactions and deal outcomes. Track metrics like "average support tickets before purchase" or "churn rate by support satisfaction score" using standard Salesforce reporting tools.

Automation Recipes

• When: A new Help Scout conversation is created Then: Search Salesforce for a matching Contact and create a Case linked to their Account
• When: A Help Scout conversation receives a "Great" satisfaction rating Then: Update the Salesforce Contact's "Last Positive Support Experience" field with the date
• When: A Salesforce Opportunity moves to "Closed Won" Then: Add a "customer" tag to the corresponding Help Scout customer profile
• When: A Help Scout conversation is tagged "feature-request" Then: Create a Salesforce Task on the Account for the product team to review
• When: A Help Scout conversation has been waiting for agent reply for 24+ hours Then: Post a Chatter update on the Salesforce Account record alerting the account team

Troubleshooting

Zapier Not Triggering on New Conversations

Verify your Help Scout API key has not expired. Go to Help Scout > Your Profile > Authentication and check the key status. Also confirm the selected mailbox in the Zapier trigger matches the mailbox where conversations are being created. If using Help Scout's new inbox, verify the Zapier integration supports the latest API version (Mailbox API 2.0).

Salesforce Contact Not Found for Matching

When using a "Find or Create Contact" Zapier step, ensure the search uses email as the match field. If your Salesforce org allows duplicate contacts with the same email, the search may return unexpected results. Enable Salesforce duplicate rules under Setup > Duplicate Management to prevent this issue.

Limitations

Without a native integration, real-time sync is limited by Zapier's polling interval (1-15 minutes depending on plan) or Make's scheduling settings. Help Scout's API does not support webhooks for all event types, so some conversation updates may not trigger reliably. Bidirectional sync requires separate Zaps for each direction, which can create loop risks if not carefully configured with filter steps. Help Scout's customer profile fields are more limited than Salesforce Contact fields, so not all Salesforce data can be pushed back to Help Scout. File attachments from Help Scout conversations do not transfer to Salesforce Cases through Zapier.