Productivity · Integration
UpKeep
Add UpKeep to your product for your customers, and give your AI agents governed access to it.
UpKeep is maintenance management for people who are rarely at a desk, so its records describe physical things: an asset at a location, the work order raised against it, the parts consumed doing the job, the meter readings that decide when preventive work is due, and the requests that arrive from whoever noticed the problem. An embedded UpKeep integration raises work orders from conditions your product already detects, reads asset and location detail so a technician is sent to the right piece of equipment rather than the right record, writes meter readings so preventive schedules advance on real usage instead of the calendar, and reacts when work is completed. The distinction that matters is between a request and a work order, since one is somebody asking and the other is work that has been accepted, and collapsing them makes a maintenance backlog look like a queue of decisions nobody made.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own UpKeep account so maintenance your product identifies becomes real scheduled work.
Raise a work order against the asset and location it concerns, so the technician is sent to the equipment rather than a description of it.
Write meter readings from your product so preventive maintenance is triggered by usage rather than by a date on a calendar.
React when work is completed or parts are consumed, so cost and availability in your product follow what really happened.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which work orders are overdue and which assets they concern.
An agent raises a work order within scoped permissions, with the asset and requester recorded.
An agent explains which assets consume the most parts and how often they come back for repair.
Example prompt
Which assets have had repeat work orders this quarter, and what parts keep getting replaced?
Set up UpKeep in 4 steps
- 01Enable the UpKeep connector in your fastn dashboard.
- 02Have each customer authorise their own UpKeep account so work orders are raised under their credentials.
- 03Map the asset, location, part and meter fields your product uses, and decide how a request becomes an accepted work order.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the UpKeep integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an UpKeep integration without building it. Your customers connect their own UpKeep 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 an UpKeep update is not your on-call problem.
- One integration serves your product and your agents. The same governed UpKeep 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
eMaint X5
SimproOften used alongside
Tools the same teams tend to run next to UpKeep, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceUpKeep integration FAQ
How do I add an UpKeep integration to my product?
Enable the UpKeep connector in your fastn dashboard, then let each customer authenticate their own UpKeep account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no UpKeep client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own UpKeep account?
Yes. Every connection is scoped to the individual customer, so each authorises their own UpKeep 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 UpKeep 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 reports which work orders are overdue and which assets they concern.
Who maintains the UpKeep integration?
fastn does. When UpKeep 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 UpKeep automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in UpKeep can trigger your workflows in return.
Does it adapt to each team's own UpKeep setup?
Yes. However a team has configured UpKeep, 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 UpKeep integration?
A common starting point: let each customer connect their own UpKeep account so maintenance your product identifies becomes real scheduled work. 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 UpKeep integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding UpKeep does not change your per-connector cost. You can start free with 3 connected accounts.
Add UpKeep to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.