Automations
Boty Leads automations are “when this happens, do that” rules that run part of the follow-up for you. They’re managed at /admin/automations and require the manager or owner role.
How a rule works
Section titled “How a rule works”Each rule has a trigger (what activates it) and an action (what it does). Actions that send WhatsApp respect Meta’s 24-hour window.
What’s available today
Section titled “What’s available today”Boty is building this engine in phases. So you can document and promote it without surprises, here’s what actually runs right now:
The trigger that works
Section titled “The trigger that works”- Stage change — fires when a lead moves from one pipeline stage to another. You can scope it to a specific source and/or destination stage.
The actions that run
Section titled “The actions that run”When the stage-change trigger is met, these actions work:
- Change stage — moves the lead to another pipeline stage. It’s the simplest and most reliable action, with no external dependencies.
- Send WhatsApp template — sends an approved WhatsApp template, respecting the 24-hour window. Requires WhatsApp to be configured (see below).
- Send webhook — makes a signed call to one of your
https://URLs (for example, your CRM or an n8n/Zapier flow), to integrate Boty with other tools.
Requirements for it to run
Section titled “Requirements for it to run”- Send WhatsApp template only really delivers if WhatsApp is configured (see Capturing leads). Without that setup, the action completes but does not send the message.
- Send webhook only accepts secure
https://destinations and signs the request so your system can verify it comes from Boty.
Practical recommendation
Section titled “Practical recommendation”To start with something that works end to end, create a rule with the stage change trigger and the change stage or send webhook action. These are the most solid combinations today and let you see the engine in action without depending on external setup.
Última verificación: