Start nodes attribute

• Type: object[]
• Data types: Automation
• Fields: start_nodes

For automations, start_nodes contains one or more ordered conditions that can independently run the same saved prompt. The conditions use OR behavior; the automation does not wait for every item to match.

Notes

• Each item includes a stable start_node_id, trigger_type, public trigger_config, summary, and available type-specific details.
• A trigger-schedule item's trigger_config.jitter_policy is standard or none. Missing legacy values serialize as standard. none removes deliberate jitter but does not promise exact execution because due schedules are discovered once per minute and can be delayed by the queue or runtime.
• A trigger-saved-search-results item includes its independent lowercase frequency and nullable next_run_at. The frequency remains required in every status, while the next run is present only when the workflow version is published. Its trigger_config contains saved_search_model_id and the same frequency.
• Use start_node_id with Update_Automation to update or delete one trigger without replacing the others.
• Include start_node_id with Test_Run_Automation when a multi-trigger automation needs to simulate one specific start condition.
• Search_Automations returns up to three start nodes by default. Compare the returned list with total_triggers_count and raise max_triggers when you need more.

Related articles

• Automations: Combine schedules, government-record changes, and workspace events in one automation.
• Create automation MCP tool: Supply one or more start-node definitions.
• Update automation MCP tool: Patch start nodes by stable ID.
• Search automations MCP tool: Request ordered start nodes and control how many are embedded.
• Test run automation MCP tool: Choose which start node a manual run should simulate.