Boomi AgentStudio usage

Boomi supplies AgentStudio and Control Tower usage context so Venturi can map agent activity to workspace and owner metadata.

Release state

This guide documents the read-only boomi connector implemented in the platform connector surface.

Required access

Grant a dedicated integration these read-only scopes:

Scope	Purpose
Boomi.AgentStudio.Read	Read agent activity and token usage rows.
Boomi.ControlTower.Read	Read workspace and control-plane context.
Boomi.Audit.Read	Read audit context for ownership and activity timing.

Do not grant deploy, edit, or administration scopes.

Setup

1. Create a dedicated Boomi integration identity for Venturi.
2. Limit it to the read-only scopes above.
3. Store the token reference in the tenant secrets flow.
4. Set ARGMIN_BOOMI_LOOKBACK_DAYS if you need a poll window other than 30 days.
5. In Venturi, open Administration -> Connectors -> Boomi and run Test connection.

Verification

• The first sync shows AgentStudio or Control Tower rows for the expected workspaces.
• Token fields are mapped as input, output, and total token counts when Boomi exposes them.
• The connector output identifies Boomi as the source and remains read-only.

Rotation and offboarding

Rotate the integration token through Boomi administration. Removing the connector stops new Boomi agent usage syncs.