Get scenario execution with the Make API

Returns the status of one execution of a scenario, with the scenario outputs, or the error and the module that caused it.

Identifier
make_get_scenario_execution

The request

POST https://connect.reportei.com/api/tools/make_get_scenario_execution/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "scenarioId": 1,
    "executionId": "<executionId>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
scenarioIdintegerYesId of the scenario, from List scenarios.
executionIdstringYesId of the execution, from Run scenario or from the id of an item of List scenario logs.

Supported connections

Your customer connects their Make account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

When connecting, your customer also enters {zone}: the address of their account on the app's API.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/make_get_scenario_execution. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.