Axer

Blog/Product

Bots that do anything

A bot in Axer is a general-purpose agent on a schedule or a webhook — not a narrow checklist.

Axer Team · 15 November 2026

Automations
Bots

The first bots we shipped were familiar: watch a site, watch a board, send a digest. Useful, but too small. A bot in Axer is now a general-purpose agent. It can use a browser, run code, call an API, and write back to you. You describe the job in your own words, or start from a template.

How a bot runs

You give it a name, a prompt, and a schedule — every hour, every day, every week, or only when a webhook fires. Each run spends credits from the same balance you use in the editor. You can pause a bot, read the run history, and open any run to see the steps it took.

If a tool is missing — a Trello board, a Slack channel — the bot does not ask you to paste a token into a form. It shows one Connect button. You approve access, and the run continues with the connection you already have.

Templates, still

Ready-made templates are still there: Trello or Jira watchers, server health, search positions, uptime and SSL, a review on each push, a morning digest, competitor prices. They are starting points. You can change the prompt, the schedule, and the connections after you create one.

Connections

Trello, Jira, GitHub, Slack, Telegram, Meta, and Google are all meant to connect with that same one-click step. A few of them need a public HTTPS domain before the last mile works; the button is there either way, and “advanced” is where a raw key would go if you ever need it.

Bots are not a second product. They use the same agent, the same credits, and the same account.

Back to the blog