Linking Flowlu as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Flowlu connector syncs accounts, leads, pipelines, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Flowlu API key and account subdomain to pull your CRM, project, task, and finance data.
You can create an API key under Portal Settings → API Settings in Flowlu. Your subdomain is the first part of your portal URL - for acme.flowlu.com the subdomain is acme.
You'll be asked for:
- API key
- Account subdomain: for example
acme.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Flowlu tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Account subdomain | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | A CRM account in Flowlu — an organization or contact you do business with. | Full refresh | — | — |
leads | A CRM opportunity (Flowlu's API keeps the legacy 'lead' entity name) tracked through a sales pipeline. | Full refresh | — | — |
pipelines | A CRM sales pipeline that opportunities move through. | Full refresh | — | — |
pipeline_stages | A stage of a CRM sales pipeline, resolving the stage an opportunity sits in. | Full refresh | — | — |
lead_sources | A source an opportunity came from, resolving | Full refresh | — | — |
loss_reasons | A reason an opportunity was lost, resolving | Full refresh | — | — |
tasks | A task in Flowlu's task management module. | Full refresh | — | — |
projects | A project in Flowlu's project management module. | Full refresh | — | — |
project_stages | A stage of a project workflow, resolving the stage a project sits in. | Full refresh | — | — |
invoices | An invoice issued to a customer in Flowlu's finance module. | Full refresh | — | — |
invoice_items | A line item on an invoice, giving revenue per product or service rather than per invoice total. | Full refresh | — | — |
estimates | An estimate (quote) prepared for a customer in Flowlu's finance module. | Full refresh | — | — |
customer_payments | A payment received from a customer, typically applied against an invoice. | Full refresh | — | — |
transactions | A money transaction (income or expense) recorded in Flowlu's finance module. | Full refresh | — | — |
billing_organizations | One of the account's own billing entities, resolving | Full refresh | — | — |
agile_issues | An issue (user story, task, or bug) on a Flowlu agile board. | Full refresh | — | — |
agile_sprints | A sprint within a Flowlu agile project. | Full refresh | — | — |
agile_stages | A stage of an agile workflow, resolving | Full refresh | — | — |
timesheets | A time-tracking entry logged against tasks or projects in Flowlu. | Full refresh | — | — |
timelogs | An individual time log entry behind a timesheet, with the hours, rates, and amounts recorded for one stretch of work. | Full refresh | — | — |
products | A product or service from Flowlu's product catalog. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.