Automations lets you run a saved workflow when a schedule fires, a pipeline record changes, or a campaign enrollment replies, bounces, or exits. You can also start one by hand on an email or a deal. The builder is a full page under Automations in the sidebar. You add a trigger and at least one step, save a version, and turn the automation on.
Create an automation
- Open the list — Select Automations in the sidebar, then New automation.
- Start the automation — In Create a new automation, describe the workflow under Build with Lev Agent, choose Start from scratch, or pick a template. Categories are Suggested, Email, Pipeline, Campaign, and Scheduled.
- Name it — A from-scratch automation opens as Untitled automation. Edit the name in the builder header.
- Rename from the list — Choose Rename to open Rename automation.
- Archive it — Choose Archive on the row.
- Show archived rows — Turn on Show archived to see archived automations and restore one.
Choosing a template creates the automation with its trigger and steps in place. Finish the fields that are still open. A from-scratch canvas cannot be saved until a trigger and a step are in place.
Build the workflow
The canvas is the automation. A trigger decides when it runs, and each step is what it does.
- Add a trigger — Choose Add trigger, or Add a trigger on an empty canvas. A schedule uses Frequency (Hourly, Daily, Weekly, or Monthly), plus Day, Day of month, Time, and Timezone when that frequency needs them.
- Scope a reply or bounce — Point the trigger at a campaign.
- Scope an exit — An enrollment-exited trigger uses Any campaign or one campaign, and Any reason or a reason: Engaged, Exhausted, Declined, Bounced, Canceled, or Relaunched.
- Add a step — Choose Add step. Steps include Send a reply, Draft a reply, Enroll in a campaign, Update contact in pipeline, and Remove contact from pipeline.
- Add an agent or documents step — Agent steps hand work to a Lev agent, such as finding the deal in an email or screening a deal against your buy box. Documents steps work on a deal's files, such as indexing its documents. Which ones you see depends on the trigger.
- Set who writes a reply — On Written by for Draft a reply or Send a reply, choose Lev AI writes it or I write it myself. I write it myself offers variables on Subject and Message. Lev AI writes it uses Instructions for Lev AI. Draft a reply saves the message for you to send. Send a reply sends it.
- Watch an incompatible step — A step that cannot run under the selected trigger turns red and says why. The message says it is not available for that trigger.
- Match a message — On a trigger that supports it, use Read message for to describe what the message should match before the run starts.
- Turn it on — Choose Turn on. The control reads Live while that version is on, and Off when it is not. Turn it off with Turn off.
Pipeline triggers run when a record is added to a pipeline or updated in one. Schedule a Marketing status report from this builder.
Pass values between steps
A step's inputs can hold a fixed value or a value from earlier in the run.
- Choose where a value comes from — Open the input's picker. Choose Custom value or one of the input's fixed choices, a field under Trigger, or an output listed under an earlier step's name.
- Read a linked input — On the canvas, the step card names the output and the step it comes from.
- Fix a link to a later step — If you move or delete the step an input reads from, the card shows Needs: Earlier step. Choose a step that runs first. The automation cannot be saved until you do.
Agent and documents step inputs can take a trigger field. Pipeline, status, campaign, and other record inputs take a fixed value or an earlier step's output.
Split into paths
A Path step sends the run down one of several paths, based on conditions. Each path has its own steps.
- Add a Path — In the step list, choose Split into paths. It starts with one path that has conditions and an Otherwise path.
- Add more paths — Select the Path step and choose Add path. Lev checks paths from first to last and runs the first one that matches. Later paths are skipped.
- Set a path's conditions — Open the path and choose Add condition. Pick a trigger field or an earlier step's output, then an operator and a value. An output with a fixed set of values is picked from a list.
- Join the conditions — Choose Match all to require every condition, or Match any to require at least one.
- Set the fallback — Otherwise runs when no other path matches, and it takes no conditions. Only the last path can be the otherwise path. Switch it with Make otherwise or Add conditions in that path's "…" menu. Without an otherwise path, the run ends when nothing matches.
- Add steps to a path — Choose Add step inside the path.
- Nest a Path — Add a Path inside a path. Paths nest up to three levels deep.
Adding a Path between two steps moves the steps after it into its first path. Schedule triggers don't offer Paths. If you don't see Split into paths under another trigger, it isn't available on your workspace yet.
Request a missing trigger or step
Tell Lev about a trigger, step, or whole workflow the builder doesn't offer yet.
- Open a request — At the bottom of the trigger or step list, choose Missing a trigger? or Missing a step?.
- Say what's missing — Under What is missing?, choose Trigger, Step, or Full workflow. The dialog title follows your choice: Request a trigger, Request a step, or Request a workflow.
- Describe it — Fill in What do you need?. Anything close that already exists shows under This might already exist, with a button to use it instead. Choose None of these to keep going.
- Submit it — Fill in When should this happen?, then choose Submit request.
- Request from Build with AI — When Build with AI can't build a piece, the chat asks whether to send it to Lev as a request. Choose Send a request to open the same dialog with your description filled in.
Nothing is sent until you choose Submit request. Lev reviews every request, and submitting one doesn't mean it will be built.
Build with AI
Build with AI drafts the workflow from a description, on the builder page.
- Describe the workflow — In Create a new automation, write the description under Build with Lev Agent and send it. The builder opens with that prompt.
- Revise on the canvas — Choose Build with AI in the builder header to generate or adjust the trigger and steps.
- Review before you turn it on — Check the trigger and each step, then save. Nothing runs until the automation is Live.
Run an automation manually
A manual automation runs when you start it on an email or a deal. You run it from Inbox, a deal page, or a pipeline.
- Build a manual automation — Choose Add trigger, then a trigger under Run manually. An email trigger runs on an Inbox thread. A deal trigger runs on a deal.
- Run it on an email — In Inbox, open a thread or hover its row, then choose Automations.
- Pick the automation — The picker lists the manual automations for that email or deal. Select one, then choose Run automation. Create automation opens a new automation in the builder with that trigger in place.
- Run it on several emails — Hover a row's avatar and check the box that replaces it. Check up to 25 emails, then choose Run automation in the bar at the bottom of the page. Each email gets its own run.
- Run it on a deal — On the deal page, choose Automations beside the deal name.
- Run it from a pipeline — Hover a deal row on a pipeline or All deals, then choose Automations beside the "…" menu.
- Open the run — A message confirms the run started. Choose View run to open it in run history, or View runs after a bulk run.
Only deal editors can run an automation on a deal. If credits run out during a bulk run, the remaining emails don't start and stay checked, so you can retry them.
Versions
Version history is the list of saved versions. Promoting a version is what makes it the live one.
- Open version history — In the builder header, choose Version history.
- Promote a saved version — When the version differs from the live one and you have no unsaved edits, choose Promote.
- Save edits onto the live version — Choose Save and promote to save the canvas and make that version live.
- Keep edits as a draft — Choose Save as draft when you want the changes stored without replacing the live version.
- Return to the canvas to change Live — While you are viewing history, turn the automation on or off from the canvas.
An automation saves only when you save it. Save and promote and Save as draft are the save actions.
Run history
Run history lists past runs and the steps each run took.
- Open run history — In the builder header, choose Run history.
- Filter by status — A run can be Succeeded, Failed, Running, or Skipped.
- Read a Path — When the run took a Path branch, run history shows that branch and its steps. The other branches are left out.