Productivity · Integration
Rhumbix
Add Rhumbix to your product for your customers, and give your AI agents governed access to it.
Rhumbix collects construction field data at the source: a foreman records hours against a cost code, quantities installed, delays and safety observations on a phone, and that becomes the timecard and daily report the office works from the next morning. Cost codes are the join that makes any of it useful, because labour hours mean nothing to a project manager until they sit against the right code and phase, and every contractor's coding structure is its own. Approval matters as much as capture: a timecard that has not been approved should not reach payroll, so state has to be read rather than assumed. Rhumbix is now part of Autodesk, which puts field labour next to the rest of the project record. fastn owns the credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each contractor connect their own Rhumbix account so field hours reach your product already coded to their cost codes and phases.
Read quantities installed alongside hours, because productivity is the ratio and neither number says much alone.
Respect timecard approval state, so unapproved field time never reaches a payroll or billing step in your product.
Read daily reports and delay records per project, so your product can show why a day went the way it did.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which cost codes are running over on labour and by how much.
An agent summarises yesterday's daily reports for a project, citing the entries it read.
An agent flags timecards still unapproved with a payroll cutoff approaching.
Example prompt
Which cost codes on this project are over on labour hours against quantities installed?
Set up Rhumbix in 4 steps
- 01Enable the Rhumbix connector in your fastn dashboard.
- 02Have each contractor authorise their own Rhumbix account so field data is read under their credentials.
- 03Map their projects, cost codes and phases, and decide how your product treats an unapproved timecard.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Rhumbix integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Rhumbix integration without building it. Your customers connect their own Rhumbix 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 Rhumbix update is not your on-call problem.
- One integration serves your product and your agents. The same governed Rhumbix 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
Procore
HarvestWorks well with
PlanGridOften used alongside
Tools the same teams tend to run next to Rhumbix, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceRhumbix integration FAQ
How do I add a Rhumbix integration to my product?
Enable the Rhumbix connector in your fastn dashboard, then let each customer authenticate their own Rhumbix account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Rhumbix client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Rhumbix account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Rhumbix 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 Rhumbix 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 cost codes are running over on labour and by how much.
Who maintains the Rhumbix integration?
fastn does. When Rhumbix 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 Rhumbix automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Rhumbix can trigger your workflows in return.
Does it adapt to each team's own Rhumbix setup?
Yes. However a team has configured Rhumbix, 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 Rhumbix integration?
A common starting point: let each contractor connect their own Rhumbix account so field hours reach your product already coded to their cost codes and phases. 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 Rhumbix integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Rhumbix does not change your per-connector cost. You can start free with 3 connected accounts.
Add Rhumbix to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.