Automations
Put your agents on a schedule.
Anything you ask an agent for every week can run on its own: on time, in your timezone, pausing for you when a step needs a person, and reporting back when it is done.
Three kinds
From one recurring job to a goal over months.
One agent, on a schedule
"Every Monday at 8, summarise last week's pipeline and flag deals with no activity." A Task is one agent doing one job, repeatedly.
Several agents, in order
Steps hand results to each other: pull the numbers, reconcile, draft the journals, wait for approval, build the pack. Each step can use a different agent.
A goal, tracked over time
"Grow qualified pipeline 20% by December." Agents plan the work, run it in cycles and track the measure until the goal is met or the date arrives.
Triggers
On a clock, or when something happens.
- Schedules with their own timezone: weekdays at 7:00, the first of the month, every two hours.
- Record changes: when a supplier, case or deal is created or updated in Records.
- Webhooks and API calls from your other systems, each with its own secret.
- Follow-ups: an agent can schedule its own check-back, from two minutes to thirty days later, and report into the same chat.
Control
Runs you can steer and stop.
- Approval mid-run: a step that changes data waits for the right person, then the run carries on.
- Retry from the failed step, without repeating what already worked, and a full history of every run.
- Least privilege per step: limit a step to exact actions; anything else is refused when it runs.
- Bulk approvals and a kill switch that stops every running automation in the organisation at once.
Example
Daily email drafts: it can draft, never send.
Every weekday morning the Inbox Assistant reads the email that arrived overnight and, for each one that needs your answer, saves a reply in your Drafts folder, threaded and in your voice. You review and send.
- Only what it needs: the step may list mail, read it and save reply drafts. Sending is not among its actions.
- Email is data, never instructions: a message that asks it to forward or send something is reported, not obeyed.
- One draft per thread: run it twice and it does not duplicate. Placeholders mark anything only you can know.
Step: Draft replies to new email
Templates
Start from one that already works.
Install a template in a click, pick the time, and adjust the steps to fit how your team works.
Questions, answered.
Which plans include Automations?
Scheduled Tasks are on Pro (5 Tasks and 100 runs a month) and Pro Plus (15 Tasks and 500 runs). Multi-step Workflows and Objectives are on Pro Plus and Enterprise. Enterprise has no limits. See pricing.
What happens if a step needs my approval while I am away?
The run pauses at that step and waits. You get the approval in Renly on the web, in the Windows app or on your Android phone, and the run carries on as soon as you decide.
Can an automation send email on its own?
No. Sending email, posting messages, publishing and e-signature requests through a connector always wait for a person, in automations as in chat. Templates such as Daily email drafts save replies as drafts for you to send.
What if a step fails?
The run stops at the failed step and keeps everything before it. Retry from that step once the cause is fixed, without repeating the steps that already worked.
Do schedules follow my timezone?
Yes. Each schedule has its own timezone, so a weekday 7:00 run happens at 7:00 where you are, through daylight saving changes.
Comparing approaches? Read what agentic workflow automation means
Hand off the routine.
Start free, or see your own weekly process automated in a demo.