Skip to content

Creating an automation ​

Every automation is built from three blocks, always in the same order:

  1. When it runs — the event that calls the automation;
  2. Only if — the conditions that must be met (optional);
  3. What it does — the actions that run, in order, one after another.

This guide walks through the full creation, including the Dry run — the test mode that runs everything in simulation before you activate it.

Before you start ​

  • Be clear about which event should fire the automation — see them all in the Automations reference;
  • If one of the actions is Start playbook, have the playbook already created.

Step 1 — Create the automation ​

On the Automations screen, click + New automation. Set the Name and, if you want, a Description — it shows in the list and helps the team understand what the automation does.

Step 2 — When it runs ​

Pick the Event that calls the automation. Events are split into three groups — Pipeline, Contact and Conversation — and each one opens its own configuration fields right below.

For example, on the Opportunity entered a stage event:

  • Pipeline — which pipeline the automation applies to;
  • Into stage — the stage that fires it. Leave it empty to match any stage;
  • Only once per deal — with this on, a card that comes back to the same stage does not run again. Off, the automation runs every time the opportunity enters the stage.

📚 Each event has its own fields — the full list, with each one's settings, is in the Automations reference.

PRINT AQUI #1

"When it runs" block of the automation editor, with the event picker and the configuration fields of the chosen event.

Step 3 — Only if (conditions) ​

With no condition, the automation runs every time it is called by the event. To refine it, add conditions and pick the mode:

  • All conditions — works as an AND: all of them must be true;
  • Any of them — works as an OR: one being true is enough.

Example: with the conditions tag has "active customer" and sector is "General":

  • In All conditions, the automation only runs for contacts that have the tag and are in the General sector;
  • In Any of them, it runs for whoever meets either of the two.

Click + Add condition to include as many as you need. The available fields include contact, opportunity and conversation data, the previous stage and all your custom fields — see the full list in the Reference.

PRINT AQUI #2

"Only if" block of the editor, with the All conditions / Any of them selector and the added conditions.

Step 4 — What it does (actions) ​

Add the actions the automation will run. They run in order, one after another — and you can reorder them with the arrows or delete them with the trash icon.

Click + Add action and pick from the catalog, organized in groups: Assignment, Contact, Deal, Conversation, Tasks and team, Timing and Integrations.

💡 Control the pace: the Wait action (Timing group) pauses the sequence for as many minutes as you set before running the next action — useful to leave a gap between a message and the following action, for example.

PRINT AQUI #3

Action catalog open, with the Assignment, Contact, Deal, Conversation, Tasks and team, Timing and Integrations groups.

Step 5 — Test with the Dry run ​

Before activating, click the Dry run 🧪 icon (at the top of the screen). The Dry run executes all conditions and actions in simulation, without saving anything:

  1. Search and pick a contact for the test;
  2. Click Run a dry run;
  3. See how the automation would behave for that contact.

⚠️ In the Dry run, the HTTP Request action is not actually sent. To call the real API, use the Test request button inside the action itself.

PRINT AQUI #4

Dry run window, with the contact search and the simulation result condition by condition.

Step 6 — Save and activate ​

Click Save and check the Active toggle at the top. You can pause and reactivate the automation at any time — from the editor or straight from the toggle in the list.


How to know it worked ​

  • The automation shows in the list with the active status;
  • As the event happens, the runs show up in the Runs tab, with result and duration.

Common problems ​

The automation "did not work"

Open the Runs tab and look for the run: in most cases it did run, but it was skipped because the conditions did not match for that contact. Expand the result to see the reason.

The automation runs again every time the card comes back to the stage

That is the default behavior. To run only the first time, turn on Only once per deal in the When it runs block.

The "stuck in a stage for N days" event did not fire at the exact time

This event is checked every hour — it fires on the first check after the period is complete, not at the exact minute.


Next steps ​

  • Check every trigger, condition and action in the Automations reference;
  • Follow the results in the Runs tab;
  • Combine it with Playbooks: the Start playbook action creates your process's tasks automatically.

GetRaze - AI-Powered Lead Generation