Introduction

This article explains the trigger rules that apply to various workflow operations.

Use Cases

When designing workflows, you may often need to determine whether a particular workflow operation triggers other workflow-related features, validations, or actions. The trigger rules for common workflow operations are summarized below.

Trigger Rules

Whether the workflow operations listed to the right will trigger the items below	Overdue Actions (Auto-submit & Auto-return)	Auto-submit Rules	Initiate Workflow upon Import	Child Workflow	Initiate Workflow through Automations	Workflow Batch Submission	Initiate Workflow via API
Form Validations Required Field Validation Required Approval Comment Validation Node Validation	❌	❌	❌	❌	❌	❌	❌
Default Values, Formulas, and Data Linkage	❌	❌	❌	❌	❌	❌	❌
Aggregate Table Validation	❌	❌	❌	❌	❌	❌	❌
Proceeding Conditions	✅	✅	✅	✅	✅	✅	✅
CC	✅	✅	✅	✅	✅	✅	✅
Automations	✅	✅	❌	✅	✅	✅	Controlled by the `is_start_trigger` field. Automations are not triggered by default.
Webhook Data Push Webhook（Message）	✅	✅	Data Push: ❌ Webhook(Message): ✅	✅	✅	✅	Data Push: ❌ Webhook(Message): ✅
Overdue Actions	✅	✅	✅	✅	✅	✅	✅
Auto-submit Rules	❌	✅ A single auto-submit sequence can process up to 50 nodes. Loop detection is performed during each auto-submit sequence. Processing stops when the workflow reaches a node that has already been processed automatically.	✅	Approver has processed the workflow: Child workflows are excluded when evaluating this auto-submit rule. Approver is the same as the previous: Child workflows participate in rule evaluation with the approver treated as empty. Therefore, the node immediately following a Child Workflow node can never be auto-submitted.	❌	✅	❌
Child Workflow	✅	❌The workflow record remains at the parent node of the Child Workflow node.	—	—	—	✅	✅

Trigger Rules for Workflow Operations

Introduction

Use Cases

Trigger Rules