Customer journeys.Without code.

Manual API call for integrations from your own systems or tools like Zapier, Make, or n8n. Keyword trigger for inbound messages (the old Autoresponder concept, now with a Start-Flow action), or simply any incoming message. Conversation opened, assigned, or closed: closed covers post-ticket surveys, NPS asks, or auto-tagging after a service interaction. Contact created, updated, subscribed, or unsubscribed, filterable by source, changed field, or tag, for example only contacts synced from HubSpot. Schedule via the Scheduler for birthdays, RRULE recurrences, and segment sends. Comment received: a comment on your Instagram or Facebook post starts a comment-to-DM automation. Came from an ad: when a contact messages you from a Click-to-WhatsApp, Click-to-Messenger, or Click-to-Instagram ad, the flow starts automatically, matched to any ad or a specific one. And WhatsApp Flow completed: as soon as a customer submits a WhatsApp form, the next flow starts. Every trigger can follow your business hours, running only inside or only outside them, and the ready-made absence message template answers after hours.

No. The Flow Builder is a visual editor with pre-built building blocks. Pick a block from the menu, connect it to the flow, configure the details. Or start from a ready-made template, or let the AI generator draft a flow from your description. Your marketing team builds welcome sequences, cart recovery, reactivation flows themselves. Code only comes in if you want it, for API calls to external systems or your own JavaScript.

All six send channels: WhatsApp, Email, SMS, Telegram, Messenger, and Instagram. A Send step can contain a sequence (for example, WhatsApp, then 5 seconds later Telegram as a fallback). Or you branch the flow with a condition based on which channel the contact actually has.

Per flow, you can enable opt-out keywords: if a contact replies STOP, UNSUBSCRIBE or CANCEL on SMS or WhatsApp (the globally established opt-out keywords), the flow ends for them instantly, optional confirmation message included. There's also the {{flow.stop_url}} variable for any message: a click cancels the flow without further input. Audit-safe and traceable.

You pick one of two modes per flow. Continue the flow: replies open a normal conversation, the flow continues in parallel. Best for drip campaigns. Stop the flow: the reply cancels the flow and hands the conversation off to a human agent in the Unified Inbox. Best for guided conversations.

Three re-entry policies are available. Block ignores the second trigger if the first is still running. Restart cancels the old run and starts a new one. Parallel runs both at the same time. Default is Block, the safest option for most use cases.

The Flow Builder is included from Professional (€79/month) through Scale and Enterprise. It isn't part of Basic (€49/month, no automation) or API Only. See plan details.

Yes. POST /flows/{id}/runs starts a flow for any contact from your own systems. Perfect for shop events (order completed, cart abandoned), CRM triggers, or custom integrations. The API also reads, creates and updates the flows themselves as JSON. See the API documentation for details.

Yes, with the "Send Template" block. Pick an approved message template and the flow auto-generates a separate path per quick-reply button (up to 3), plus a fallback path (the customer types instead of tapping) and a timeout path. Because a real template is sent, delivery works even outside the 24-hour window, reliable for win-back and drip sequences. Buttons are translated automatically for Telegram, Messenger, Instagram, SMS, and email, so your branches behave the same on every channel. No approved template yet? The free WhatsApp Template Generator validates your draft before submission.

Yes. The "Last reply text" flow variable automatically holds the contact's most recent reply, no contact field needed. Conditions and branches support the operators "is one of", "is not one of", and "contains any of": add keywords like "no, nope, not interested" and the flow routes matching replies down the right path, ignoring casing and extra spaces. Collect Input can also store its result in a flow variable instead of a contact field.

Yes. The flow format spec describes every step type, field and variable, and it starts with a ready-to-copy prompt for your AI tool. Paste the result into the JSON view: live checks show right away whether every step fits, and the canvas shows the flow as soon as you switch back. Inside the editor, the built-in AI Assistant does the same without copy and paste. AI edits in the editor use AI credits.

Yes, from Professional. The API reads, creates and updates flows as JSON, with the same checks as the editor. If a flow doesn't fit, the response lists the problem per step, so your script or AI tool knows exactly what to fix. Details in the API documentation and the flow format spec.

Yes, one at a time. Whoever is editing holds the flow; teammates see it read-only and can ask to edit or take over. That way nobody overwrites someone else's changes. Every save lands in the History with its author and source (canvas, JSON or AI Assistant). You see what changed in a diff and can restore an earlier version after a confirmation.