One trigger — the rest runs by itself
Drag a trigger, hang conditions and actions on it — and the routine runs, across module boundaries too.
Screens from a demo workspace. Companies, people and figures are fictitious.
Automations at work
Five capabilities people actually open Automations for. Everything else it can do is listed in full in section 04 — this is only what stands on its own.
Actions that really act
Most automation tools only send a notification: “please take care of this”. Here the order, the invoice or the contract really comes into being — with a real document number and correctly calculated tax, because the same calculation applies as for a document you create yourself. Assign ownership, change a stage, set a label, request an approval, call a connected system: the action does it, it does not just pretend to.
and tax worked out correctly — the automation genuinely creates the document
More than a hundred triggers — including the silent ones
Lead created, deal won, invoice paid, application received, contract signed, form submitted. And what does NOT happen fires too: no activity for days, a deal sitting too long in the same stage, an invoice overdue. Plus the schedule at a fixed time of day — in your workspace time zone. If the app was briefly unreachable, the missed run is caught up rather than quietly swallowed.
silent ones too: no activity for days, a deal sitting too long in its stage
Sequences — following up over weeks
Build follow-up programmes across days and weeks: email, waiting time, call task, next email. The sequence drops out by itself as soon as it has reached its goal — a meeting is booked, a deal is created, won or lost — and just as much when an email comes back undeliverable. Contact blocks and consent are a hard boundary here: anyone marked “do not contact” cannot even be enrolled.
as soon as the goal is reached or an email bounces back undeliverable
Four-eyes approvals
Sensitive actions — a quote above the amount you set, a bulk deletion, a role or permission change — only run after consent. Whoever requests does not decide; that holds for the owner too. Which role may decide you set per policy — and there you can also allow self-approval outright, if that is how your team works. Two cases are solved on purpose, so the policy never brings your work to a halt: if there is nobody else who could decide, the decision goes through and is recorded as a solo call. And if a policy ever points nowhere because its role was deleted, the owner can still decide.
whoever requests it does not decide it — that goes for the owner too
One builder for three modules
The same visual canvas for sales, recruiting and projects — learn to use it once and you can use it everywhere. Each module brings its own triggers and actions; the way you operate it stays the same. No zoo of island tools, no three different ways of working that in the end only one person in the company masters.
for sales, recruiting and projects — learn it once, use it everywhere
Paths that run through here
A trigger is not a schedule but an event on a record. That is why an automation reacts to what actually happened — not to the fact that it is Monday.
From a quote to an order
What Automations receives and passes on
Automations carries what happens without anyone acting — trigger, condition, action. The individual message that goes out belongs to Email.
Everything that is in it
44 capabilities in 7 groups — complete, not curated.
What it does not do
Every limit names the place where it happens instead.
- Not a Zapier.
Automations act INSIDE Funnalized. To trigger a foreign application you use the webhook — there is no catalogue of third-party services.
- No language model decides.
Conditions are rules you can read. What happened is in the run log — including the failure.
- Nothing runs in secret.
Every run is visible, and so is every failure. An automation that fails silently would be worse than none.
What teams want to know beforehand
Do I notice when an automation gets stuck?
Yes. The dashboard shows how many are running and how reliably — optionally only the failures. Automations work in the background; that is where you notice.
Can one automation trigger another?
Yes, and there is a brake against loops. One result triggers the next, but not itself.
What happens if someone withdraws mid-sequence?
The sequence stops — not at the next run, but immediately. Consent is checked before every send, not only at entry.
Automations is one of 21. You get all of them.
Sign up and you'll hear from us the moment we go live. Not a newsletter — one message.
€50€150/ month · permanently
Only your email address. No spam, unsubscribe at any time.