Workflow & Automation · Integration
K2 Workflow
Add K2 Workflow to your product for your customers, and give your AI agents governed access to it.
Embed a K2 Workflow integration so your customers can start and progress their own business processes from inside your product. Every team builds its own workflows, forms, and stages, so those are mapped per customer as configuration rather than code and an unusual process needs no release from you. fastn handles per-customer authentication and API upkeep, and logs each action per tenant so a task transition is attributable.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers start one of their own workflows from an event in your product.
Read the tasks assigned to a user so pending work appears inside your product.
Complete or reassign a task from your product so approvals do not require a second tool.
Read workflow status and history so users can see where a request has reached.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a user's outstanding tasks and summarises what is waiting on them.
An agent starts a workflow or completes a task within governed permissions, with each action logged.
An agent reacts to a workflow reaching a stage and gathers the context the approver needs.
Example prompt
List tasks assigned to this user that have been open more than five days and show which workflow each belongs to.
Set up K2 Workflow in 4 steps
- 01Open the K2 Workflow connector from your fastn dashboard.
- 02Have each customer authenticate their own K2 environment.
- 03Map their workflows, forms, and task fields, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the K2 Workflow integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a K2 Workflow integration without building it. Your customers connect their own K2 Workflow account inside your product and work their processes, runs and queues there, with no per-customer code on your side.
- Handle the part that actually costs time: runs are asynchronous and can fail long after they are accepted, so an outcome that never arrives must look different from one that succeeded. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a K2 Workflow update is not your on-call problem.
- One integration serves your product and your agents. The same governed K2 Workflow connection powers in-product features and gives AI agents scoped, audited access, so you start work in the automation platform your customers already run, and get the outcome back without wiring it twice.
Used by these teams
Works well with
ClickUp
JiraOften used alongside
Tools the same teams tend to run next to K2 Workflow, across other categories.
Amazon SES
Resend
Mailgun
PostmarkK2 Workflow integration FAQ
How do I add a K2 Workflow integration to my product?
Enable the K2 Workflow connector in your fastn dashboard, then let each customer authenticate their own K2 Workflow account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no K2 Workflow client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own K2 Workflow account?
Yes. Every connection is scoped to the individual customer, so each authorises their own K2 Workflow account and only ever sees their own processes, runs and queues. 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 K2 Workflow 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 user's outstanding tasks and summarises what is waiting on them.
Who maintains the K2 Workflow integration?
fastn does. When K2 Workflow 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 start a K2 Workflow run and read its outcome?
Yes. Your product can trigger a process in the customer's own K2 Workflow account, pass it input, and take the result back as an event rather than polling for it.
What happens when a K2 Workflow run is slow or fails?
The failure surfaces with its error rather than as a silent timeout, and the run keeps its own identifier so a retry can be matched to the original. That matters more here than in most integrations, because a run that half-completed is not the same as one that never started.
What can I build with the K2 Workflow integration?
A common starting point: start one of their own workflows from an event in your product. 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 K2 Workflow integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding K2 Workflow does not change your per-connector cost. You can start free with 3 connected accounts.
Add K2 Workflow to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.