Help Scout#
Connect Help Scout with OAuth using your Help Scout app credentials. The source writes 6 fixed tables under titan.helpscout.
select
id,
first_name,
last_name
from titan.helpscout.customers
limit 10Connect Help Scout#
Open Apps, choose Connect app, and select Help Scout.
Enter OAuth using your Help Scout app credentials.
Review the tables, then save the source.
Watch Sync history until the first run completes.
Credentials are stored as secrets. They never become lake columns or appear in query results.
Sync behavior#
Customers, conversations, mailboxes, users, tags, and workflows share one source schedule.
A new source syncs when you connect it and then follows its schedule. The default recurring interval is 4 hours. An interrupted run keeps its completed progress and retries safely.
Every lake table also has the system columns _synced_at and _deleted; the column reference below lists source columns only.
Table reference#
customers#
titan.helpscout.customers has 7 source columns.
Source field id.
Source field firstName.
Source field lastName.
Source field email.
Source field company.
Source field createdAt.
Source field updatedAt.
conversations#
titan.helpscout.conversations has 10 source columns.
Source field id.
Source field number.
Source field subject.
Source field status.
Source field type.
Source field mailboxId.
Source field createdAt.
Source field updatedAt.
Source field closedAt.
Source field assignee.
mailboxes#
titan.helpscout.mailboxes has 5 source columns.
Source field id.
Source field name.
Source field email.
Source field createdAt.
Source field updatedAt.
users#
titan.helpscout.users has 7 source columns.
Source field id.
Source field firstName.
Source field lastName.
Source field email.
Source field role.
Source field createdAt.
Source field updatedAt.
tags#
titan.helpscout.tags has 3 source columns.
workflows#
titan.helpscout.workflows has 6 source columns.
Source field id.
Source field name.
Source field type.
Source field status.
Source field createdAt.
Source field modifiedAt.
Deletes and history#
Rows are merged by their source key. When the source can prove that a row was deleted, Supernova keeps the row and sets _deleted so queries can choose whether to include history. Filter current-state queries with where not _deleted.