Skip to content
Crons

AI cron jobs for business teams

Scheduled AI agents that work every day

Write the job in one sentence. Crons runs it on schedule, remembers what changed and sends the results to Slack, HubSpot or Sheets.

Ask me before

Live blueprint

Updates as you type
Every Monday at 08:00 0 8 * * 1 next Mon 19 Oct, 08:00 UTC
  1. Oct 19 Mon 08:00
  2. Oct 26 Mon 08:00
  3. Nov 2 Mon 08:00

Competitor Monitor, 6 steps

  1. Fetch 20 competitor pricing pages
  2. Load yesterday's snapshot of each page
  3. Find price, plan and limit changes
  4. 3 more steps in the full blueprint

Your blueprint is built from your words and a library of tested templates. Nothing runs until you choose a plan.

Operations lead at a standing desk reading a finished overnight run log on a large monitor

The screen you live in

Every recurring job in one list, with the next run in plain sight

Your Crons shows each agent, its schedule in words and as a cron expression, when it fires next and how the last run went. Green means it ran and delivered. Amber means it is waiting for you.

Analyst checking the next scheduled runs on a laptop beside a wall calendar
Your Crons 5 active
Cron Schedule Delivers to Next run Last run
Lead Generation Every 4 hours 0 */4 * * * HubSpot Slack in 2h Ran 1 h ago, 3 leads added
Competitor Monitor Every day at 08:00 0 8 * * * Slack in 11h Ran today, 3 changes found
SEO Audit Every Monday at 08:00 0 8 * * 1 Sheets Gmail in 84h Ran Monday, 9 issues
Invoice Reconciliation Every month on the 1st 0 9 1 * * Sheets Gmail in 408h 6 reminders need approval
Customer Health Digest Every weekday at 08:30 30 8 * * 1-5 Sheets Slack in 16h Ran today, 4 at risk

Product screen with example crons and fictional data.

Why teams switch to Crons

You describe the outcome once and the work keeps happening

Recurring research eats the first hour of too many mornings. Someone opens twenty tabs, compares them with last week, writes a summary and pastes it into Slack. Crons does that job on a schedule, with the judgment of an AI model and the discipline of a cron.

SEO manager reviewing a Monday report on a large monitor
You type Every Monday at 08:00 audit our top 50 pages and put the fixes in Google Sheets
Every Monday at 08:00 0 8 * * 1 6 steps

Write it once, in your own words

No trigger trees, no field mapping. You write what you want and when, Crons turns it into a schedule, a numbered list of steps and the connections it needs. You can edit any step in plain English later, and the blueprint updates with it.

Product marketer comparing two web pages on two monitors
Halcyon Metrics, Pro$79$99 Orbitline, Team seats105 Cobalt Deskno change, not reported

It remembers what changed since the last run

Each cron keeps its own memory. It stores what it saw, compares the new run against it and reports only the difference. Leads are never added twice, a competitor page that did not move stays quiet, and an issue that is still open says so.

Finance manager approving a reconciliation on a laptop
Approval needed, Invoice Reconciliation

6 reminder emails are ready to send from Gmail, total $18,420 overdue.

Approve and send Review drafts

You approve the risky part, the rest runs alone

Mark any step as critical and the cron pauses there. You see exactly what it is about to send or write, then approve or reject with one click in Slack or the dashboard. Research, fetching and summarizing run on their own. Customer emails and CRM writes wait for a person.

RevOps lead reading a morning digest on a laptop

#sales-leads 08:02

Lead Generation found 3 qualified companies. Northwind Analytics, ICP 86. Bluefield Logistics Cloud, ICP 81. Corvel Health Data, ICP 74. Added to HubSpot.

Results land where your team already works

A Slack message at 8 AM, a new row in Google Sheets, a company in HubSpot, a page in Notion or an email in Gmail. You pick the destination when you write the cron. Nobody has to log in to another tool to read what the agent found.

Attempt 1 failed, timeout

Attempt 2 in 30 s

Attempt 2 succeeded

Retries and alerts handle the bad days

A slow site or a flaky API gets three tries with backoff. If a step still fails, you get one clear alert with the step and the error, not a silent gap in your Monday report.

web_fetch1.8 s

ai, compare4.2 s

slack, post0.4 s

A full run log you can audit

Every run keeps each step's input, output, timing and retries. When someone asks why a lead was added or a price was flagged, the answer is one click away and exportable.

Templates

Start from a cron that already works for your department

Every template is a complete cron with a schedule, steps, memory rules and approval points. Open one, change the wording to fit your team and turn it on.

Browse all templates

Sales

Leads that fit, delivered while they are still fresh.

Marketing

Audits and reports that land before Monday standup.

Competitive intelligence

Every price, plan and launch your rivals ship.

Recruiting

A growing shortlist without a day of searching.

Finance

Reconciled books and reminders you approve.

Customer success

Accounts at risk, flagged before they cancel.

How a run works

Each run reads, compares, decides and delivers in a few minutes

  1. 1

    The schedule fires

    At the time you set, in your timezone, Crons starts the run. You can also run it by hand or start it from a webhook.

  2. 2

    Steps gather the facts

    Web fetch and browser steps read the pages, HTTP steps call your APIs, integration steps read Sheets, HubSpot or Gmail.

  3. 3

    Memory filters the noise

    The cron compares what it found with what it saw before and keeps only what is new or changed.

  4. 4

    AI writes the result

    A model step summarizes, scores or drafts, inside the plan limits you can see in the dashboard.

  5. 5

    You approve, it delivers

    Critical steps wait for your click. Everything else lands in Slack, Sheets, HubSpot, Notion or Gmail.

Competitor Monitor, run 214

Started Thu 08:00 Europe/Berlin, finished in 2 min 41 s

Succeeded

  1. 1. Fetch 20 competitor pricing pages

    20 pages, 1 retry

    38.2 s

  2. 2. Load yesterday's snapshot

    20 snapshots

    0.3 s

  3. 3. Find price, plan and limit changes

    3 changes, 17 unchanged

    41.7 s

  4. 4. Continue only when something changed

    true

    0.1 s

  5. 5. Send the summary to #competitive

    message posted

    0.6 s

  6. 6. Save today's snapshot

    20 snapshots saved

    0.4 s
Usage this run, 3 AI calls, 0 browser minutes. Plan usage this month, 41 percent.

For the person who signs off

Predictable cost, controlled risk and hours back every week

Crons is easy to approve because nothing about it is open ended. The price is a flat plan. The limits are hard and visible. The agents ask before they act on anything that matters.

  • Flat plan, hard limits. Runs, AI calls and browser minutes per month are fixed per plan. No credits, no overage, an alert at 80 percent.

  • Approval gates and audit log. Critical steps wait for a person. Teams adds an audit log of every change and approval, plus SSO.

  • Your data stays yours. Credentials are encrypted at rest, connections are scoped and revocable, and your data is not used to train models.

Small team reviewing a dashboard on a wall screen

Work out the value with your own numbers

Change the inputs to match your team. We do not fill in anyone else's results.

Time cost today per month

Plan cost per month

If the crons take over this work, the time freed is worth the plan, about a month.

Estimate from your inputs only, using 52 weeks per year. Check plan limits for the run frequency you need.

Honest comparison

Crons fits recurring research that needs judgment and a schedule

Each option below is good at something. Here is where Crons is the better fit and where it is not.

Doing it by hand Classic workflow builders Cron monitors Crons
How you set it up A calendar reminder and a checklist Draw triggers and map fields Point at a job you already wrote Write one sentence
Reads and judges web pages Yes, slowly Limited, needs extra steps No Yes, fetch, browser and AI steps
Remembers last run In someone's head Only if you build storage Only success or failure Built in, per cron
Approval before risky actions Yes Possible with extra setup Not applicable Built in, one click in Slack
Runs on a schedule When someone remembers Yes Watches your schedule Yes, written in plain English
Best fit One off tasks Moving data between apps Watching your own scripts Recurring research, monitoring and reports

If you only need to know when your own server script failed, a cron monitor is the right tool. Crons runs the job itself.

Built so an agent never acts without the controls you expect

Approvals

Critical steps wait for a person before anything is sent or written.

Audit log

Every run, change and approval is recorded. Full audit log on Teams.

SSO on Teams

SAML single sign on, roles, approval rules per team and a 99.9 percent uptime SLA.

Encryption

Credentials encrypted at rest, scoped connections you can revoke.

Final payments

Cancel any time in the billing portal. Payments are final.

Read how security works

Pricing

One flat price per month with every limit in plain view

Pick the plan that fits how many crons you run and how often. Every plan includes memory, approvals, retries and the full run log.

Starter

One team member automating their own recurring research.

$49 per month

Billed $588 yearly

  • Up to 10 active crons
  • 300 runs and 3,000 AI calls per month
  • Natural language schedules, every hour at most
  • Slack, Gmail, Google Sheets, Notion, HubSpot and outgoing webhooks
  • Web fetch and 60 browser minutes per month
  • Memory between runs, 3 retries with backoff, failure alerts by email and Slack
  • Human approval before critical actions
Most teams start here

Pro

A team running sales, marketing and competitor crons.

$149 per month

Billed $1,788 yearly

  • Up to 50 active crons
  • 1,500 runs and 10,000 AI calls per month
  • Runs as often as every 15 minutes
  • 300 browser minutes per month
  • Inbound webhook triggers, REST API and MCP server access
  • Custom code steps in a sandbox
  • Run logs kept 90 days, CSV export of run history

Teams

Company wide agents with SSO, audit log, roles and a 99.9% uptime SLA.

$499 per month

Billed $5,988 yearly

  • Unlimited active crons, fair use, run limit applies
  • 6,000 runs and 35,000 AI calls per month
  • Runs as often as every 5 minutes
  • 1,200 browser minutes per month
  • Up to 25 seats, roles and approval rules per team
  • SSO (SAML), audit log, roles, IP allowlist for webhooks
  • 99.9% uptime SLA with service credits, 4 hour support reply

Prices in USD. Cancel any time in the billing portal, access stays until the end of the paid period. Compare every limit

Questions

Straight answers to what buyers ask before they start

Still unsure about something? Write to support@crons.ai and a person answers.

How is Crons different from Zapier or Make?

In a workflow builder you wire triggers and actions together by hand, and the result does exactly what you drew. In Crons you describe the outcome in a sentence, and Crons builds the schedule, the steps and the integrations for you. The unit is a cron: a job with a schedule, memory of earlier runs and approval gates. It is built for recurring research and reporting, where the work is reading, comparing and summarizing, not only moving a field from one app to another.

Will the AI do something wrong in my CRM or send a bad email?

Any step that writes to a CRM, sends an email or posts to a channel can be marked critical. A critical step stops and waits for your click in Slack or in the dashboard, with the exact content it is about to send. You can also run any cron in dry run mode, where every action is logged but nothing leaves Crons. Every input, output and decision of every step stays in the run log.

What does it cost if a cron runs a lot?

Your plan price. Each plan has a fixed number of runs, AI calls and browser minutes per month, shown in the dashboard. At 80 percent you get an alert. At 100 percent new runs stop until the next period or until you move to a bigger plan. There are no credits, no top ups and no overage bills.

Can it log in to sites or use our internal API?

Yes. Browser steps open real pages, click and read what a person would see. HTTP steps call any API with credentials you store once, encrypted. Pro and Teams add inbound webhooks to start a cron from your own systems, a REST API, and MCP access so other agents can list, run and read your crons.

What happens when a run fails?

Each step retries up to 3 times with backoff. If it still fails, you get an alert in Slack or by email with the failing step and its error. The cron keeps its memory, so the next run continues from what it already knows instead of starting from zero, and nothing is reported twice.

Is our data used to train models?

No. We use model providers under business terms that do not train on customer inputs or outputs. Your instructions, connected data and run results are used only to run your crons, stay in your workspace, and are deleted when you delete them or close the account.

Can I cancel?

Yes, any time, in the billing portal. Your plan stays active until the end of the period you paid for, then your crons pause. Payments are final, as described in the refund policy, so pick the plan that fits your current crons and move up when you need more.

Hand your next Monday report to a cron

Write the job, see the blueprint in seconds, save it to your account and turn it on when you are ready.

Build my cron Start from a template
Build my cron