Node Types
AgentVerse nodes are the building blocks of every orchestration. Each node performs a specific function and connects to other nodes to form a workflow.
Categories
Trigger Nodes
Trigger nodes start an orchestration. Every orchestration must have exactly one trigger node as its entry point. Trigger nodes have no inputs — they only produce outputs.
| Node | Description |
|---|
| Webhook | Start an orchestration via an incoming HTTP request |
| Starter — Schedule At | Run an orchestration on a time-based schedule |
| Starter — Manual Trigger | Start an orchestration manually from the UI |
| Airtable Trigger | Trigger on Airtable record events |
| Slack Trigger | Trigger on Slack events (messages, reactions, etc.) |
| WhatsApp Trigger | Trigger on incoming WhatsApp messages |
| Shopify Trigger | Trigger on Shopify store events (orders, carts, products, etc.) |
| SubVerse AI Trigger | Trigger when a SubVerse AI voice call completes |
Action Nodes
Action nodes interact with external services. They receive data from upstream nodes, perform an operation (API call, database write, file upload), and return a result.
| Node | Description |
|---|
| Slack | Send messages, manage channels, and interact with Slack |
| Airtable | Read, create, update, and delete Airtable records |
| Shopify | Manage Shopify orders, products, customers, and inventory |
| WhatsApp | Send WhatsApp messages and manage contacts |
| HTTP Request | Make HTTP calls to any external API |
| File Upload | Upload files to cloud storage (S3) |
| Respond to Webhook | Send a custom HTTP response back to a webhook caller |
Logic Nodes
Logic nodes control the flow of an orchestration. They branch, loop, pause, or wait for external input before continuing execution.
| Node | Description |
|---|
| Conditions | Branch execution based on one or more conditions |
| For Loop | Iterate over a list of items or repeat N times |
| Wait | Pause execution for a duration or until an event |
| Human in the Loop | Pause and require a human approval to continue |
AI Nodes
AI nodes integrate language models and AI agents into your orchestration. They support multi-modal operations and can connect to other nodes as tools.
| Node | Description |
|---|
| AI Agent | Call any LLM provider to generate text or images |
| SubVerse Agents | Execute SubVerse AI agents over voice, WhatsApp, email, or chat |
Connection Types
Nodes communicate over two types of connections:
| Type | Description |
|---|
| Main | The primary data flow between nodes — carries JSON data from one node to the next |
| AI Tool | Connects tool nodes to an AI Agent node, making them callable by the agent during reasoning |
AI Tool connections are only available on the AI Agent node. Connect any action or logic node as a tool to give the agent the ability to call it autonomously.
Data Flow and {{ }} Expressions
Data moves between nodes as structured JSON. Reference any upstream node’s output in a parameter field using the {{ }} expression syntax:
{{ nodeName.fieldName }}
{{ nodeName.nested.field }}
{{ forLoop.item.email }}
See Dynamic Inputs for the full guide on expressions, the field picker, and common patterns.
Node Parameters
All nodes share a common parameter structure:
| Property | Description |
|---|
| Display Name | Label shown on the canvas |
| Node Name | Internal identifier used in {{ }} expression references |
| Credentials | Stored authentication details for external services |
| Parameters | Node-specific configuration fields |
{{ }} expressions, and dynamic option loading from connected external services.
