Embed a QueBIT ReportWORQ integration in your product

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

Yes. Every integration is scoped to the individual customer, so each authorises their own QueBIT ReportWORQ account and only ever sees their own files, documents and versions. 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 integration is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent starts a report run on request and reports which outputs it produced. A prompt that works on day one: "Has this month's reporting pack been generated yet, and which recipients did it go out to?"

fastn does. When QueBIT ReportWORQ changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' integrations keep working.

Each customer's own QueBIT ReportWORQ grant. Where QueBIT ReportWORQ holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.

Where QueBIT ReportWORQ supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.

A common starting point: let each customer connect their own ReportWORQ environment so your product can start a report run instead of asking somebody to open Excel. 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 customer connections, not on how many connectors you enable, so adding QueBIT ReportWORQ does not change your cost. You can start free with 3 customer connections.