HumDay

Automate Slack

HumDay reads Slack’s own published API description and derives 174 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Slack

What Slack is

One way to interact with the Slack platform is its HTTP RPC-based Web API, a collection of methods requiring OAuth 2.0-based user, bot, or workspace tokens blessed with related OAuth scopes.

API host: slack.com

Things people automate with Slack

What HumDay can do in Slack

94 documented operations change something in Slack. The 55 most useful are listed here.

What HumDay can read from Slack

These are the operations a schedule or a trigger can watch.

How automating Slack works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Slack account.
  4. Grant access, then go live. You approve the specific Slack operations it may use — and only those.

Popular Slack integrations

Connect Slack to the tools people pair it with most.

Automate Slack with these

Categories

Questions about Slack automation

Can HumDay connect to Slack?
Yes. HumDay reads Slack's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 174 operations are documented.
Do I need to write code to automate Slack?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Slack account.
What can HumDay do in Slack?
94 of the 174 documented operations change something in Slack, and 80 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Slack account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Slack is held behind that approval.

Where this came from

The operations above are read from a published API description for Slack at raw.githubusercontent.com/slackapi/slack-api-specs/master/web-api/slack_web_openapi_v2.jso. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.