Integrations: what's possible today
An honest map of how BuildFlow connects to other systems right now, what is not built yet, and which route to take for your case.
Updated 2 September 2026
Read this bit first
BuildFlow does not yet have a first-party integrations product: no API key management screen, no OAuth app, no webhook configuration, no marketplace connectors. What it does have is a real, queryable Postgres database with proper access rules on it — and that is enough to build most of what people ask for. This page is about being clear which is which.
What people usually want
| Want | Possible today? | How |
|---|---|---|
| Push a won deal from the CRM into a new BuildFlow project | Yes | Write to the database from your own script or automation platform |
| Pull project status back into the CRM record | Yes | Read from the database on a schedule |
| Get a Slack or Teams message when a snag is raised | Yes, with a poll | Poll for new rows; true push needs a webhook we have not built |
| Fire a webhook the instant something changes | Not built | Postgres can do it; we have not exposed configuration for it |
| Sync certificates and dates into accounting or compliance software | Yes | Read on a schedule |
| One-click connector in an app marketplace | Not built | — |
| Bulk export a project | Partly | Handover pack PDF today; a full data export on request |
The three routes
1. Direct database access
BuildFlow runs on Supabase, which exposes your Postgres database over HTTP as a REST API with your Row Level Security rules applied. Anything the app can do, a script of yours can do — and it is subject to exactly the same access rules.
This is the route for anything real: a nightly sync, a CRM hook, a dashboard of your own.
2. An automation platform
Zapier, Make and n8n can all call an HTTP endpoint, so they can all talk to BuildFlow — you are using their generic HTTP step rather than a BuildFlow connector. It is more setup than clicking a logo and considerably less than writing a service.
3. Export
The handover pack PDF covers a finished project: timeline, milestones, certificates, inspections, final snag list, spec book and completed photos. Documents and photos download as the files you uploaded. For a structured export of a whole account, ask us.
Choosing a route
- One-off migration in, or a one-off pull out — a script against the REST API, run once.
- Keep two systems roughly in step — a scheduled job every 15 minutes to an hour. This covers almost every CRM case; construction jobs do not move by the second.
- React within seconds — not properly supported yet. Poll at a minute if you must, and tell us what you are building, because that is the case that would justify webhooks.
The limits are still the limits
Plan limits are enforced in the database on insert, not in the interface. An integration that tries to create a twenty-first active project on Pro is refused exactly as the app would be. Handle the error rather than assuming a write succeeded.
What we would build next
In rough order of how often people ask:
- 1.Outgoing webhooks — pick events, give a URL, get a signed POST. Removes the polling from every recipe on these pages.
- 2.Scoped API keys — a key per integration, revocable, with an audit trail, instead of borrowing a session or a service key.
- 3.A CRM connector or two — likely HubSpot and Pipedrive first, since they are what small builders actually run.
- 4.Calendar feeds — an iCal URL per project so milestones and inspections appear in Outlook or Google Calendar.
- 5.Structured export — a JSON or CSV bundle of a project or an account, on demand.
If one of these is the difference between BuildFlow working for you and not, say so — it moves the order.