Automations Overview

Automations are trigger-based rules that perform actions automatically when specific events occur in QuintaGo. They eliminate repetitive manual work — from sending a welcome message when a lead arrives, to moving a deal to a new stage when a proposal is signed.

Anatomy of an automation

Every automation has three parts:

• Trigger — the event that starts the automation
• Conditions — optional filters to narrow when it runs
• Actions — what happens when the trigger fires

Available triggers

• Lead created — fires when a new lead enters the system
• Stage changed — fires when a lead moves to a specific stage
• Proposal sent — fires when a proposal is delivered
• Proposal signed — fires when a lead signs the proposal
• No activity for X days — fires when a lead has not been touched
• Event date approaching — fires N days before the event date
• Message received — fires on inbound WhatsApp message
• Form submitted — fires on a specific form submission

Available actions

• Send a WhatsApp message (template or free-form)
• Send an email
• Move lead to a different pipeline stage
• Assign the lead to a team member
• Add or remove a tag
• Create a task with a due date
• Trigger a webhook
• Add a delay before the next action

Building your first automation

Go to Automations → New automation. A common starting point is an instant welcome message:

1. Trigger: Lead created
2. Condition: Source is Website form
3. Action: Send WhatsApp message → select your welcome template
4. Action: Assign to team member → round-robin

Automations run in real time. The welcome message typically arrives within 3 seconds of the lead being created.

Testing and monitoring

Each automation has a run log at Automations → Your automation → Runs. You can replay failed runs, inspect the trigger payload, and see exactly which action failed and why.