What is the SendSeven Flow Builder?
The SendSeven Flow Builder is a visual drag-and-drop editor for multi-step customer journeys. Teams build flows without code: from scratch, from a ready-made template or with the AI generator. Building blocks cover messages and approved WhatsApp templates sent straight from a flow, WhatsApp Flow forms, an AI assistant step, API calls to external systems and the hand-off to your team. External systems can start a flow via Zapier, Make.com or n8n. From EUR 79/month (Professional).
Customer journeys.
Without code.
Visual drag-and-drop editor with connected building blocks. So intuitive that your marketing team builds multi-step customer journeys across every channel. No developers. No Zapier. No compromise.
Three levers for real customer journeys
One trigger turns into a story: if-then branching, waits, collected answers, all across the channels your customer actually reads. Without anyone writing code.
6 channels in one flow
A flow starts on WhatsApp, follows up by email 24 hours later, sends an SMS if there's no reaction. Your customer doesn't notice it's a flow. They just notice that someone is paying attention.
Automated where it helps. Personal where it counts.
The "Run AI Assistant" block handles routine questions automatically. When it can't help or the customer asks for a person, it hands off cleanly to a human agent, with full context. Your team focuses on the cases where a person is actually needed.
Live funnel, not guesswork
Every step shows how many contacts pass through and how many drop. Drop-off on step 4? You see it instantly and fix the flow without redeploying.
Multi-channel cascade in one flow
Welcome on WhatsApp. 24 hours later, an email with the right products. If they click: a WhatsApp nudge to checkout. If they don't: an SMS that the discount expires tomorrow. One customer journey, three channels, one story. Your team builds it in a morning, and the flows run 24/7.
- Welcome sequences, cart recovery, win-back of inactive customers, birthday campaigns, NPS surveys: all in one tool
- Branches by click, reply, tag or contact field: every customer gets only what fits them
- Pinpoint waits from seconds to days; the flow holds until the moment is right
- Triggers your way: an API call from your shop, a keyword in an inbound message, a new or updated contact, a schedule, or a closed conversation for post-ticket surveys and NPS asks
Building blocks for every step, from simple sends to AI hand-offs
Send. Send a template, even outside the 24-hour window. Send a WhatsApp Flow. Wait. Branch. Choice by tap. Tag. Hand off to a human. Collect a reply. Generate a tracked link. Call an external API. Run your own code. Start another flow. Update a field in HubSpot. End the flow. Run an AI Assistant with clear handoff rules. Query your Knowledge Base. Send an email, whatever channel the flow runs on. Combined, they become a welcome sequence, cart recovery, reactivation campaign, birthday flow, NPS survey, lead qualifier, or an automated first response that hands off cleanly to your team when a real issue comes up.
- Send Template: approved WhatsApp templates straight from the flow, with an automatic path per quick-reply button plus fallback and timeout. Works even outside the 24-hour window
- Send Email: drop a real email into any flow, even one running on Instagram or Messenger. Collect an address mid-flow and send the confirmation at the end, no channel switch needed
- Rich media in the Send block: image or video together with buttons, WhatsApp buttons and lists with header and footer, quick replies on Telegram, Messenger, and Instagram
- Collect Input turns into a small chatbot: ask for first name, preferred slot, satisfaction score, straight in the flow
- Free-text routing without buttons: the contains-any-of operator routes replies like "no, nope, not interested" down the right path, regardless of casing
- Run AI Assistant: automate routine questions, hand off cleanly when the assistant can't help or the customer asks for a person. Separate outputs for completed, timeout and escalated
- KB Query fetches a short answer straight from your Knowledge Base, no full dialog mode. Perfect for standard questions
- API Call pulls data from your shop or CRM and pushes flow results back, with one path for success and one for errors. API keys stay encrypted. No double data entry
- Custom Code runs your own JavaScript in a sandbox, Start Flow hands over to another flow and picks up its result, and the HubSpot block writes answers straight to the contact's HubSpot record
- Send WhatsApp Flow opens a form right inside WhatsApp. If a message can't be delivered, for example to a landline that isn't on WhatsApp, a separate path tries the next channel
- Every node carries a name you choose, and every edge has a jump-to-node picker. Big flows stay readable, even three months later
Funnel per stage, replay per contact
The Observe tab shows every step as a funnel stage: entered, currently waiting, completed runs at a glance. Below it, the per-contact flow recording: full audit trail with millisecond precision, every message, every reply, every system step. Compliance buyers love it.
- Drop-off rate between any two stages; find the weak spot in seconds
- Channel performance: Sent, Delivered, Opened, Replied per channel
- Replay timeline per contact with millisecond precision (GDPR-compliant audit trail)
- Stop button cancels active runs for individual contacts, without restart
- Replay shows each node by its own name, not an ID, with the actual result it produced
- A variable timeline shows what every variable was set to, step by step
- Secrets and API tokens are masked automatically in every replay
GDPR-compliant drip sequences
Opt-out has to be frictionless, otherwise a customer becomes a complaint. 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. Zero effort for your team.
- Repeat triggers handled cleanly: Block, Restart, or Run in parallel
- Customer replies mid-flow? Either keep going or stop and hand off to a human agent
- Opt-out keyword detection on SMS and WhatsApp, confirmation message optional
- One-click opt-out via {{flow.stop_url}}: drop into any message, audit-safe
From trigger to live flow in 3 steps
No sandbox mode, no compile step. Publishing means: from now on, contacts flow through. No waiting.
Pick the trigger
API call for integrations, a keyword or any inbound message, a new or changed contact, or a schedule via the Scheduler (birthdays, weekly sequences). Every trigger can follow your business hours.
Connect the building blocks
Click the plus button, choose a block, fill it in. Move blocks freely via drag and drop, and reset to auto-layout anytime. Branch, wait, send. Done.
Publish and observe
The Observe tab shows from second one how contacts flow through. Spot drop-offs, adjust steps, no restart needed.
Frequently asked questions
What triggers does the Flow Builder support?
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.
Do I need developers to build a flow?
No. The Flow Builder is a visual drag-and-drop editor with pre-built building blocks. Pick a block from the menu, connect it to the flow, drag it where you want it, 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.
How many channels can I combine in one flow?
How does GDPR compliance work for drip sequences?
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.
What happens if a contact replies during the flow?
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.
What happens if the same contact gets triggered twice?
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.
Is the Flow Builder available on every plan?
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.
Can I start flows via API?
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. See the API documentation for details.
Can I send approved WhatsApp templates in a flow?
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.
Can a flow react to free-text replies, without buttons?
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.
More revenue. Loyal customers. Less effort.
Customer journeys, finally without code. Your marketing team builds welcome sequences, cart recovery, and reactivation flows themselves, across every channel. Your service takes over the moment a customer replies. That's how automated journeys feel when they're built right.