Linking None as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
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.
Contents
The None connector syncs constituents, transactions, interactions, 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 Bloomerang private API key to pull your donor database, including constituents, transactions, interactions, appeals, campaigns, and funds.
Generate a private API key under Settings → User Settings → API Keys in your Bloomerang account. This key grants full read/write access to your Bloomerang data, so keep it secret.
You'll be asked for:
- API key
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.
Some None tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Constituents | An individual, household, or organization tracked in the Bloomerang donor database. | Incremental, Full refresh | LastModifiedDate | — |
Transactions | A donation, pledge, pledge payment, or recurring donation payment recorded against a constituent. | Full refresh | — | — |
Interactions | A logged touchpoint with a constituent, such as an email, call, or in-person visit. | Full refresh | — | — |
Appeals | A fundraising appeal (a specific ask sent to donors) that transactions can be designated to. | Full refresh | — | — |
Campaigns | A fundraising campaign that groups appeals and transactions toward a shared goal. | Full refresh | — | — |
Funds | A designation fund (general ledger bucket) that transactions can be allocated to. | Full refresh | — | — |
Refunds | A refund issued against a transaction, used to compute net giving. | Incremental, Full refresh | LastModifiedDate | — |
SoftCredits | Giving credit attributed to a constituent other than the donor for a transaction designation. | Incremental, Full refresh | LastModifiedDate | — |
Households | A household that groups individual constituents so giving can be aggregated across members. | Full refresh | — | — |
Phones | A phone number on a constituent record, including non-primary numbers. | Full refresh | — | — |
Addresses | A mailing address on a constituent record, including non-primary addresses. | Full refresh | — | — |
Emails | An email address on a constituent record, including non-primary addresses. | Full refresh | — | — |
Notes | A free-form note recorded against a constituent. | Full refresh | — | — |
Tasks | A follow-up task assigned to a Bloomerang user for a constituent. | Full refresh | — | — |
Relationships | A link between two constituents, such as spouse, employer, or board member, listed once for each constituent on it. | Full refresh | — | — |
PledgePaymentFailures | A failed payment against a pledge installment. | 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.