Let Kendr do recurring work on its own.
Kendr Automations runs on a schedule, when a form is answered, a file lands in a Drive folder, a task moves or a webhook is called. Describe what should happen in plain words and check the steps Kendr drafts.
Kendr does the work, then files it, posts it or emails it. Every run is logged step by step with a credit cap, and anything that sends outside Kendr asks for your OK first.
Every run on the record
Each run shows its trigger, every step and its log, and what it cost. Paused automations do not run, and new automations are saved switched off until you turn them on.
Frequently asked questions
What can start an automation?
A schedule, a Kendr event such as a form response or a new file, a webhook, or a manual run.
Can an automation overspend?
No. Every run has a credit cap, and every run is logged.
Do automations start running straight away?
No. A new automation is saved off; you check the steps and switch it on.