For AI service providers · Capability
How do providers connect client tools to AI agents?
Use the client’s authorized account and verify which agent receives access. Agentic Workers app-connection invitations are scoped to one Super Agent in Agent only mode. The client completes the supported authorization through Composio. Confirm a live read before enabling writes, and revoke invitations separately from disconnecting accounts.
By Agentic Workers Team · Published · Updated
Authorize the intended account
Choose the needed app in the customer portal’s App connections view. Supported authorization may use OAuth, an API key or provider-specific fields. Do not ask the client to paste account passwords into an agent chat. The account owner should review the provider’s consent screen.
Test the permission boundary
The selected agent uses its private connected account. Confirm the client identity with a small read-only request. A connection marked active may still lack permission for a specific resource, so inspect the actual result before allowing changes.
Disconnect and revoke
There is one client account per app per agent in this flow. Disconnecting an app and revoking an invitation are different actions. An active invitation can reconnect an app after disconnection; an authorization already open with the provider can outlive invitation revocation.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Request
Provider selects the required apps and an expiry for the invitation.
- 02
Authorize
Client chooses the right account and grants the required permissions.
- 03
Test
Provider verifies a harmless read, then checks supported write approvals.
Fit and limitations
- Good fit
- Providers connecting client-owned tools to a clearly scoped agent.
- Poor fit
- Sharing one account across unrelated clients or promising controls the source provider does not expose.
- Known limits
- Provider scopes and app availability differ. The portal does not supply a universal security certification, password vault or automatic end-to-end offboarding.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Customer portal operating notesProduct documentation | Upload and app-connection invitations are scoped to a selected agent. Revoking an invitation is separate from disconnecting an account. | |
| Connect tools to a Super AgentProduct documentation | Authorization requirements depend on the provider. Verify the actual account and resource access with a read-only request. |
Questions providers ask
What should we test before using client data?
Provider selects the required apps and an expiry for the invitation. Client chooses the right account and grants the required permissions.
What should the provider verify after a run?
Provider verifies a harmless read, then checks supported write approvals.
What is the main limitation?
Provider scopes and app availability differ. The portal does not supply a universal security certification, password vault or automatic end-to-end offboarding.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now