Trigger Node
Triggers define how and when your workflow starts executing.
Trigger Types
Event Trigger: Automatically starts when a record is created, updated, or deleted in a selected table.
Manual Trigger: Starts when explicitly triggered via API or UI, with optional input parameters.
Scheduler Trigger: Runs automatically on a schedule using cron expressions.
Input Fields - Event Trigger
Table/Collection: Select the database table or collection to monitor for changes. Choose from Truco tables (invoices, accounts, contracts, etc.) or integrated third-party collections.
Actions: Select which operations trigger the workflow - Created (new records), Updated (modified records), or Deleted (removed records). You can select multiple actions.
Input Fields - Manual Trigger
Collection (Optional): Optionally associate this workflow with a specific collection for organizational purposes.
Input Schema: Define the structure of data that users must provide when triggering the workflow. Use the visual schema builder to add fields like text, numbers, dates, etc.
Input UI Schema: Customize how input fields are displayed in the trigger form (field order, labels, help text).
Input Fields - Scheduler Trigger
Cron Expression: Define when the workflow runs using cron syntax or select from preset schedules (hourly, daily, weekly, monthly). Examples: 0 9 * * * runs daily at 9 AM, */15 * * * * runs every 15 minutes.
Stop Conditions
Predefined Conditions: Select from available stop conditions like ‘Recipient responds to workflow’ or ‘Entity is not overdue’.
Custom Conditions: Write JavaScript expressions using workflow variables. Example: ${workflow.variables.status} === 'completed'. The workflow stops when the condition evaluates to true.
Tips:
- Use event triggers for automated workflows based on data changes
- Use manual triggers when you need user input or want to control execution timing
- Test your trigger configuration using the Test tab
- Custom stop conditions support full JavaScript expressions with workflow variables