Skip to main content
Feedback

Boomi Integration (Early Access) MCP connector

Updated 

Boomi Integration (Early Access) is Boomi's integration platform for building and running data and application workflows across your tenant. The Boomi Integration MCP connector allows AI agents to trigger deployed processes and monitor their execution status. It also supports retrieving process results, enabling agents to incorporate Boomi-driven integrations into broader automated workflows.

Authentication type

  • API Key - Requires a static API key to be configured before the agent can connect to the service.

Uses

Use the Boomi Integration (Early Access) MCP connector to perform the following actions:

  • Trigger deployed Boomi Integration processes directly from an AI conversation
  • Kick off data synchronization workflows between connected business systems
  • Automate order, invoice, and record processing without manual intervention
  • Launch integration processes on demand to keep systems up to date
  • Coordinate multi-system workflows through a single deployed process call
  • Reduce manual data entry by running existing integration workflows automatically
  • Connect AI-driven requests to established business process automation
  • Extend existing Boomi workflows to respond to natural language requests

Example prompts

Use the following example prompts to invoke Boomi Integration (Early Access) MCP connector tools from your AI assistant or Boomi Connect workflow:

  • Run the customer onboarding process in Boomi Integration.
  • Start the order sync workflow in Boomi Integration for today's orders.
  • Trigger the deployed invoice reconciliation process in Boomi Integration.
  • Kick off the inventory update process in Boomi Integration now.
  • Launch the employee data sync process in Boomi Integration.
  • Run the shipment notification workflow in Boomi Integration.
  • Execute the monthly billing process in Boomi Integration.
  • Start the CRM data refresh process in Boomi Integration.
  • Trigger the vendor payment workflow in Boomi Integration.
  • Run the deployed process that updates product catalog in Boomi Integration.

How the Boomi Integration MCP connector works

The Boomi Integration (Early Access) MCP connector connects Boomi Connect to Boomi Integration. AI agents connect to Boomi Connect through MCP and call the MCP tools exposed by the connector. The connector exposes one MCP tool to the AI agent for each available deployed Boomi Integration process.

AI agent
   │
   │ MCP
   ▼
Boomi Connect
   │
   │ Boomi Integration MCP connector
   ▼
Boomi Integration
   │
   └── Deployed Integration process

The way you author an Integration process affects how the AI agent identifies and uses the corresponding MCP tool. Process information determines the tool name, inputs, outputs, and execution behavior.

At runtime, the connector also exposes the describe_process tool. Before running an MCP tool, the AI agent uses describe_process to retrieve information about that tool. This information includes its inputs and outputs.

Configuring the Boomi Integration connection

As a connection administrator, you configure the Boomi Integration connection in Boomi Connect. Process authors configure the Integration processes that the connector exposes as MCP tools. Connection administrator and process author might be the same or different users.

Prerequisites

  • A Boomi Integration account and a user with a Platform API token.
  • At least one Boomi Integration process deployed to an environment with an attached runtime.

Setting up a connection

In Boomi Connect, enter the following required values from the Boomi Enterprise Platform to configure the Boomi Integration connection.

FieldWhere to find the value in Boomi Enterprise Platform
Account IDGo to Settings > Account > Account Information to view the account ID. For example, mycompany-A1B2C3.
User NameGo to Settings > My User Settings > User Information to view the email address associated with the user. Use the email address for the user who owns the Platform API token. For example, user@boomi.com.
Platform API tokenGo to Settings > My User Settings > Platform API Tokens. For example, 123aab45-67b8-9012-3a45-67c8e9e01e23.
Runtime IDGo to Manage > Runtime Management. Then, select a runtime to view the Runtime Information panel.

The connector also reads process information configured in Boomi Integration. Refer to Process information used by the connector for details.

Managing process tools

As a connection administrator, you can view the available process tools when you configure the connection. You can disable individual processes that you do not want the connection to expose. Disabled processes do not appear in the available tool list and cannot be invoked through the connection.

note

Processes that use a Listener start shape appear in the process list, but the connector cannot run them. Disable these processes when configuring the connection.

Authoring Integration processes for the connector

As a process author, you configure the Integration processes that AI agents call through the connector. The following sections explain how process authoring affects MCP tool inputs and outputs, tool selection, and how the connector handles execution behavior.

Process inputs and outputs

The Boomi Integration MCP connector derives MCP tool inputs and outputs from the underlying Integration process.

Inputs: The connector reads process property components and dynamic process properties used by the process and exposes these properties as MCP tool inputs.

Process property components can provide additional information about an input, including its label, help text, type, default value, and allowed values. Dynamic process properties provide only a name and default value.

Outputs: The connector returns any document that the process returns through the Return Documents shape as MCP tool output.

Process execution behavior

The Integration process determines whether the connector waits for the process to complete and what the MCP tool call returns. This behavior is defined in the Integration process, not in the Boomi Connect connection configuration.

Process configurationResult returned to the callerConnector wait time
The process uses a Return Documents shape.Documents returned by the process.Up to 30 seconds.
The process does not use a Return Documents shape.Confirmation that the process finished and its execution ID.Up to 30 seconds.
[mcp:async] is entered in the Notes field on the Start shape.Confirmation that the process started. The process continues to run in Boomi Integration.None.

Process authoring best practices

As a process author, follow these best practices to help the AI agent identify and use the correct MCP tool.

  • Name the process for its purpose: The process name becomes the MCP tool title and helps the AI agent select an appropriate tool. Use a descriptive name that reflects the process job, not its implementation mechanism. For example, the AI agent can select "Salesforce Lead search - find Leads by lot or batch" for a recall question and skip "API - Process 3".

  • Provide a process description: Explain what the process does and how it works. This context helps the AI agent decide whether to use the process.

  • Prefer process property components instead of dynamic process properties: A process property component provides a type, help text, allowed values, and a default value. A dynamic process property provides only a name and a default value.
    For complex processes, the additional detail that a process property component provides, helps the AI agent understand how to use each input. However, dynamic process properties are useful for simpler processes.

  • Describe the output in the Notes field on the Return Documents shape: Details about the returned process data help the AI agent understand the tool output and plan a chain of tool calls before calling the process.

  • Mark long-running processes with [mcp:async]: Type [mcp:async] in the Notes field on the Start shape.

Process information used by the connector

In addition to the required connection values, the connector reads the following information from the processes in Boomi Integration.

Process informationWhere the author sets it in Boomi IntegrationHow the connector uses it
Process nameProcess component nameProvides the MCP tool title and the main signal for tool choice.
Process descriptionDescription field on the process componentProvides description in describe_process.
Start shape notesNotes field on the Start shape containing [mcp:async]Returns as soon as the process run starts instead of waiting.
Return Documents shapeWhile adding a Return Documents shape to the processProvides returnsOutput and determines whether output is fetched after the run.
Return Documents notesNotes field on the Return Documents shapeProvides outputNotes in describe_process, which describes the output shape.
Process Property referenceThe process uses a process property component.Creates an input named from the Component and Label.
Label, Help Text, Type, Default, Allowed ValuesConfigure these values on the process property component.Defines the input name, description, type, default value, and allowed values.
Dynamic process propertyThe process uses a dynamic process property.Creates an input containing only its name and default value.

Considerations

Consider the following when using the Boomi Integration connector:

  • Processes that use a Listener start shape appear in the process list, but the connector cannot run them.
  • The connector lists only the first 500 processes deployed to the selected runtime's environment. Processes beyond that limit do not appear in the tool list.
note

No tools are currently available for this connector.

On this Page