Source connector

Help Scout connector

Help Scout integration for databases, warehouses and BI tools

Shared inbox help desk with customer conversation history. Datrise captures Help Scout entities such as conversations, customers, mailboxes, threads, tags and satisfaction ratings, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Help Scout Mailbox API 2.0 authenticates with OAuth 2.0, incremental runs key on modifiedSince, and Help Scout caps calls at Per-account (shared across all tokens/apps on that account) tiered by plan: roughly 200 requests/minute on Standard, 400/minute on Plus, 800/minute on Pro; write requests (POST/PUT/PATCH/DELETE) count as 2 against the limit, reads count as 1.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `help_scout_conversations`) with a schema derived from the Help Scout API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Help Scout pipeline page, and join the waitlist to get the Help Scout connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Help Scout data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
conversations	help_scout_conversations	Upsert by primary key, incremental on updated-at
customers	help_scout_customers	Upsert by primary key, incremental on updated-at
mailboxes	help_scout_mailboxes	Upsert by primary key, incremental on updated-at
threads	help_scout_threads	Upsert by primary key, incremental on updated-at
tags	help_scout_tags	Upsert by primary key, incremental on updated-at
satisfaction ratings	help_scout_satisfaction_ratings	Upsert by primary key, incremental on updated-at

Help Scout API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Help Scout Mailbox API 2.0
Authentication	OAuth 2.0 — Server-to-server connectors use the OAuth 2.0 Client Credentials grant (app ID + app secret, no user redirect) while customer-facing apps use the Authorization Code grant; both issue bearer access tokens.
Pagination	page — List endpoints (e.g. `/v2/conversations`) return `page`/`pages`, `size`, `totalElements`, and `totalPages`, defaulting to 25 records per page with a maximum of 50.
Rate limit	Per-account (shared across all tokens/apps on that account) tiered by plan: roughly 200 requests/minute on Standard, 400/minute on Plus, 800/minute on Pro; write requests (POST/PUT/PATCH/DELETE) count as 2 against the limit, reads count as 1.
Incremental cursor	modifiedSince — List endpoints accept a `modifiedSince` query parameter (`YYYY-MM-DDTHH:MM:SSZ`) to pull only records changed after a given timestamp.
Webhooks	Yes — Help Scout webhooks (convo.created, convo.assigned, convo.deleted, convo.moved, customer.created, etc.)
Bulk export	No
Deletes detectable	Yes — Conversation `state` includes `deleted` alongside `draft`/`published`, and the `convo.deleted` webhook event fires on removal; spam-folder conversations auto-purge permanently 30 days after their last action.

Official API reference

What bites when replicating Help Scout

Access tokens expire after exactly 172,800 seconds (48 hours) and the API returns HTTP 401 on expiry with no advance warning header, so a connector must refresh proactively rather than reactively on a schedule longer than 2 days.
Write calls (POST/PUT/PATCH/DELETE) cost 2 units against the per-minute rate limit while reads cost 1, so a sync that both reads and writes needs separate budget accounting, not a single request counter.
Conversation `status` (active/closed/open/pending/spam) and conversation `state` (draft/published/deleted) are two different fields; filtering only on `status` will not surface deleted conversations.
Conversations that land in the Spam folder are permanently purged 30 days after their last action, so a connector polling on a `modifiedSince` cursor slower than that window can miss spam-classified conversations entirely.

Compare this against every other documented API

Popular destinations for Help Scout

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Help Scout connector FAQ

What Help Scout data does the connector extract?: 6 objects: conversations, customers, mailboxes, threads, tags and satisfaction ratings. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Help Scout integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Help Scout data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Help Scout → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Help Scout pipeline with guided onboarding

Join the waitlist to get priority access for Help Scout integrations with guided setup, schema-aware mapping, and production-grade incremental sync.