Workflow node catalogue

GET /v1/orgs/{orgId}/automation-nodes and the read-only MCP tool automation_node_catalog describe all canonical workflow action kinds plus Slack post (slack_post) and GoodQA issue creation (create_issue) connector descriptors. CRM read permission and the automation feature gates apply. Responses are private and must not be cached.

Each node includes its connector, effect class, prerequisites, documentation, availability, missing prerequisite reasons and settings paths, and connection counts. catalogIdentity references the existing automation schema and semantics catalogue; identity hashes this node list including the caller's current availability. The action schemas remain available through the existing automation catalogue rather than being copied here.

ready: the discoverable prerequisites currently resolve. Execution still requires all target-specific checks.
needs_connection: an active connection or channel binding is missing.
needs_permission: the caller lacks a required permission, machine grant or saved revision grant.
not_enabled: the runtime does not accept the action kind, or its feature is disabled.

Unsupported connector kinds always return not_enabled, even when a connection exists. Slack requires org:manage_integrations permission plus an active, unrevoked, unexpired installation and a bound channel; missing chat:write is a permission prerequisite. Channel names are returned only to integration managers. Tokens, secrets, machine names, project names and connection identifiers are never returned.

Every executable node requires CRM edit permission, matching the workflow engine. Webhook discovery counts enabled non-persona endpoints and checks the webhook feature and integration permission. Machines check the per-org machines.enabled platform switch and count the caller's live grants through the existing read-only machine authority helpers. GoodQA projects count only active tenant projects where the actor has the canonical issue:create permission, including custom roles and extra permissions. Agent decisions require a saved delegated revision, explicit human grant and configured model/daemon; a general catalogue has no saved revision to authorize. Lifecycle expansion requires a current lifecycle event context.

Discovery is advisory and never a grant. It does not connect an integration, write a workflow, approve a command, start an agent, send a message or call a provider. Permissions, key ceilings, org policy, grants, target references and approvals are checked again at execution. Queued outbound work is not confirmed delivery; draft email is for human review and sending.

Production registration is delivered separately by the epic adoption task; see the module's registration proposal.

Workflow node catalogue

ready: the discoverable prerequisites currently resolve. Execution still requires all target-specific checks.

needs_connection: an active connection or channel binding is missing.

needs_permission: the caller lacks a required permission, machine grant or saved revision grant.

not_enabled: the runtime does not accept the action kind, or its feature is disabled.

Production registration is delivered separately by the epic adoption task; see the module's registration proposal.

Workflow node catalogue

ready: the discoverable prerequisites currently resolve. Execution still requires all target-specific checks.
needs_connection: an active connection or channel binding is missing.
needs_permission: the caller lacks a required permission, machine grant or saved revision grant.
not_enabled: the runtime does not accept the action kind, or its feature is disabled.

Production registration is delivered separately by the epic adoption task; see the module's registration proposal.