Productivity · Integration
Dispatch
Add Dispatch to your product for your customers, and give your AI agents governed access to it.
Embed a Dispatch integration so your customers can work their own jobs, appointments, and assignments from inside your product, with governed agent access to the same records. Every team configures its own statuses, fields, and workflow stages, so those are mapped per customer as configuration rather than code, and a team with an unusual setup does not need a release from you. fastn handles each customer's authentication and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own jobs and scheduled appointments into your product, mapped to their fields.
Create or update a job from an event in your product so nobody re-enters it by hand.
Read assignment and status changes so your product reflects the current state of the work.
Trigger your product when a job is created, assigned, rescheduled, or completed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a job's history and status before answering a customer question about it.
An agent creates or updates a job within governed permissions, with the action audited.
An agent reacts to a completed job and runs the next step of a workflow.
Example prompt
List jobs scheduled for tomorrow with no one assigned and show which ones have already been rescheduled once.
Set up Dispatch in 4 steps
- 01Open the Dispatch connector from your fastn dashboard.
- 02Have each customer authenticate their own Dispatch account.
- 03Map the job, status, and assignment fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Dispatch integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dispatch integration without building it. Your customers connect their own Dispatch 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 Dispatch update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dispatch 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
ClickUpWorks well with
Salesforce
SlackOften used alongside
Tools the same teams tend to run next to Dispatch, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceDispatch integration FAQ
How do I add a Dispatch integration to my product?
Enable the Dispatch connector in your fastn dashboard, then let each customer authenticate their own Dispatch account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dispatch client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dispatch account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dispatch 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 Dispatch 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 reads a job's history and status before answering a customer question about it.
Who maintains the Dispatch integration?
fastn does. When Dispatch 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 Dispatch automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Dispatch can trigger your workflows in return.
Does it adapt to each team's own Dispatch setup?
Yes. However a team has configured Dispatch, 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 Dispatch integration?
A common starting point: read their own jobs and scheduled appointments into your product, mapped to their fields. 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 Dispatch integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dispatch does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dispatch to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.