Funnalized
DEENTell me when it starts
Module 14 · Automations

One trigger — the rest runs by itself

Drag a trigger, hang conditions and actions on it — and the routine runs, across module boundaries too.

0Capabilities
0Paths through
0Handovers
0Entries in the catalogue

Screens from a demo workspace. Companies, people and figures are fictitious.

What it does

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.

The load-bearing capability

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.

A real document number

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.

Over 100 triggers

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 someone unsubscribes via the link in the email. Contact blocks and consent are a hard boundary here: anyone marked “do not contact” cannot even be enrolled.

Exits on its own

as soon as the goal is reached or someone unsubscribes

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.

Four eyes

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.

1 builder

for sales, recruiting and projects — learn it once, use it everywhere

Handovers

What Automations receives and passes on

Comes in to Automations
Automations
Goes out of Automations

Automations carries what happens without anyone acting — trigger, condition, action. The individual message that goes out belongs to Email.

Complete

Everything that is in it

0Entries in the catalogue

50 capabilities in 8 groups — complete, not curated.

Honestly

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.

Follow-up

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.

All 50 entries as a list

The canvas 8

  • 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.
  • Conditions and branches If-then right in the flow: a condition block splits the path into yes and no, a branch block into any number of named paths with their own rules. Comparisons work the way you compare things day to day — equals, contains, greater than, between, days since, is today — and every single action can additionally carry a condition of its own.
  • Waiting until the moment is right Between two steps you let minutes, hours, days or weeks pass. The waiting step reports back at the right time all by itself — and exactly once, even if the app restarts in the meantime. Following up at a sensible interval instead of by the second.
  • Blocks for trigger, condition, branch, waiting time, action and end
  • Connect, branch and rebuild by drag and drop
  • Check on saving — a broken flow does not go live
  • Does the trigger fit the action? The app says so while you build As you put it together, the app checks whether the chosen trigger can reach the action at all: directly, only through a chain of links, or not at all. You find out while building, not from a run that never happens.
  • If something is missing, it says what Instead of “please check your input” the app names the action and the field — “Create task: title missing” — and one click jumps right there. Only what can be seen in the chosen case at all is required. A half-configured automation you can still save, as inactive; it is switched on only once everything is complete.

Triggers for every moment 6

  • 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.
  • One result sets off the next A won deal creates the project. A signed contract provisions the portal access. A lead becomes a deal. The modules work for each other — up to three levels deep, and then it stops: so that nothing goes round in circles and nothing happens twice.
  • Leads, deals, customers, contacts and companies
  • Quotes, invoices, contracts, orders and payments
  • Appointments, tasks, email events, forms and schedules
  • Satisfaction responses, approvals and stage rule transitions

Actions with real effect 6

  • 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.
  • Communicate: send an email, notify, send a survey
  • Create: task, appointment, deal, customer, quote, invoice, project
  • Steer: change stage, assign ownership, set a label, request approval, count a counter up or down
  • Connect: start a sequence, apply a stage rule, call another system by webhook
  • A document sent by an automation or sequence carries its PDF as an attachment; if it cannot be produced, the email does not go out without it, and the run names the reason

Sequences, stage rules and approvals 8

  • 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 someone unsubscribes via the link in the email. Contact blocks and consent are a hard boundary here: anyone marked “do not contact” cannot even be enrolled.
  • Stage rules — guided processes A stage rule carries a record step by step through fixed stations — with a checklist at each transition, a mandatory note and actions at every change. Whether by the press of a button or by drag and drop on the board: the same rules apply. No station gets skipped, and nobody quietly slides a card back.
  • 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.
  • Sequences: exit on a booked meeting, a created deal or an unsubscribe; contact block as a hard boundary
  • Stage rules: checklist at the transition, mandatory note, and only the responsible role moves it on
  • Approvals: request and decision sit with different people
  • Who is currently in which sequence you see across the workspace or for one specific lead, deal or contact
  • A single enrolment you remove with a reason — and a paused one you resume deliberately

Satisfaction and clean data 4

  • Satisfaction and clean data Customer satisfaction belongs to the same automation — NPS, CSAT, CES — asked after a won deal, after the invoice or after onboarding, without anyone having to remember it. Whoever is happy gets pointed towards a public review or a testimonial; whoever is not stands out immediately. In parallel, data quality keeps the base clean: merge duplicate records, change many entries in one go, handle access and erasure requests under GDPR.
  • NPS/CSAT/CES start automatically and then sit in the customer profile
  • Satisfied customers to review links, testimonials only after internal approval
  • Merge duplicate entries, change many entries at once, GDPR access and erasure

Safe, honest, traceable 5

  • Log with result, duration and the reason for skipping
  • GDPR boundary in delivery — a blocked email is skipped for good, not attempted again later
  • AI and chat connections honestly marked “coming soon”; what is active today is the secured webhook
  • Every run in the workspace on one list, filtered by sales, recruiting or projects if you like
  • Per automation the number of runs and the success rate; per sequence also the open and click rate for each step

Connecting your own systems 4

  • Webhooks you can verify You send events from Funnalized to your own systems — new targets with an https address only, every delivery signed and with a delivery ID of its own so the receiver can spot retries. If one fails, the app tries again. The log shows state, attempt and next retry for every delivery, and you send a test with one click.
  • API keys that may only do what you allow For your own integration you create keys with read and write rights per data type, optionally with an expiry date. Revoking takes effect immediately. When you create one, the base address, an example call with exactly this key and the interface description (OpenAPI) sit right beside it.
  • You see a webhook’s secret exactly once, it is stored encrypted — and you can renew it at any time
  • Incoming webhooks accept data from other systems, checked against a secret of their own

What you build yourself — and what is already there 9

  • More than a hundred ready-made automations to take over A searchable library, filtered by category: you take a finished automation with one click instead of starting on an empty canvas — and change it afterwards like one of your own.
  • Name the stations of a stage rule freely A process need not stick to existing pipeline stages. You build it out of stations you name yourself, give them a colour and an order, and set which is the start and which the end.
  • Transitions with required fields and rules of your own For every single transition you decide which fields must be filled, which value rules apply — with your own error message — and which preconditions must hold before it is offered at all.
  • Checklist items that check themselves Beside the tick by hand there are items the app checks against real data: whether a scorecard has been submitted, whether interview feedback with a rating exists, whether an assessment has been passed. What can be proven need not be asserted.
  • An approval holds the transition A transition can wait until somebody has decided. Who decides is read by the app from a field on the record itself — you do not enter the same person for every case.
  • Sequence steps that do more than email A step can create a quote or an invoice and send it — two separate steps, so that creating never quietly means sending. For SMS, LinkedIn and WhatsApp the app instead creates a task that is due, carries the message text and is assigned to a person.
  • Recruiting sequences branch on the result of an assessment: passed moves on to the stage you chose, not passed takes the other route
  • Hand out ownership in turn or to whoever has the least load, instead of always naming the same person
  • An automation or sequence you switch off without deleting it — and back on the same way
The neighbours

The module before, the module after

All 21 sit in a fixed order — from here it continues in both directions.

Automations is module 14 of 21 — the same order as in the menu and the footer.

One message at launch. After that you'll find me in the top right of the app.

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

Waiting list

Only your email address. No spam, unsubscribe at any time.

See all modules

€50€150/ month · permanently

50 founder placesTell me when it starts