Node Types Explained
Nodes are the building blocks of workflows. Each node performs a specific function - triggering the workflow, performing actions, or controlling flow.
Node Categories
Triggers
Triggers start your workflow. Every workflow needs exactly one trigger.
| Trigger | Description | |---------|-------------| | Form Submission | Fires when a form is submitted | | Webhook | Fires when an HTTP request is received | | Schedule | Fires on a time schedule (cron) | | Manual | Fires when manually triggered |
Actions
Actions perform operations. Connect multiple actions to build your automation.
| Action | Description | |--------|-------------| | HTTP Request | Make API calls to any service | | Send Email | Send emails via your configured provider | | Database | Query or update databases | | Plugin Actions | Actions from installed plugins (Slack, etc.) |
Logic
Logic nodes control how data flows through your workflow.
| Logic Node | Description | |------------|-------------| | Condition | Branch based on data values | | Switch | Multiple branches based on value | | Loop | Iterate over arrays | | Delay | Wait before continuing |
Transform
Transform nodes modify data passing through.
| Transform | Description | |-----------|-------------| | Map | Transform array items | | Filter | Remove items from arrays | | Merge | Combine multiple data sources | | Code | Custom JavaScript transformation |
Trigger Nodes Deep Dive
Form Submission
Triggers when a user submits one of your forms.
Output data:
{
"formId": "abc123",
"submissionId": "xyz789",
"fields": {
"name": "John",
"email": "john@example.com"
},
"submittedAt": "2024-01-15T10:30:00Z"
}
Webhook
Receives HTTP requests from external services.
Configuration:
- URL: Your unique webhook endpoint
- Method: GET, POST, PUT, DELETE
- Authentication: None, API Key, or Bearer Token
Output data:
{
"headers": {},
"body": {},
"query": {},
"method": "POST"
}
Schedule
Runs on a time-based schedule.
Configuration:
- Interval: Every X minutes/hours/days
- Cron: Advanced scheduling with cron expressions
- Timezone: Your preferred timezone
Action Nodes Deep Dive
HTTP Request
Make requests to any REST API.
Configuration:
- URL: The endpoint to call
- Method: GET, POST, PUT, PATCH, DELETE
- Headers: Custom headers
- Body: Request payload (for POST/PUT)
- Authentication: None, API Key, Bearer, Basic, OAuth
Send Email
Send emails through your connected provider.
Configuration:
- To: Recipient email(s)
- Subject: Email subject line
- Body: HTML or plain text content
- Attachments: Optional file attachments
Logic Nodes Deep Dive
Condition
Creates two branches based on a condition.
Configuration:
- Field: The data field to check
- Operator: equals, contains, greater than, etc.
- Value: The comparison value
Branches:
- True: Continues when condition is met
- False: Continues when condition is not met
Loop
Iterates over an array, running subsequent nodes for each item.
Configuration:
- Array: The data field containing the array
- Item Variable: Name for the current item
Best Practices
- Start simple - Begin with trigger + one action, then expand
- Name your nodes - Use descriptive names for clarity
- Test incrementally - Test after adding each node
- Handle errors - Add error handling for critical actions
- Use conditions wisely - Keep branching logic simple
Next Steps
- Using Variables - Pass data between nodes
- Conditional Logic - Advanced branching
- Debugging Errors - Troubleshooting tips