Triggers & Actions
Complete reference for workflow triggers and actions.
Triggers
Section titled “Triggers”Triggers start your workflow. Every workflow needs exactly one trigger.
Manual Trigger
Section titled “Manual Trigger”Run the workflow by clicking a button.
Configuration:
- Button label
- Required inputs (form fields)
Use when:
- Testing workflows
- On-demand processes
- User-initiated actions
Schedule Trigger
Section titled “Schedule Trigger”Run on a recurring schedule.
Configuration:
| Field | Options |
|---|---|
| Frequency | Hourly, Daily, Weekly, Monthly, Custom |
| Time | Specific time of day |
| Timezone | Your preferred timezone |
| Days | Which days (for weekly) |
Cron syntax for advanced scheduling:
0 9 * * 1-5 # 9am weekdays0 0 1 * * # Midnight on 1st of month*/15 * * * * # Every 15 minutesUse when:
- Regular reports
- Data sync jobs
- Scheduled notifications
Node Types
Section titled “Node Types”Workflows are built using nodes. Each node represents a step in your workflow.
Human Node
Section titled “Human Node”Requires human input or approval before continuing.
Configuration:
| Field | Description |
|---|---|
| Task Name | Name of the task |
| Task Description | Instructions for the human |
| Assigned Users | Specific users who can respond (optional) |
| Default Value | Required for scheduled workflows |
Use when:
- Approval workflows
- Data entry tasks
- Review processes
Agentic Node
Section titled “Agentic Node”Runs an AI agent (Corint or a custom agent).
Configuration:
| Field | Description |
|---|---|
| Task Name | Name of the task |
| Task Description | Prompt or instructions for the agent |
| Agent | Which agent to use (default Corint or custom) |
| Executor | User whose OAuth credentials to use (optional) |
Example task description:
Analyze the following customer feedback and categorizethe sentiment as positive, negative, or neutral:
{{previous_node.output.feedback_text}}Use when:
- AI-powered analysis
- Content generation
- Data processing
Tool Node
Section titled “Tool Node”Executes a specific tool.
Configuration:
| Field | Description |
|---|---|
| Task Name | Name of the task |
| Task Description | Instructions for tool usage |
| Tool | The tool to execute |
Use when:
- Direct tool operations
- Utility functions
Plugin Node
Section titled “Plugin Node”Executes a plugin action.
Configuration:
| Field | Description |
|---|---|
| Task Name | Name of the task |
| Plugin | The plugin to execute |
Use when:
- Custom integrations
- Plugin-specific operations
Workflow Structure
Section titled “Workflow Structure”Workflows use a graph-based structure:
Nodes and Edges
Section titled “Nodes and Edges”- Nodes: Individual steps (human, agentic, tool, or plugin)
- Edges: Connections between nodes that define execution flow
- Parallel Execution: Nodes with no dependencies can run simultaneously
Execution Flow
Section titled “Execution Flow”- Workflow starts with nodes that have no predecessors
- Each node executes when all its predecessor nodes complete
- Nodes can have multiple predecessors (wait for all) or multiple successors (branch)
- Execution continues until all nodes complete or an error occurs
Variables and Context
Section titled “Variables and Context”Workflows pass data between nodes through context:
- Node Outputs: Each node’s output becomes available to subsequent nodes
- Previous Node Data: Reference outputs from previous nodes in the workflow
- Workflow Context: Shared data available throughout the workflow execution