Portal Community

What Are Node Capabilities?

A node capability declares what external system category a node integrates with. It is a classification tag — not a runtime contract — that tells the platform:

Capabilities are declared with a simple attribute on the executor class. The engine discovers them automatically at startup — no manual registration required.

The 12 Capability Types

#CapabilityDomainExample Nodes
1WebhookHTTP event triggers & outbound callsWebhookTriggerNode, WebhookCallNode
2BusinessServiceInternal platform service APIsBusinessServiceCallNode
3FormAtlas Forms HIL integrationUserFormNode
4WidgetUI widget HIL stepsWidgetNode
5MessagingSlack, email, SMS, pushSendSlackNode, SendEmailNode
6IdentityUser lookup, roles, permissionsUserLookupNode, PermissionCheckNode
7EntityBusiness entity CRUDEntityReadNode, EntityQueryNode
8DatasourceSQL, REST, DataOcean queriesSqlQueryNode, RestDatasourceNode
9RuleRule engine evaluationRuleEvalNode
10ProcessWorkflow lifecycle controlStartWorkflowNode, CancelWorkflowNode
11DIDCommDecentralized identity messagingDIDCommSendNode, VCVerifyNode
12MCPAI tool server callsMCPToolCallNode

Why Capabilities Matter

Gateway to deep dives: Each capability type has its own dedicated guide (Guide36 through Guide47). This overview guide is the entry point — use the Capability Type Map page to navigate to the specific guide for each capability.