CloudBot

Enable the CloudBot connector in your fastn dashboard, then let each customer authenticate their own CloudBot account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CloudBot client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own CloudBot 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.

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 triggers an automation within governed permissions.

fastn does. When CloudBot 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.

Yes. Your product can trigger a process in the customer's own CloudBot account, pass it input, and take the result back as an event rather than polling for it.

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.

A common starting point: trigger their own automations 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.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CloudBot does not change your per-connector cost. You can start free with 3 connected accounts.