Overview
Voiceflow integrates with Make so your AI agent can run an existing scenario, pass the confirmed inputs and use the scenario’s returned result. Make owns the connected apps, scenario logic and execution history. Voiceflow does not create or maintain the scenario for you.
Examples of when to use Make
- Connect the scenario owner — authorize the Make account and zone used by your workflow.
- Run a support automation — submit a confirmed service request or retrieve information across connected apps.
- Check completion before retrying — distinguish a completed scenario from an execution whose outcome is still unknown.
Studio
Use an editable Voiceflow test project and a Make account with API access. The scenario owner supplies its URL, configured inputs, expected outputs and a safe test record. Start with the packaged Run scenario action.
Code
Authorize Make in Agent studio, then use Voiceflow’s API or CLI to inspect the action schema, execute it in Draft and attach it to the agent. The OAuth connection is a browser prerequisite; the execution endpoint does not establish it.
Connecting Make
Authorize the account and zone that own the scenario.
Have the Make workflow owner activate the test scenario and define its scenario inputs and outputs. This Voiceflow connection requires Make API access, which the connector checks against the account’s plan. Obtain the full scenario URL, such as https://eu1.make.com/123/scenarios/456, and use its account zone when authorizing. Inputs and outputs are configured in Make, not inferred from the apps connected to it. See Make scenario inputs and outputs.
Authorize Make in Agent studio
Studio
Open the connection
Open your test project in Agent studio. In the left sidebar, choose More → Integrations, then Connect on Make. Use a separate test project/account for initial setup. Make uses the project’s Published connection for both Draft and Published runs; changing Environment does not isolate its credentials. Draft scenario/input defaults let you choose test resources within that connected account.
Authorize the scenario account
Enter the Make zone requested by the dialog, choose Connect and complete Make’s browser authorization. Use the account that owns the scenario. Return to Voiceflow and confirm the tool shows its connected account before testing an action.
Code
Visit the same project in Agent studio
Open Agent studio and select the project used by your API requests. In the left sidebar, expand More → Integrations, then choose Connect on Make. This OAuth setup needs the browser; integration connect accepts API-key integrations and does not provision Make OAuth.
Complete authorization and return to code
Enter the scenario account’s Make zone, select Connect and finish Make consent. Confirm Make is connected. Use a test project/account; a selected Environment does not itself isolate integration credential slots. Continue below with that project’s ID and a test Environment alias.
Run a scenario
Send confirmed inputs and use only the current execution’s result.
The packaged action is Run scenario (make_run_scenario). scenarioURL is required; optional data is an object whose keys and value types match the scenario’s inputs. Keep the scenario fixed in the tool configuration rather than letting the model select an arbitrary scenario.
These illustrative inputs record a callback request. The scenario owner must implement those inputs, authorization, validation and duplicate handling in the existing scenario before the agent uses them:
Configure and test the action
Studio
Add Run scenario
Open Agent, choose + beside Global tools, then Make → Run scenario. Open the attached tool. Set the scenarioURL default to your activated test scenario’s full URL, then wait for its scenario inputs to load automatically. If they do not appear, verify that the connected account can access that activated scenario before configuring its fields. The displayed fields must match Make’s scenario interface. Schema discovery and execution use the project’s Published Make connection. Keep the fixed scenario URL and its discovered interface aligned with that account/zone.
Assign each input's owner
Create variables for trusted customer identity and request_id in More → Variables, leaving their defaults empty outside the isolated Run test. Have the authenticated application populate them on the next runtime action before invoking the tool. Bind the tool’s trusted fields to those variables. Set the callback number and reason as customer-collected fields and describe their required format. Confirm them before submitting; enforce access and number validation in the scenario, because model guidance is not a validation gate.
For a Studio Run test, use temporary fictional defaults for identity/request ID in this test project. Backend runtime values do not automatically fill Studio Run. Clear those defaults afterward.
Describe invocation and check a conversation
Set Trigger to run only after the customer requests and confirms the callback. In the agent instructions, require the current scenario result before saying the request was recorded. In Run, ask for a callback, confirm its number/reason and inspect the Make tool call. Compare its returned record reference with the scenario’s execution history and callback queue. Test an invalid customer/number and a provider error: the agent must not claim completion.
You can instead use an Integration step at a fixed point in a Workflow. Choose Make and Run scenario, supply the same fixed URL and input bindings, then use Capture response only for paths verified in the current returned result. Clear old result variables before the call; missing captured fields do not clear older values.
Code
Set VF_TOKEN to a Voiceflow API credential, PROJECT_ID to the authorized test project and ENVIRONMENT to its test alias. Use a current Voiceflow CLI; it reads VF_TOKEN. Save the example above with your real test scenario URL as make-inputs.json, then wrap it in the execute request:
Require success: true, inspect output.data and compare Make’s execution ID/status and any scenario-defined outputs with its execution history. These calls select Draft project resources but resolve Make credentials from the project’s Published connection, and can perform real provider writes. A successful standalone call does not attach the tool. JSON data is a nested object; keep literal customer text inside that object rather than a top-level Secret-binding string.
Attach the action to the agent
Studio
The Global tool added above is already attached. Keep the fixed scenario URL, trusted identity/request ID and customer-collected fields distinct. Ask “Please arrange a callback about my delayed delivery”, then confirm the number and reason. The agent should call this action once and report the current request reference. A recorded callback request is not a completed phone call. If a call fails or returns no usable reference, explain that recording could not be confirmed and check Make before trying again.
Code
Add the catalog resource, then attach it with this scenario’s actual input schema. Save {"toolName":"make_run_scenario"} as make-catalog.json:
Keep integrationToolID as INTEGRATION_TOOL_ID and your scenario URL as SCENARIO_URL. Fetch its interface through the schema-refinement endpoint (an HTTP request is also required in the CLI workflow):
Require a non-null schema with the expected scenario fields; this endpoint can return an error body without an HTTP error. Schema refinement reads the project’s Published Make connection, as execution does. Keep the test scenario and its interface in that connected account/zone; selecting another Environment does not isolate the connection.
For the callback recipe, require string inputs request_id, customer_id, callback_number and reason in the returned schema. Create empty make_request_id and make_customer_id variables before binding them:
Your authenticated backend supplies those variables on the next runtime action, before the tool runs. The request ID remains stable for retries of the same confirmed request; the scenario validates customer access and deduplicates it before a write.
Save the following as make-attachment-template.json. Its nested input keys are the JSON paths the scenario editor uses; the model collects only the confirmed number and reason:
Build the attachment with your resource ID, fixed URL and actual returned schema:
Resolve unresolvedReferences. Test from a client bound to this project’s Draft: supply the verified customer/request variables, ask “Please arrange a callback about my delayed delivery”, confirm the number/reason and inspect the tool call. Require the current saved callback reference in the agent’s answer and a matching record in Make’s execution history and callback queue. Test an invalid customer/number and provider failure; the agent must not claim completion or reuse an earlier reference.
For an existing configured attachment, Get tool, rather than the compact list, returns its refined extendedInputVariables; preserve the applicable schema when editing it. Changing the scenario interface requires fetching/reviewing the new schema and retesting its bindings.
Completion and recovery
Check the original execution before repeating work that may have succeeded.
Make’s packaged action requests a responsive run. Make waits for completion, but a run lasting more than 40 seconds can time out while the scenario keeps executing. Voiceflow or your client can stop waiting sooner; the provider’s 40-second window is not a guaranteed conversation wait. The Voiceflow adapter does not register Make’s optional callback URL. A timeout is an unknown outcome, not cancellation. See Make’s Run a scenario contract.
Inspect the original scenario run
Open the scenario’s execution history in Make. Match the supplied request ID and execution time, inspect every required downstream action and check whether an output was produced. Scenario warnings or errors must not become a success answer merely because an execution ID exists.
Reconcile before retrying
If the scenario created the callback or another record, retain that record instead of submitting again. If the outcome is still unknown, report it as unconfirmed and let the workflow owner investigate. For retryable writes, have that owner deduplicate a stable request ID before the side effect; Voiceflow does not add provider-wide idempotency for you.
Repair and test the connection
For the activation error, activate the scenario in Make. For API-access errors, verify the account’s API entitlement. For authorization errors, open More → Integrations → Make → Manage in the same Agent studio project and reconnect the intended account/zone. Code readers need the same browser visit. Confirm the project’s connected account before any test: Make has no separate Draft connection, including for standalone execution. Reconnecting can change the credential used by Published traffic. Removing or disconnecting the account does not stop a scenario already running in Make.
Before launch, publish the tested agent and verify the published client reaches the intended Make connection and scenario. For work requiring a person or a longer process, use a separate receipt/notification design; the responsive call does not keep a conversation open until that work finishes.
Related guides: Run a cross-system workflow · Handle pending automation requests · Investigate a failed automation.