Automation

Events

• Automation event routes create and maintain trigger definitions such as new lead, customer status changed, mission done, ticket status changed, payment event, form submitted, room reservation, or message event.
• Use par/val and par2/val2 for filters such as source, folder, tag, status, custom fields, internal status, tab status, project column, or event-specific options.
• Activating or disabling an event controls whether the trigger can start its flow.

Actions

• Automation action routes create and maintain flow nodes such as sending SMS/email/WhatsApp, updating customer data, creating a mission, IF branching, AI agent, API call, start flow, or stop automation.
• Action parameters depend on the selected type. Common fields are parameter, text, subject, extra_param, delay, run conditions, and position_and_connection for visual builders.
• Activating or disabling an action controls whether that node executes when the parent trigger runs.

Safety

• Only account users with automation/settings permission should manage automations.
• The UI should show validation errors before saving and should not send unknown action parameters.
• Use User.Basic to load folders, statuses, tags, team members, custom fields, templates, products, projects, and entry tabs for dropdowns.

Common Flow

• Load User.Basic to check automation/settings permissions.
• List existing events with AutomationEvents.List.
• Add or edit an event trigger with AutomationEvents.Add/Edit.
• List existing action steps with AutomationActions.List and group them by flow_id.
• Add or edit action steps with AutomationActions.Add/Edit.
• Activate only after required trigger and action fields are complete.
• Listen for socket events like automationevents.add.created and automationactions.edit.updated to refresh open builders.

Routes In This Category