Productivity · Integration
Simpro
Add Simpro to your product for your customers, and give your AI agents governed access to it.
Simpro runs the office side of a trade business, so a job in it carries the quote it came from, the site it happens at, the labour booked against it and the materials it consumed. An embedded Simpro integration creates and updates jobs and quotes, reads customers, sites and contacts, reads schedules and timesheet entries, works with cost centres and stock, and reads the invoices a job produces. Two characteristics decide how you build it. Simpro is configured heavily per business, from custom fields to how cost centres are structured, so the mapping belongs in configuration and not in your build. And a job's cost is assembled from many small entries recorded in the field, which means a read should follow the job rather than wait for a nightly total. fastn keeps each build's credentials per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Simpro build so work created in your product becomes a job with the right site and cost centre.
Turn an accepted quote into a job without anybody retyping the line items.
Read schedules and timesheet entries so your product reports on labour actually booked rather than labour planned.
Read stock and materials against a job so your product knows what a piece of work really consumed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which jobs are open at a site and which have passed their quoted value.
An agent creates or updates a job within scoped permissions, with the change attributed to the build that authorised it.
An agent explains a job's cost by reading the labour and materials booked to it.
Example prompt
Which open jobs have gone past their quoted value, and what is driving the overrun on each one?
Set up Simpro in 4 steps
- 01Enable the Simpro connector in your fastn dashboard.
- 02Have each customer authorise their own Simpro build so calls run under their credentials.
- 03Map the job, quote, site and cost centre fields that business uses, including its custom fields, then enable the actions you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Simpro integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Simpro integration without building it. Your customers connect their own Simpro 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 Simpro update is not your on-call problem.
- One integration serves your product and your agents. The same governed Simpro 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
ServiceM8Works well with
XeroOften used alongside
Tools the same teams tend to run next to Simpro, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceSimpro integration FAQ
How do I add a Simpro integration to my product?
Enable the Simpro connector in your fastn dashboard, then let each customer authenticate their own Simpro account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Simpro client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Simpro account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Simpro 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 Simpro 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 jobs are open at a site and which have passed their quoted value.
Who maintains the Simpro integration?
fastn does. When Simpro 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 Simpro automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Simpro can trigger your workflows in return.
Does it adapt to each team's own Simpro setup?
Yes. However a team has configured Simpro, 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 Simpro integration?
A common starting point: let each customer connect their own Simpro build so work created in your product becomes a job with the right site and cost centre. 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 Simpro integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Simpro does not change your per-connector cost. You can start free with 3 connected accounts.
Add Simpro to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.