Productivity · Integration
Tempo
Add Tempo to your product for your customers, and give your AI agents governed access to it.
Tempo is time and capacity for Jira, so its records hang off Jira's: a worklog belongs to a Jira issue, a plan allocates a person to work in a Jira project, and Tempo's own accounts and customers are what turn logged hours into something billable or capitalisable. That dependency is the defining fact, because an id from Tempo means little until it is resolved against the Jira site it came from, and the two are separate calls with separate credentials. Work attributes are the other per-customer piece: a company decides what extra fields a worklog carries, billable or not, which cost centre, which activity type, and those are configuration rather than a schema you can assume. fastn holds each site's Tempo token per tenant and keeps the mapping current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Jira site and Tempo token, so worklogs are written under their credentials.
Log time against a Jira issue from your product, with the work attributes that customer requires already filled in.
Read worklogs by account or team so your product can bill, capitalise or report on hours without a manual export.
Read plans and capacity so your product knows what a team is already committed to before it promises more.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports how many hours went to an account last month and which issues consumed them.
An agent logs or corrects a worklog within scoped permissions, with the attributes it set recorded.
An agent flags who has logged well under or well over their planned capacity this period.
Example prompt
How many billable hours were logged to this account last month, and which Jira issues did they go to?
Set up Tempo in 4 steps
- 01Enable the Tempo connector in your fastn dashboard.
- 02Have each customer connect their own Jira site and supply a Tempo API token, since the two are authorised separately.
- 03Map the worklog, account, team and work attribute fields that customer configured, and decide which are mandatory.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Tempo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Tempo integration without building it. Your customers connect their own Tempo 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 Tempo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Tempo 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
Jira
Teamwork
AsanaOften used alongside
Tools the same teams tend to run next to Tempo, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceTempo integration FAQ
How do I add a Tempo integration to my product?
Enable the Tempo connector in your fastn dashboard, then let each customer authenticate their own Tempo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Tempo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Tempo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Tempo 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 Tempo 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 how many hours went to an account last month and which issues consumed them.
Who maintains the Tempo integration?
fastn does. When Tempo 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 Tempo automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Tempo can trigger your workflows in return.
Does it adapt to each team's own Tempo setup?
Yes. However a team has configured Tempo, 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 Tempo integration?
A common starting point: let each customer connect their own Jira site and Tempo token, so worklogs are written under their credentials. 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 Tempo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Tempo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Tempo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.