Overview
Voiceflow integrates with Boomi so your AI agent can call a deployed integration process and use its returned delivery information in a customer conversation. Boomi runs the external workflow; Voiceflow calls its approved endpoint and uses the response in the conversation.
Examples of when to use Boomi
- Connect the business service — prepare its authorization, schema and test resources.
- Return a delivery update — invoke the configured service and interpret its current result.
- Recover a failed request — inspect execution and downstream state before retrying.
Studio
Use an editable test project in Agent studio. Your integration developer or administrator prepares the service below, supplies its endpoint and credentials, and gives you a verified test request plus its expected result. Keep provider-side deployment with that owner.
Code
Use a Voiceflow personal or service key with project access, a current Voiceflow CLI and the selected test Environment. You prepare the provider service and create, execute and attach the Voiceflow request separately. The examples use a test project; they can read or change connected systems.
Connecting Boomi
Prepare a deployed endpoint and the credentials for its approved operation.
Prepare the provider service
Studio
Ask your Boomi administrator or integration developer to complete the service setup linked below. Obtain all four handoff items before creating the Voiceflow tool:
- The deployed HTTPS endpoint and its exact authentication headers.
- The credential value for the Voiceflow Secret.
- A request schema, response schema and verified test customer/resource.
- A successful test response and a rejected unauthorized request, confirmed in the provider’s execution history.
The sample request fields on this page are a recipe contract for your existing workflow. Have the owner map them to that workflow; a provider account alone does not create this endpoint.
Code
Prepare the listening process
Ask your Boomi integration developer to expose your existing delivery lookup process with a Web Services Server connector using Listen. This connector requires the applicable Boomi edition. For this recipe, choose Operation Type: Query and Object: Delivery. Set both Input Type and Output Type to Single JSON Object, select the corresponding JSON profiles, and define request strings customer_id and order_id. Copy the generated Simple URL Path, ending in /ws/simple/queryDelivery for this example. The process must verify that the customer may access the order before retrieving delivery details.
Return one useful JSON document
Map the lookup into one JSON document containing order_id, status and estimated_delivery. End that process path with Return Documents, matching the operation’s output profile. A standard 200 from the web server without that document does not supply delivery data. Return an explicit business error when the order is unavailable; do not map an empty document to a successful delivery answer.
Deploy and authorize the runtime
Deploy the process to the intended runtime and confirm its listener in Manage → Runtime Management → Listeners. Obtain the HTTPS base URL from Shared Web Server, then append the operation’s actual simple HTTP path; the example path below is a recipe choice, not a Boomi-wide endpoint.
For this recipe, the runtime administrator uses API Type: Basic and Authentication Type: Basic on a dedicated test runtime. The username is the Boomi account ID and the password is the generated authentication token. These are web-service credentials, not your Boomi Platform API credentials. Prepare Basic followed by the Base64 encoding of ACCOUNT_ID:AUTHENTICATION_TOKEN. Store the complete header value as boomi_authorization. Base64 does not encrypt it; use HTTPS.
Verify the service handoff
The developer supplies the deployed HTTPS endpoint, full authorization value, input/output profiles and a verified test customer/order pair. Confirm the service returns the matching JSON document and rejects another customer’s order. If the existing runtime uses Advanced API Services or another authentication type, obtain its actual endpoint and credential contract instead of changing shared server settings to match this recipe.
Provider setup: Web Services Server operation, Shared Web Server authentication and web-service responses.
Create the Voiceflow request
Studio
Store the service credential
Open your test project in Agent studio, then More → Secrets. Create boomi_authorization with the credential supplied by the service owner. Creating its default also writes Main’s Published value, so keep initial setup in a test project. If the selected Environment has a different Draft credential, set its Draft override too.
Create a request variable
Open More → Variables, create boomi_request with an empty default and ask your application developer to populate it with the prepared request. For a Studio Run test, temporarily set its default to the developer’s prepared test string in this isolated test project; backend runtime variables do not automatically populate Studio Run. Clear the default after that test.
Configure the API request
Open Agent → Global tools → + → API and name the tool Check a delivery request. Choose POST, set the owner-supplied endpoint and add the headers below. Set the raw JSON body to {payload}.
Bind inputs before running
Open the attached tool’s inputs. Open authorization and set its Default value to the Secret boomi_authorization, and set payload’s Default value to boomi_request. Keep Async execution off so the agent receives this call’s response. The provider workflow may still return a pending receipt.
Code
Set VF_TOKEN, PROJECT_ID and ENVIRONMENT for the test project. Set PROVIDER_CREDENTIAL to the complete Boomi Basic header value. The service owner supplies PROVIDER_URL and the verified test request.
Save this definition as boomi-tool.json, replacing the illustrative URL with PROVIDER_URL. Braced names declare inputs on this API tool; they are bound to Secrets/variables on its attachment later.
Save apiTool.id as API_TOOL_ID, then discover input IDs:
Save apiTool.id as API_TOOL_ID, then discover input IDs:
Creating the Secret default also writes Main’s Published value. If your selected Environment uses a different credential, set its Draft override before testing. Match each variables[].name to its id for the attachment; resolve unresolvedReferences before continuing.
Check a delivery request
Provide a verified request and use the result from the current call.
Invoke Check a delivery request when the customer asks where their order is. The authenticated application supplies the verified identity and prepared request variable before the call; keep those inputs bound to trusted defaults. Use the returned order ID, delivery status and estimated delivery only after confirming they belong to the requested order. For a pending result, explain that work is waiting. For a current failure or missing required fields, say the result could not be confirmed; never reuse an earlier result or automatically repeat an uncertain write.
Prepare the request
Code
The application developer builds the request from an authenticated customer/resource and the confirmed task. Save this illustrative body as boomi-request.json, replacing test identities with values the application has verified:
Serialize it with the literal-safe request encoder: node encode-request.mjs boomi-request.json > boomi-payload.txt. It preserves quotes, newlines and literal text such as {customer_name} without treating that text as a Voiceflow variable or Secret. Do not concatenate customer text into quoted JSON placeholders.
Studio
Have your developer deliver the encoded string and populate boomi_request in the authenticated client’s next action before this tool runs. They send variables on the runtime action; creating the variable or session alone does not fill it. For Studio Run, use the temporary test default described above, then clear it. The provider service must enforce customer access and validate the request; tool descriptions do not enforce either.
Code
Read the confirmed body, encode it, and build standalone inputs. This tests the saved request against the selected Environment’s Draft; it does not attach the tool or publish the agent.
Require success: true, inspect output.status and output.body, and check the business fields against the service owner’s response schema. truncated: true means the returned body is incomplete. On timeout or error, inspect provider execution before retrying a write.
Let the agent use the request
Studio
Describe the trigger and result use
Open the attached Check a delivery request tool and set Trigger to the condition below. Its input defaults must already point to the Secret and prepared request variable; the model must not collect credentials or choose another customer’s identifier.
Test the conversation
In Run, use the verified test request. Ask “Where is my order?” and confirm the intended tool runs with the fixed identity and prepared payload. Inspect the current tool result in Run and compare it with the order in the business system. Also test the rejected-resource case: the agent must not claim success or expose another customer’s data.
Code
Save this as boomi-attachment.json. Replace YOUR_API_TOOL_ID and each input ID with the values discovered above. The payload and credential are defaults, not model-collected inputs.
Your authenticated backend supplies the encoded payload as variables.boomi_request on the next runtime action. Use a test client bound to this project’s Draft, ask for the order status and inspect the emitted tool call, current response and agent answer. Verify both the successful and rejected-resource cases. The backend/provider enforces access; the description is model guidance, not an authorization gate.
The attached API tool returns the provider body to the agent. For a Workflow’s Capture response, paths start at that body: for example status rather than standalone output.body.status. A missing capture can leave an earlier variable value unchanged; clear result variables before a Workflow call and branch on the current HTTP/business outcome. These Global tool examples use the current result directly.
Maintaining the connection
Inspect provider execution, update credentials and test the intended deployment.
Replace a credential
Inspect the original provider execution
Use the request ID and execution time to find the provider run and its downstream record. A timeout can follow a completed side effect; reconcile that state before repeating a write.
Update the intended credential version
Studio
Open the same project and More → Secrets, select the provider Secret and update the target Environment’s Draft value for testing. After validation, explicitly set the Published value for the intended Environment; this changes the credential serving live traffic.
Code
Retain secret.id from creation as SECRET_ID, set PROVIDER_CREDENTIAL to the replacement and use the value operation below. After validation, explicitly set the Published value for the intended Environment; this changes the credential serving live traffic.
Code
Save the Draft update body as credential-value.json:
For the selected Environment’s Published credential, change versionVariant to published after the Draft test. To replace the project default, omit environmentAlias and versionVariant; this also writes Main’s Published value. Test the intended connection before changing a live default.
Before launch, select the target Environment and supply the provider Secret’s Default value for its published agent; a Draft override alone does not supply Published. Publish the tested configuration, then repeat the conversation test against that Environment’s published client and verify the provider account/resource it reaches.
Rotate the credential with the provider owner, update the relevant Secret default/Environment overrides, and retest the existing tool. Removing a tool from Voiceflow does not remove the provider deployment or revoke its credential. Disable/revoke access in Boomi when retiring the integration, then remove the unused attachment and API resource.