All guides

Automation builder

If this happens, then do that — scenarios like Make.com or IFTTT, built into Dezvo.

Everyone builds their own scenarios; owners and admins see and change all of them.

1 Start

  1. Automation builder → pick a recipe (e.g. New lead → Slack) and press Use this, or start a blank scenario.
  2. A scenario is off until you switch it on — build and test it first.

2 Build

  1. Bubble 1 is the trigger: something happening in Dezvo (a new lead, a won deal, a paid invoice…), a schedule (every 15 minutes up to weekly, in your workspace's time), your own web address (forms and other apps post to it), or only when you press Run.
  2. Press + to add the next step: Dezvo CRM (create or find leads, notes, tasks, deals, accounts), email, bell notices, Slack, SMS / WhatsApp, HTTP (any API), or tools (variables, text, numbers, dates, JSON, wait, stop).
  3. Click a bubble to fill it in. The {} button puts in data from earlier bubbles — {{1.email}} is the email from bubble 1, {{3.data.id}} the id an API gave back in bubble 3.

Each bubble keeps its number, so moving steps never breaks {{2.…}}.

Keep API keys under Keys and use them as {{secret.api_key}} — they're encrypted and shown as ••• in history.

3 Filters and routers

  1. The funnel on a line is a filter: the run only goes on when its checks pass. Checks in one box must all pass; Or… adds another box that may pass instead.
  2. A Router splits the run: every route whose filter passes runs, top to bottom — e.g. Known lead → add a note, New lead → create it.

4 Test, switch on, check

  1. Test runs it with the example data and changes nothing; Run once does it for real.
  2. Switch it on. History shows every run — what went into each step, what came out and what went wrong.
  3. If a step fails: stop (default), carry on, or try again twice — set on each bubble. When a run fails you get a bell notice.

Limits per run and per day are in Settings → Rules & limits → Automation builder.

5 What you can automate

A scenario acts as the person who made it: it can only use the events and steps your own access allows (for example, people who work only on their own leads get events and changes for their own leads), and it stops if your access changes or you leave the workspace. Owners and admins can use everything.

Questions people ask

Automation builder: what you can automate?
A scenario acts as the person who made it: it can only use the events and steps your own access allows (for example, people who work only on their own leads get events and changes for their own leads), and it stops if your access changes or you leave the workspace. Owners and admins can use everything.