Execution scope
The four execute operations run a single capability using the selected environment’s draft. They do not start a conversation, require agent compilation, or populate conversation variables. External effects can still occur. Integration actions use the project’s Draft connection; MCP tools use the saved server connection.
Result fields
Outputs by capability
Example result
Illustrative successful function result; values depend on the saved function:
Inputs, secrets, and failures
Input rules
Functions and API tools accept strings keyed by declared input name. Every declared input is required, and undeclared names are rejected. Integration and MCP tools accept JSON inputs according to their schema; get the schema before constructing the request. For integrations, toolName is a catalog action name belonging to the selected provider.
Secrets and connection state
Use {secret_name} in a string input to reference a project secret. Conversation-variable tokens have no conversation state to resolve against. For integration/MCP inputs, only top-level string values receive secret substitution: placeholders inside nested objects or arrays are sent as written. The runtime redacts loaded secret values from returned results; do not treat this as permission to paste credentials into arbitrary inputs. Saved MCP connection settings can use their configured variables and secrets independently of the input map.
Timeouts and truncation
Functions and API requests use the smaller of their configured/default timeout and 18 seconds. The API’s runtime client has a separate 30-second timeout; this is not a promise that a remote integration action is cancelled. Timeout results have success: false, output: null, and an error explaining that the tool may still have run.
Selected payloads above 64 KiB of serialized JSON are cut and returned as strings. For functions, truncation applies to individual output variables and trace payloads; for API tools it applies to the response body; integration/MCP results are truncated as tool output. This is not a total response-size guarantee. Check truncated before treating output as complete structured data.
Failure handling
Input validation and authorization can fail before execution. Missing secret values can produce a 422; rate limiting can produce a 429. An unavailable execution route in an older runtime deployment is reported as a 503. Tool failures can instead be returned in the normal result envelope. Check both layers. After a timeout or ambiguous transport failure, reconcile external effects before retrying; direct execution supplies no general idempotency guarantee.
Related guides
Run tools without a conversation · Function MCP execution · API tool MCP execution · Integration MCP execution · MCP tool execution