Helpin
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Connect Helpin to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Sync your Helpin support conversations, CRM records, tasks, planning and docs into the PostHog Data warehouse.
In Helpin, a workspace manager creates an automation account under Settings > MCP access > Service accounts, then creates a token for it. The token starts with hmp_ and is shown once. Give the account read scopes for the tables you want:
helpin.support.read: support conversations, messages, inboxes and tagshelpin.crm.read: contacts, companies, deals and pipelineshelpin.pm.read: tasks, epics, sprints, objectives, labels and workflowshelpin.docs.read: documentshelpin.context.read: teams and members
The account can be read-only. Leave the API host blank for Helpin Cloud. For a self-hosted Helpin, enter your API host. It must use https.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
API host (optional) | text | No |
Linking Helpin to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Helpin
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
support_conversations | Support conversations in the Helpin inbox, from email, chat and other channels. Merged conversations and conversations that are snoozed at sync time are not listed. | Full refresh | — | — |
support_conversation_messages | Public messages in each support conversation, oldest first. Internal notes are not included. | Full refresh | — | — |
support_inboxes | Support inboxes: the shared inbox and each mailbox, with their conversation counts at sync time. At most 100 are listed. | Full refresh | — | — |
support_tags | Tags for support conversations. At most 100 are listed. | Full refresh | — | — |
crm_contacts | CRM contacts in the workspace, with their custom properties. | Full refresh | — | — |
crm_companies | CRM companies in the workspace, with their custom properties. | Incremental, Full refresh | updated_at | — |
crm_deals | CRM deals with their stage name and amount. | Full refresh | — | — |
crm_pipelines | CRM deal pipelines with their ordered stages. At most 100 are listed. | Full refresh | — | — |
tasks | Project tasks, including completed and archived tasks. | Incremental, Full refresh | updated_at | — |
epics | Epics with their state, owner, dates, health and progress counts. | Full refresh | — | — |
sprints | Sprints with their dates, status and progress counts. | Full refresh | — | — |
objectives | Objectives with their type, state, owners, linked epics and progress. | Full refresh | — | — |
labels | Workspace and team labels for tasks, epics and objectives. Archived labels are not listed. | Full refresh | — | — |
workflows | The workflow each team uses, with its ordered states. One row per team. | Full refresh | — | — |
teams | Teams in the workspace. | Full refresh | — | — |
members | Active workspace members with their role and teams. Email addresses are not included. | Full refresh | — | — |
documents | Docs documents with their status, space and collection, including archived documents. The document body is not included. | Full refresh | — | — |





