Productivity · Integration
BuildingConnected
Add BuildingConnected to your product for your customers, and give your AI agents governed access to it.
Embed a BuildingConnected integration so your customers can manage their own bid invitations, projects, and subcontractor network from inside your product, with governed agent access to the same records. Bid responses arrive at unpredictable times and in inconsistent detail, so events are delivered per tenant and normalised for your product to act on. fastn handles each customer's auth and API upkeep, so onboarding another contractor is configuration rather than a deploy.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own BuildingConnected account and read projects and bid packages into your product.
Send and track bid invitations to subcontractors so preconstruction runs inside your product.
Read subcontractor and vendor records, including their trades and coverage, for qualification workflows.
Trigger your product when a bid is submitted, declined, or a due date approaches.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads outstanding bid invitations and flags packages with too few responses.
An agent sends a reminder to non-responding subcontractors within governed permissions.
An agent reacts to a submitted bid and starts the levelling or review workflow.
Example prompt
List bid packages due this week with fewer than three responses and show who has not replied.
Set up BuildingConnected in 4 steps
- 01Open the BuildingConnected connector from your fastn dashboard.
- 02Have each customer authenticate their own BuildingConnected account with least-privilege scopes.
- 03Map the project, bid, and subcontractor fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the BuildingConnected integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BuildingConnected integration without building it. Your customers connect their own BuildingConnected account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a BuildingConnected update is not your on-call problem.
- One integration serves your product and your agents. The same governed BuildingConnected connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
BuildxactWorks well with
Autodesk BIM 360
BluebeamOften used alongside
Tools the same teams tend to run next to BuildingConnected, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceBuildingConnected integration FAQ
How do I add a BuildingConnected integration to my product?
Enable the BuildingConnected connector in your fastn dashboard, then let each customer authenticate their own BuildingConnected account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BuildingConnected client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BuildingConnected account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BuildingConnected account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this BuildingConnected integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads outstanding bid invitations and flags packages with too few responses.
Who maintains the BuildingConnected integration?
fastn does. When BuildingConnected changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in BuildingConnected automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in BuildingConnected can trigger your workflows in return.
Does it adapt to each team's own BuildingConnected setup?
Yes. However a team has configured BuildingConnected, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the BuildingConnected integration?
A common starting point: connect their own BuildingConnected account and read projects and bid packages into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the BuildingConnected integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BuildingConnected does not change your per-connector cost. You can start free with 3 connected accounts.
Add BuildingConnected to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.