Slack automation that runs on your own machine.
Cronable posts to Slack as the last step of a workflow: the nightly backup result, a failed payment, yesterday’s sales in three plain sentences. The workflow runs on a computer you control, and the bot token behind it never leaves your encrypted store.
A Slack workflow on the canvas
Each card is one job. A wire means the next job runs when the one before it succeeds, or when it fails.
Post to #sales
Slack·Running
After Summarize sales (succeeded)
2s
Summarize sales
Claude (API)·Succeeded
After Paid orders (succeeded)
3 min ago
Paid orders
Shopify·Succeeded
Daily at 08:00
4 min ago
Paid orders
Shopify·Succeeded
Daily at 08:00
4 min ago
Summarize sales
Claude (API)·Succeeded
After Paid orders (succeeded)
3 min ago
Post to #sales
Slack·Running
After Summarize sales (succeeded)
2s
“Every weekday at 8am, summarize yesterday’s paid Shopify orders and post it to #sales in Slack.”
Every Slack step Cronable ships
Actions
Steps a workflow can take in Slack.Post a message to a channel
Send text to any channel by name (#ops) or ID. Slack’s mrkdwn formatting works, and both the channel and the message can pull in data from earlier steps.
Reply in a thread
Give the timestamp of an earlier message and the post lands as a threaded reply. Every Slack post returns its own timestamp, so one run can keep all its updates in one thread.
Alert only when something breaks
Attach a Slack job as another job’s failure handler and it posts only when that job fails.
Triggers
What starts a Slack workflow.Slack is an action in Cronable: it posts, it does not listen. A Slack workflow starts from a schedule, from another job finishing, or from a trigger in another app, such as a Stripe event, a GitHub push or a new row in a sheet. To start a workflow from a chat message, use the Telegram integration’s message trigger.
Slack workflows worth automating first
Daily sales digest
Each morning a Shopify job pulls yesterday’s paid orders, a Claude step turns them into a short summary, and Slack posts it to #sales. Nobody has to open a dashboard.
Backup watch for #ops
A terminal job runs your nightly backup. On success one Slack job posts the summary; on failure another pings the channel, so silence never has to mean “probably fine”.
Payment-failure alerts
A Stripe trigger fires on every failed payment, a Filter step keeps the ones worth chasing, and Slack tells finance who to contact.
Release notes in one thread
When a GitHub release is published, an AI step drafts the notes and the first Slack post opens a thread. Later steps reply underneath with test and deploy results.
How you connect
Connecting Slack
Slack connects with a bot token you paste once. There is no OAuth app to host and nothing for Slack to review.
- 1Create a Slack app in your workspace and give its bot the chat:write scope.
- 2Install the app and copy its bot token, the one that starts with xoxb-.
- 3Store the token as a Slack credential under Settings → Secrets → Credentials. Test connection checks it without posting anything.
- 4Invite the bot to each channel it should post in.
Your Slack automation, on your own machine
Runs on your own machine
Install Cronable as a Mac or Windows app, or on a server you own. Your Slack jobs, secrets and run history stay on that machine by default.
Built from one sentence
Describe the workflow in plain English and the built-in assistant builds the jobs, the schedule and the failure handling for you to review on the canvas. On every plan, including Free.
Unlimited runs
Plans count the jobs you define, not how often they fire. A job that touches Slack every hour costs the same as one that runs once a month.
Credentials encrypted locally
Keys and tokens are AES-256-GCM encrypted in a local database, referenced from jobs by name and masked out of logs and run output.
Slack automation, answered
Can Cronable send messages to Slack?
Yes. A Slack job posts a message to a channel through Slack’s chat.postMessage API, as a bot you install in your own workspace. Run it on a schedule, after another job, or as a failure alert.
Do I need a Slack app or a bot token?
You need a bot token, and it comes from a Slack app you create in a few minutes: add the chat:write scope, install the app to your workspace and copy the xoxb- token. The app never has to be published or reviewed.
Where is my Slack token stored?
In Cronable’s credential store on your own machine, encrypted with AES-256-GCM. Jobs refer to it by name, so the token never appears in a job file, and it is masked out of run logs.
Can a Slack message trigger a workflow?
Not today. The Slack integration posts messages; it does not receive them. Workflows that end in Slack usually start from a schedule or a trigger in another app, and the Telegram integration can start a workflow from a chat message.
Why does a send fail with not_in_channel?
The bot has to be a member of a channel before it can post there. Invite it (for a private channel, add it and use the channel ID) and run the job again.
Related integrations
Solutions that use Slack
Anything you do twice in Slack is cronable.
Pick the report you paste into Slack by hand every week. Start there.