AI & Automation · Available in early access
Set the rule once. It runs itself.
Pick something that happens — a warning sign found on a prospect, someone applying or paying, a deploy that failed — then pick what Akiroo should do about it. Every rule saves as a draft, so nothing acts until you switch it on, and every run it makes is written down.
What it does
Inside Automation.
The tools available in this part of Akiroo.
- 01
Build a rule by picking what happens and what Akiroo should do about it.
- 02
React to warning signs found on your prospects — an expiring certificate or domain, a slowing website, a new job posting, a bad review, a visit to your site.
- 03
React to an application moving forward, from the form submission through to the payment.
- 04
React to your own code and infrastructure: pushes on a connected GitHub or Forgejo repository, and deploys, ships and monitor alerts from connected Teploy tools.
- 05
Act on it: file a task, note it on the prospect, move a deal, change a prospect status, email a prospect, or post to your connected social accounts.
- 06
Narrow a rule with a filter so it fires only on the cases you care about.
- 07
Run history for every rule that fired: the step it took, the result, and the reason when it deliberately stopped.
- 08
Deploy, roll back or restart an app on a connected server, each run held for a person to approve by default.
Questions
A few useful
details.
What can a rule react to?+
Warning signs Akiroo finds on your prospects — an expiring certificate or domain, a website slowing down, a new job posting, a bad review, a visit to your own site — plus applications moving through intake, and the pushes, deploys and monitor alerts from the repositories and deployment tools you have connected.
Can a half-finished rule email my customers?+
No. Every rule saves as a draft, and a draft never runs. Sending email and posting publicly need a person to enable the rule first, and anything that touches a live server is held for approval on top of that.
Early access