Skip to content

Boomi AgentStudio usage

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

Onboarding scope

This guide covers the read-only boomi connector in the Venturi platform connector package. It reads agent activity, token usage, and audit context and never deploys, edits, or administers Boomi resources.

Required access

The names below are Venturi capability identifiers, not Boomi API permissions:

Venturi capability 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 privileges.

The vendor-side authorization is a Boomi Platform API token. A token belongs to the Boomi user who generated it and authenticates as that user (BOOMI_TOKEN.<username>). Generate it as a dedicated Venturi user whose role grants the API Access privilege, which Boomi requires for Platform API tokens, and view-only access to AgentStudio, Agent Control Tower, and audit data, with no deployment or edit rights. The connector exchanges the token for the JSON Web Token that the Agent Control Tower GraphQL API requires; Boomi expires each JSON Web Token after 5 minutes. See Boomi’s Platform API tokens overview, Platform API authentication, and Agent Control Tower GraphQL APIs.

Setup

  1. Create a dedicated Boomi user for Venturi with the view-only role above.
  2. Sign in as that user and generate a Platform API token.
  3. Store the token as an encrypted credential reference in Settings / Admin / Credentials.
  4. The default lookback is 30 days; set VENTURI_BOOMI_LOOKBACK_DAYS to change it. See sync windows and failure behavior.
  5. In Venturi, go to Integrations / Boomi and run Test connection.

Verification

  • Test connection passes the read-only boundary check: agent, workspace, and audit reads succeed, and the token’s user holds no deploy or edit privilege.
  • The first sync shows AgentStudio or Agent 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 Platform API token through Boomi administration, then update the credential reference in Settings / Admin / Credentials. Removing the connector stops new Boomi agent usage syncs.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Boomi AgentStudio usage
Page: https://docs.venturi.systems/connectors/boomi/