Automata Provider Webhook icon

Automata Provider Webhook

Receives Automata provider execution calls via webhook and forwards payload to the workflow

Automata Provider Webhook

AI-generated

Summary

Receive and process execution calls from Automata via webhook, validating Bearer JWT tokens and optionally responding immediately to Automata. Register this webhook as an Automata provider with configurable agent metadata to enable Automata to invoke the workflow for specific intents and tasks.

Inputs

  • Respond Immediately — Optionally send a 200 OK response immediately upon receiving the webhook call, or defer response to a later Respond to Webhook node.
  • Registry Environment — Select the Automata registry environment (Dev, Prod, or Custom URL) where this webhook will be registered.
  • Registry URL — Custom Automata registry URL (required if Registry Environment is Custom).
  • Webhook URL to Register — Choose whether to register the production or test webhook URL with Automata.
  • JWT Secret (required) — The JWT secret key configured in your Automata provider to validate execution tokens and register the webhook securely.
  • Agent ID (required) — Unique Automata agent identifier string, namespaced, to identify this provider.
  • Agent Name (required) — Name of the agent as displayed in Automata search results.
  • Description (required) — Text describing the agent's functionality, influencing search ranking.
  • Intents (required) — Comma-separated list of dot-notation intents supported by this agent.
  • Tasks — Comma-separated list of task names that the agent supports.
  • Categories (required) — Comma-separated categories used for ranking the agent.
  • Tags (required) — Comma-separated keywords and tags for discovery and search.
  • Location Scope (required) — Location information to scope the agent, e.g., city or region.
  • Languages (required) — Comma-separated list of language codes supported by the agent.
  • Version (required) — Agent version string.
  • Input Schema (JSON) — Optional JSON Schema string describing expected input parameters.
  • Meta (JSON) — Optional JSON metadata to expose in Automata search results.

Output shape

A single JSON object containing the received webhook payload details (agentId, task, parameters, token payload, HTTP headers, query, and path parameters) is emitted as main output. If 'Respond Immediately' is enabled, the node also sends a 200 OK HTTP response immediately.

The webhook expects an HTTP POST with an Authorization header containing a Bearer JWT token signed using the configured JWT Secret. The token must match the configured Agent ID. Webhook URL registration happens automatically upon create call. If the incoming request authorization is missing, invalid, or the token agent_id mismatches, the node responds with HTTP 401 or 403 errors encapsulated in the webhook response and no workflow data is emitted. The node does not handle webhook response if 'Respond Immediately' is disabled; instead the workflow should respond later using a Respond to Webhook node.

Discussion