Workflow & Automation · Integration
Datamatics TruBot
Add Datamatics TruBot to your product for your customers, and give your AI agents governed access to it.
TruBot is Datamatics' robotic process automation platform, and its parts divide cleanly: processes are built in Designer, published and scheduled from Cockpit, executed by bots running on Stations, and reported on in Analytics. An embedded TruBot integration works against the control side rather than the desktop, starting a published process with the inputs your product supplies, feeding items into the work a bot picks up, and reading whether a run succeeded, failed or is still going. What makes automation different from an ordinary API call is that a bot is driving somebody else's application on the other side, so a run is slow, it can fail for reasons that have nothing to do with your request, and it must be treated as asynchronous work with an outcome to collect rather than a call to wait on. Deployments are on premise as well as cloud, so the endpoint is per customer. fastn holds the credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own TruBot environment so your product can hand work to the bots they already run.
Start a published process with inputs from your product, then collect the outcome rather than blocking on the run.
Feed items into the queue a bot works through, so volume from your product is processed at whatever rate their capacity allows.
Read run history and failures so a bot that broke because a target application changed surfaces in your product rather than in a log nobody opens.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which runs failed overnight and what each was attempting when it stopped.
An agent starts an approved process within governed permissions, with the inputs it supplied recorded.
An agent explains whether a queued item has been picked up yet and how far behind the queue is running.
Example prompt
Which automated runs failed since yesterday, and how many items are still waiting in the queue?
Set up Datamatics TruBot in 4 steps
- 01Enable the Datamatics TruBot connector in your fastn dashboard.
- 02Have each customer supply credentials and the endpoint for their own environment, since deployments are on premise as well as cloud.
- 03Map the processes and inputs your product uses, then decide how run outcomes are collected and what a failure should mean.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Datamatics TruBot integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Datamatics TruBot integration without building it. Your customers connect their own Datamatics TruBot 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 Datamatics TruBot update is not your on-call problem.
- One integration serves your product and your agents. The same governed Datamatics TruBot 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
Compare with
UiPath
Microsoft Power Automate
KissflowOften used alongside
Tools the same teams tend to run next to Datamatics TruBot, across other categories.
Amazon SES
Resend
Mailgun
PostmarkDatamatics TruBot integration FAQ
How do I add a Datamatics TruBot integration to my product?
Enable the Datamatics TruBot connector in your fastn dashboard, then let each customer authenticate their own Datamatics TruBot account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Datamatics TruBot client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Datamatics TruBot account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Datamatics TruBot 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 Datamatics TruBot 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 which runs failed overnight and what each was attempting when it stopped.
Who maintains the Datamatics TruBot integration?
fastn does. When Datamatics TruBot 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 Datamatics TruBot run and read its outcome?
Yes. Your product can trigger a process in the customer's own Datamatics TruBot account, pass it input, and take the result back as an event rather than polling for it.
What happens when a Datamatics TruBot 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 Datamatics TruBot integration?
A common starting point: let each customer connect their own TruBot environment so your product can hand work to the bots they already 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 Datamatics TruBot integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Datamatics TruBot does not change your per-connector cost. You can start free with 3 connected accounts.
Add Datamatics TruBot to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.