Actions7
Action → Execute Approved Action
AI-generatedSummary
Execute an action marked as approved by sending it to the Hermes API. Select the action from the input item, a specific field, or manual JSON; missing action details are filled from the node’s fallback fields.
Inputs
- Input Source — Choose the entire input item (which can auto-detect an action in output, action, command, hermes_action, or data), Manual JSON, or Specific Field.
- Input Field Name — For Specific Field, the dot-separated path to the action JSON, such as output or data.action.
- Manual JSON — For Manual JSON, provide the action object. It should include action, target_service, and operation; data and approval fields can also be supplied.
- Action Name, Target Service, Target Operation — Fallback values used when the selected input does not supply these fields. Target Service defaults to gmail.
- Payload JSON — Fallback data object used when the action input has no data object.
- Requires Approval, Approval Status, Safety Level, Dry Run — Fallback action settings. The action is locally checked against approval status and safety policy; if approval is required but status is not approved, execution returns an approval_required result without calling the execute-approved endpoint.
- Advanced Options — Configure allowed, blocked, or sensitive action lists; correlation and idempotency IDs; raw response inclusion; logging; retry count; and request timeout. Retry count is limited to 0–5 and timeout to 1–600 seconds.
Output shape
One output item per input item, containing a normalized result record.
Successful API responses include success, status, action, target_service, operation, result, error, approval_required, correlation_id, idempotency_key, and executed_at. With Include Raw Response enabled, raw_response is also included. Failures can be thrown or returned as success:false records when Continue On Fail is enabled. The operation POSTs to /v1/actions/execute-approved; it does not itself establish approval.