Content & Documents · Integration
PlanGrid
Add PlanGrid to your product for your customers, and give your AI agents governed access to it.
Embed a PlanGrid integration so your product can work with the drawings and field records a construction team already keeps rather than asking them to upload copies. PlanGrid, now part of Autodesk Construction Cloud, is built around project sheets and their versions, with RFIs, issues and punch items, field reports and photos filed against them. Sheet versions and project permissions are exactly the things that are easy to get subtly wrong, so access runs through each customer's own grant and your product cannot read what the connected account could not read itself. fastn handles per-customer authorisation, pagination and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own PlanGrid projects so your product reads the current sheet set instead of a stale PDF.
Read RFIs, issues and punch items per project so your product shows what the field is waiting on.
Write a field record or attach a photo from your product so evidence lands in the project everyone else is looking at.
Respect each project's own permissions and sheet versioning rather than flattening them in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the current version of a sheet within scoped permissions, with every read audited.
An agent opens an issue or RFI with the right project and detail, with the write attributed to the tenant that authorised it.
An agent reports which punch items are still open on a project before a walkthrough.
Example prompt
List open RFIs on this project and show which sheets they reference.
Set up PlanGrid in 4 steps
- 01Open the PlanGrid connector from your fastn dashboard.
- 02Have each customer authorise their own PlanGrid account and select projects.
- 03Map the sheets, RFIs, issues and photo 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 PlanGrid integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PlanGrid integration without building it. Your customers connect their own PlanGrid account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a PlanGrid update is not your on-call problem.
- One integration serves your product and your agents. The same governed PlanGrid connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Autodesk BIM 360
BluebeamWorks well with
ProcoreOften used alongside
Tools the same teams tend to run next to PlanGrid, across other categories.
Shopify
Stripe
Jira
AsanaPlanGrid integration FAQ
How do I add a PlanGrid integration to my product?
Enable the PlanGrid connector in your fastn dashboard, then let each customer authenticate their own PlanGrid account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PlanGrid client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PlanGrid account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PlanGrid account and only ever sees their own files, documents and versions. 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 PlanGrid 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 finds the current version of a sheet within scoped permissions, with every read audited.
Who maintains the PlanGrid integration?
fastn does. When PlanGrid 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.
Whose permissions does the PlanGrid integration run under?
Each customer's own PlanGrid grant. Where PlanGrid holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in PlanGrid automatically?
Where PlanGrid supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the PlanGrid integration?
A common starting point: connect their own PlanGrid projects so your product reads the current sheet set instead of a stale PDF. 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 PlanGrid integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PlanGrid does not change your per-connector cost. You can start free with 3 connected accounts.
Add PlanGrid to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.