Workflow & Automation · Integration
Process Street
Add Process Street to your product for your customers, and give your AI agents governed access to it.
Embed a Process Street integration so your customers can run their own procedures from inside your product instead of remembering to start them by hand. Process Street models a procedure as a workflow, and each time it is used it becomes a workflow run with tasks to complete, form fields to fill and approvals to clear. Every team builds its own workflows and fields, so mapping is configuration per customer rather than code. fastn handles per-customer authorisation, token refresh, rate limits and API upkeep, so supporting another customer's workflows does not mean a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Process Street account so an event in your product starts the right workflow run.
Pass data from your product into a run's form fields so nobody re-enters what you already know.
Read task and approval state so your product shows how far a procedure has progressed.
Trigger your workflow when a run is completed or a task is checked off, rather than polling for it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent starts a workflow run with the right data within governed permissions.
An agent reads the open tasks in a run before reporting what is outstanding.
An agent completes a task or fills a form field, with every action attributed and audited.
Example prompt
List workflow runs with tasks overdue by more than three days and show who owns each.
Set up Process Street in 4 steps
- 01Open the Process Street connector from your fastn dashboard.
- 02Have each customer authorise their own Process Street account.
- 03Map the workflows, tasks and form 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 Process Street integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Process Street integration without building it. Your customers connect their own Process Street 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 Process Street update is not your on-call problem.
- One integration serves your product and your agents. The same governed Process Street 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
monday.com
Asana
PipefyOften used alongside
Tools the same teams tend to run next to Process Street, across other categories.
Amazon SES
Resend
Mailgun
PostmarkProcess Street integration FAQ
How do I add a Process Street integration to my product?
Enable the Process Street connector in your fastn dashboard, then let each customer authenticate their own Process Street account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Process Street client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Process Street account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Process Street 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 Process Street 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 starts a workflow run with the right data within governed permissions.
Who maintains the Process Street integration?
fastn does. When Process Street 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 Process Street run and read its outcome?
Yes. Your product can trigger a process in the customer's own Process Street account, pass it input, and take the result back as an event rather than polling for it.
What happens when a Process Street 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 Process Street integration?
A common starting point: connect their own Process Street account so an event in your product starts the right workflow run. 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 Process Street integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Process Street does not change your per-connector cost. You can start free with 3 connected accounts.
Add Process Street to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.