Automation & omni-channel scenarios

Build the funnel once. It runs on every channel you use.

One visual graph handles the trigger, the wait, the condition and the reply, in the DM, the inbox or the comment thread. 139 node types, one canvas.

Start free

A comment thread with an automatic public reply, the direct message that followed it, and the AXL scenario canvas that produced both.
Automation at a glance

Start with an event. Let the scenario finish the follow-up.

Connect triggers, waits, conditions and actions on a visual canvas. One contact moves through one run, and every node records what happened.

A scenario open on the AXL canvas: three trigger chains with an execution counter on every node, a green Condition branch, and one selected node with its configuration panel open beside it.
A drawn product still of the scenario canvas, node counters and an open configuration panel.
  • Trigger. Start from an order, form, comment, renewal, lesson, webinar or account event.
  • Wait and decide. Pause for time or behaviour, then branch on the same conditions used in CRM segments.
  • Act. Send on nine channels, grant access, move a deal, create a task or call a webhook.
  • Inspect. See execution counters, retry failed webhooks and branch on their response.
See scenario rules and channel limits

Build and configure the graph before one switch activates it. Nodes copy between scenarios, and a listener can hold a run until a purchase, payment, page visit or quiz answer arrives.

Current limits: Facebook comment automation still depends on two Meta permissions in review. SMS uses your own provider, and email can remain the final fallback after messenger channels.

Do this in 10 minutes

Turn Instagram comments into DMs and leads.

  1. 01 Connect Instagram Then a scenario on it, switched off. A channel holds many, each with its own switch. Settings → Channels
  2. 02 Keywords, then four replies “Guide please!!” matches guide. One reply is picked at random. Settings → Scenarios → the canvas
  3. 03 Send the DM with a button The button is what puts two branches on the node. Canvas → Send message
  4. 04 Ask for the email, or wait The answer writes into the field. Tag both branches. Canvas → Ask contact for data
  5. 05 Flip it, test from another account Run counters and a per-contact log answer “did it fire?”. Settings → Scenarios → Runs

The same five steps, as one prompt

“Create a scenario on my Instagram channel. Trigger: a comment matching guide, link or send on the posts tagged ‘lead magnet’. Post one of four replies at random, then DM that person the link with a button. If they press it, ask for their email; if not, follow up tomorrow.”

An agent can build the whole graph; the sign-in and the activation switch stay yours. What an agent can finish here →

A scenario open on the AXL canvas: three trigger chains with an execution counter on every node, a green Condition branch, and one selected node with its configuration panel open beside it.
How it connects

Scenarios are the wiring between everything else.

Where events come from, and what the graph does back.
Module It hears It does
CRM & payments Order created or paid, renewal paid or failed, deal moved Create the deal, add the payment, reassign it, pause the subscription
Website & funnels Form submitted, quiz completed, page visited, custom events Attach a scenario to one page or form
Email & broadcasts Email opened or clicked, from an email this run sent Run the sequence over email and messenger, on the same segment
Courses & LMS Course started, lesson completed, homework submitted Grant or revoke access, issue the certificate, award points
Webinars & video Registered, finished, a timer at any offset, a chat keyword Register someone, then split follow-up by who stayed for the offer
Community Member joined, badge earned Tag them, message them, open the space the badge unlocked
Questions

Questions people actually ask.

Yes, through the same node as Telegram or WhatsApp. Two caveats: you connect your own Twilio or RingCentral account because AXL is not the SMS vendor and does not resell numbers; that provider bills you per message on top of your AXL bill.

Yes. The trigger watches every post or a named list you pick, and each keyword matches by equals or contains, ignoring case by default.

Yes. Pick a saved segment and run the scenario as a bulk action, or start it from one contact card. Same graph, started by you instead of by an event.

Outbound webhooks with custom methods and headers, retries across 24 hours, and the response stored for later conditions. Inbound, a POST or GET starts any active scenario and matches the contact from the payload, under an API key you can scope to running scenarios and nothing else. The run endpoint →

Answer everyone, on the channel they used, in under a minute.

Draw the graph once and it runs on Instagram, WhatsApp, Telegram, email and your CRM at the same time. Plans start at $49 a month, with included usage and published overage rates.

Start free · Automation guides · Email and analytics guides