Inbox & chat
An AI agent that keeps up with Slack so you do not have to.
Connect Slack and an OpenHelm agent can read the channels you scope it to, summarise what happened, answer or escalate questions, and post updates from your other jobs. Recurring schedules mean the digest is there before you are.
What agents do with Slack. Recurring jobs, checked every run.
Daily channel digest
Summarise the channels you care about into one morning message or email: decisions made, questions still open, and anything that mentions your team.
Support-channel triage
Watch a #support or #help channel, classify new questions, draft suggested answers from your docs, and flag the ones that need an engineer.
Job results posted to Slack
Have any other OpenHelm job, such as a weekly report or a monitoring run, post its structured result into a channel when it completes.
Unanswered-message sweep
On a schedule, find questions in shared channels that never got a reply and compile them into a follow-up list for the owner.
Connect Slack. A few minutes, once.
Connect Slack
Add Slack under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections/links \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "provider": "<provider id>", "name": "Slack" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.Questions
Which channels can the agent see?
Only the ones the connected credential can access. Connections are scoped and revocable, so you decide which workspaces and channels are in reach, and you can withdraw access at any time.
How does OpenHelm connect to Slack?
Through a scoped OAuth grant: you sign in to Slack once via a hosted connect flow, in the OpenHelm app or via a connect link minted with POST /v1/connections/links. OpenHelm stores no passwords, the grant is limited to what your jobs need, and you can revoke it at any time.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Slack data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
More in Inbox & chat
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.