Productivity · Integration
Shortcut
Add Shortcut to your product for your customers, and give your AI agents governed access to it.
Shortcut models engineering work as stories grouped into epics and scheduled into iterations, and unlike a general task tool those three levels are genuinely distinct rather than nested folders. A story carries workflow state, an owner and an estimate; an epic is the thing a stakeholder actually asks about; an iteration is the time box. An integration that only reads stories will be able to list work but not answer the question anyone senior is asking, which is whether the epic will land. Workflow states are configured per workspace, so a status is not a fixed enum and mapping it is configuration rather than code. fastn scopes each customer's token and keeps that mapping out of your codebase.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Shortcut workspace so engineering work appears next to the workflow your product owns.
Read stories with their epic and iteration, which is what makes a progress view meaningful.
Create or update a story from your product, with workflow states mapped per customer.
React when a story changes state, rather than polling a busy workspace.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises which stories in an epic are still open and who owns them.
An agent files a story within governed permissions, with the write audited per tenant.
An agent reacts to a story moving to done and updates the record your product holds.
Example prompt
Which stories in this epic are still open, and are any of them unowned?
Set up Shortcut in 4 steps
- 01Enable the Shortcut connector from your fastn dashboard.
- 02Have each customer authorise their own Shortcut account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Shortcut integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Shortcut integration without building it. Your customers connect their own Shortcut 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 Shortcut update is not your on-call problem.
- One integration serves your product and your agents. The same governed Shortcut 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
Linear
Jira
AsanaOften used alongside
Tools the same teams tend to run next to Shortcut, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceShortcut integration FAQ
How do I add a Shortcut integration to my product?
Enable the Shortcut connector in your fastn dashboard, then let each customer authenticate their own Shortcut account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Shortcut client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Shortcut account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Shortcut 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 Shortcut 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 summarises which stories in an epic are still open and who owns them.
Who maintains the Shortcut integration?
fastn does. When Shortcut 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 Shortcut automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Shortcut can trigger your workflows in return.
Does it adapt to each team's own Shortcut setup?
Yes. However a team has configured Shortcut, 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 Shortcut integration?
A common starting point: let a customer connect their own Shortcut workspace so engineering work appears next to the workflow your product owns. 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 Shortcut integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Shortcut does not change your per-connector cost. You can start free with 3 connected accounts.
Add Shortcut to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.