Automations & AI Guide
Build automated workflows and leverage AI to scale your operations.
Understanding the Workflow Builder
The automation builder is a visual node-based editor. Workflows start with a trigger node (what starts the automation), followed by action nodes (what happens), and optional condition nodes (branching logic). Nodes are connected by dragging from output ports to input ports. Each workflow runs in sequence — when a node completes, the next connected node executes.
Note: Access the builder under Automations. The node palette is organised into categories: Triggers, Actions, Conditions, AI, and Templates.
Trigger Nodes
Triggers are the starting point of every workflow. Available triggers include: Lead Created, Lead Stage Changed, Deal Won, Deal Lost, Form Submitted, Website Published, Scheduled Time, and Webhook Received. When a trigger fires, it passes context data (like the lead ID or deal value) to the next node in the workflow.
Note: Triggers are defined in the node definitions library and execute via the automation runner service.
AI Nodes
Marqly includes several AI-powered nodes. The AI Lead Scoring node analyses lead data and returns a score (1-100), confidence level, and scoring factors. The AI Message Generation node creates personalised email or SMS content based on context. The AI Form Generation node builds form fields based on a description. These nodes use the AI engine which supports multiple LLM providers.
Note: AI nodes are under the AI category in the node palette. The AI engine routes requests through the configured provider.
Conditions & Branching
Condition nodes let you create branching logic. For example: IF lead value > 10000 THEN send to high-value pipeline ELSE send to standard pipeline. Conditions can check lead properties, deal values, form responses, or custom fields. You can chain multiple conditions to create complex decision trees.
Note: The Condition node type supports comparison operators: equals, not equals, greater than, less than, contains.
Scheduling & Execution
Workflows can run immediately when triggered, or on a schedule (cron-based). Scheduled workflows are checked every minute by the cron scheduler. Execution logs show each node's status, input, and output — useful for debugging. Failed nodes can be retried manually from the logs view.
Note: The cron scheduler at /api/cron/email-scheduler checks for pending scheduled automations every minute.