Automations in Revamp365 run a sequence of actions automatically whenever an event fires on a contact or deal — for example, texting a lead the moment their status changes. Every automation is built from one trigger, optional filter conditions, and one or more action steps.
Open the automations builder
The builder lives on the Automations page (the engine is a paid feature on Pro+ and Dealmaker plans, and your phone number must be verified to reach it).
- Go to Automations in the app. The page opens on the Automations tab, with a Logs tab beside it.
- Click + Create automation in the top right. A full-screen builder opens titled "Create automation."
- If you have no automations yet, the empty state also shows featured templates — click Use template on one to pre-fill the builder instead of starting blank.
Understand the trigger, condition, action model
The builder uses a left rail with three kinds of steps:
| Stage | What it does |
|---|---|
| Trigger | The single event that starts the automation (for example, Contact created or Lead status changed). |
| Filter | Optional conditions — the automation only continues when the record matches your AND/OR rules. |
| Step 1…N | The actions that run in order, such as Send SMS, Create task, or Wait. |
Build the automation
- On the Trigger tab, enter an Automation name (for example, "Hot lead instant SMS").
- Pick a Trigger event. Triggers are grouped by Contact, Deal, Call, SMS, AI Agents, Email, Booking, and Schedule / Time. Some triggers add their own settings — Inbound SMS keyword matched, for instance, asks for keywords and a match type.
- Choose a Re-enrollment policy: Once per record (default), Every time the trigger fires, or Cooldown with a minimum wait in minutes.
- (Optional) On the Filter tab, click Add filter to require conditions like
lead_status equals Hotbefore the steps run. Leave it empty to run on every trigger match.
- On Step 1, choose a Step type from the grouped action list (Communications, Contact data, Tasks / Notes / Tags / Lists, Deals, Flow control, AI Agents, and more), then fill in its fields. Message bodies support variables like
{{ contact.first_name }}.
- Click Add step to chain more actions. Use the Wait action under Flow control to space steps out. You can add up to 25 steps.
- Click Save.
Tip: turn on Dry run on the Trigger tab to record what each step would do without actually sending — useful for testing before you go live.
Turn the automation on
New automations save as Draft, so nothing fires until you enable them.
- On the Automations list, flip the On / Off switch in the automation's row to activate it (its status changes to Active).
- Or use the row's actions menu and choose Activate.
Statuses are Draft, Active, Paused, and Archived. You can keep up to 50 automations active at once. To stop one temporarily, flip the switch off (it moves to Paused) without losing the configuration.
Once it is active, watch executions on the Logs tab. See read automation run logs and fix failures for how to read enrollments and step runs and retry failures.