Built in integrations for everyday business tools
A scheduled AI agent is only useful if its output lands somewhere people look. Crons ships with native integrations for the tools most teams open every morning, and an HTTP step for everything else. You connect an account once in your workspace and every cron can use it as a source, a destination or both.
| Integration | Typical reads | Typical writes |
|---|---|---|
| Slack | Messages in a channel you choose | Post summaries, threads and approval requests |
| Gmail | Labeled emails and attachments | Send or draft emails, behind an approval gate if you want |
| HubSpot | Contacts, companies, deals and properties | Create or update records, add notes and tasks |
| Google Sheets | Rows from a named sheet | Append rows, update cells, keep a log tab |
| Notion | Pages and database entries | Create pages, update database properties |
| Webhooks out | Not applicable | POST a JSON payload to your endpoint |
| HTTP request | Any REST or JSON endpoint | Any REST endpoint with stored credentials |
Integrations, outgoing webhooks, memory, retries, approvals and alerts are included on every plan, starting with Starter. Inbound webhooks and the REST API are part of Pro and Teams. See the full comparison on the pricing page.
Scoped OAuth that you can revoke any time
When you connect Slack, Gmail, HubSpot, Google Sheets or Notion, Crons asks for the narrowest set of permissions the integration needs. For Google Sheets you can limit access to the files you pick. For Slack the bot only posts in channels it has been invited to. For HubSpot you see which objects the connection can read and write before you approve it.
- Tokens are encrypted at rest and never shown in run logs or prompts
- Each connection shows which crons use it, so you know the impact before you change it
- Revoke a connection in Crons or in the connected tool and it stops working on the next step
- On Pro and Teams, roles decide who can create connections and who can only use them
If a token expires or is revoked, the step fails cleanly, the run log says which connection broke and you get an alert. Nothing is retried with a different account. Read more about data handling on the security page.
Connect anything else with HTTP steps and webhooks
Your stack has more than five tools. The HTTP request step calls any REST or JSON API with a method, URL, headers and body. Authentication values live in the credential store and are referenced by name, so an API key never sits inside the cron description. The AI reasoning step can read the JSON response and decide what matters, which saves you from writing parsing code for each endpoint.
Outgoing webhooks send a structured JSON payload to an endpoint you control at the end of a run or after any step. Teams use them to feed an internal dashboard, a data warehouse loader or another automation tool. On Pro and Teams, inbound webhooks let other systems start a cron, which is covered on the API, webhooks and MCP page.
Approval gates before writes that matter
Reading data is low risk. Writing to a CRM, emailing a customer or posting in a public channel is not. In Crons you can place an approval gate in front of any integration action. The run pauses, a reviewer sees the exact record or message in Slack or the dashboard, and the step continues only after someone approves it. Rejected steps are logged with the reviewer and the reason.
The planner adds approval gates by default before customer emails, CRM writes and posts to public channels. You can remove them for internal channels where speed matters more, and you can run any cron as a dry run to see every planned write without sending anything.
Example crons that combine several tools
- 1Every Monday at 8 AM, read new HubSpot deals over $10,000, research each company on the web and post a one paragraph brief in #sales.
- 2Every day at 6 PM, read Gmail messages labeled Invoices, extract totals into Google Sheets and flag any amount that does not match the purchase order.
- 3Every Friday at 3 PM, collect product mentions from three community sites, summarize sentiment in a Notion page and send the link to Slack.
Each of these is one sentence on the homepage. The demo shows the parsed schedule, the steps and a sample first result before you sign up. For ready made versions, browse cron templates by department.
Frequently asked questions
Which integrations does Crons support?
Slack, Gmail, HubSpot, Google Sheets and Notion are built in. Outgoing webhooks and HTTP requests connect any other system with a REST or JSON API.
Can I limit what Crons can access in my tools?
Yes. Connections use scoped OAuth with the narrowest permissions the integration needs, and in Google Sheets you can pick specific files. You see the scopes before approving.
How do I revoke access?
Remove the connection in your Crons workspace or revoke it in the connected tool. It stops working on the next step and every affected run shows which connection failed.
Are integrations included in every plan?
Yes. Starter, Pro and Teams all include integrations, outgoing webhooks, memory, retries, approvals and alerts. Inbound webhooks, the REST API and code steps are on Pro and Teams.
Can a cron email customers or update the CRM without review?
Only if you remove the approval gate. By default the planner places a gate before customer emails, CRM writes and public posts, so a person confirms each one.
What if the tool I use is not listed?
Use the HTTP request step with credentials from the credential store, or send results to your own endpoint with an outgoing webhook.