Hermes icon

Hermes

Validate, approve, route, and execute AI-generated actions safely

Actions7

Action → Execute Action

AI-generated

Summary

Builds an action from the selected input, fills missing fields from the node parameters, applies local safety and approval checks, then sends it to the Hermes API to execute. Choose an action name, target service, target operation, and payload in the input or fallback fields; execution requires Hermes API credentials.

Inputs

  • Input Source — Use the whole incoming item (default), enter Manual JSON, or read action JSON from a Specific Field. Whole-item mode can detect an action in output, action, command, hermes_action, or data.
  • Input Field Name — In Specific Field mode, the field path containing the action JSON, such as output or data.action.
  • Manual JSON — The action object to process when Manual JSON is selected.
  • Action Name — Fallback action identifier when the input has no action field.
  • Target Service — Fallback service when the input has no target_service: Gmail, Google Calendar, Whatsapp, Crm, Tasks, Reminders, Reports, Webhooks, or Custom Api.
  • Target Operation — Fallback operation when the input has no operation field.
  • Payload JSON — Fallback data object when the input has no data object.
  • Requires Approval — Fallback for requires_approval when it is absent from the input.
  • Approval Status — Fallback for approval_status when absent from the input; supports Approved, Not Required, Pending, and Rejected.
  • Safety Level — Fallback for safety_level when absent from the input; supports Critical, High, Low, and Medium.
  • Dry Run — Fallback for dry_run when absent from the input. Select the Dry Run Action operation to force simulation.
  • Advanced Options — Configure local allowed, blocked, and sensitive action lists; correlation and idempotency IDs; raw response inclusion; log level; retry count (0–5); and request timeout (1–600 seconds).

Output shape

One output item per input item, containing a normalized action result.

Success output includes success, status, action, target_service, operation, result, error, approval_required, correlation_id, idempotency_key, and executed_at. Include Raw Response adds raw_response. Local validation failures throw unless Continue On Fail is enabled, in which case failures are returned as normalized items. Approval-required actions return an approval_required status without being executed.

Examples

Example 1: Use an action from an incoming item

Select Entire Input Item and provide an action object with action, target_service, and operation; data is optional and can fall back to Payload JSON.

Example 2: Supply action JSON directly

Select Manual JSON and enter the action object, or select Specific Field and set its field path. Fallback parameters fill missing action fields.

Example 3: Restrict actions before execution

Set Allowed Actions and/or Blocked Actions in Advanced Options; sensitive actions can trigger approval checks according to the approval policy configured in the Hermes credentials.

Links

Discussion