Content & Documents · Integration
SketchUp
Add SketchUp to your product for your customers, and give your AI agents governed access to it.
SketchUp models are files, and for an integration that is the honest place to start: a model and the exports taken from it sit in the project storage a customer already uses, alongside the drawings and documents around them. An embedded SketchUp integration reads those model files and their metadata, files exports and generated documents back into the right project folder, and reads version history so your product can say which iteration somebody is looking at. Permissions come from the customer's own storage grant, so your product cannot open a project it was not given. This is deliberately file level: the modelling itself happens in the application, and what a product integrates with is the content that comes out of it. fastn holds the per-tenant credentials and keeps every read and write audited.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SketchUp project storage so your product reaches their models without a manual upload.
Read a model file and its metadata so your product can record what a design contained at a point in time.
File exports and generated documents back into the project folder that customer's team already works in.
Read version history so your product shows which iteration of a model a decision was based on.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the current model for a project and reports when it last changed and who changed it.
An agent files a generated export into the folder a customer nominates, within scoped permissions.
An agent lists projects whose models have not been touched since a milestone.
Example prompt
Find the latest model for this project and tell me when it last changed and what was filed alongside it.
Set up SketchUp in 4 steps
- 01Enable the SketchUp connector in your fastn dashboard.
- 02Have each customer authorise the project storage their models live in, so existing permissions carry over.
- 03Agree which project folders your product may read and write, and map the file metadata you use.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SketchUp integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SketchUp integration without building it. Your customers connect their own SketchUp 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 SketchUp update is not your on-call problem.
- One integration serves your product and your agents. The same governed SketchUp 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
Often used alongside
Tools the same teams tend to run next to SketchUp, across other categories.
SketchUp integration FAQ
How do I add a SketchUp integration to my product?
Enable the SketchUp connector in your fastn dashboard, then let each customer authenticate their own SketchUp account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SketchUp client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SketchUp account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SketchUp 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 SketchUp 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 model for a project and reports when it last changed and who changed it.
Who maintains the SketchUp integration?
fastn does. When SketchUp 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 SketchUp integration run under?
Each customer's own SketchUp grant. Where SketchUp 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 SketchUp automatically?
Where SketchUp 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 SketchUp integration?
A common starting point: let each customer connect their own SketchUp project storage so your product reaches their models without a manual upload. 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 SketchUp integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SketchUp does not change your per-connector cost. You can start free with 3 connected accounts.
Add SketchUp to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.