HumDay

Post new GitHub issues and pull requests to Slack

HumDay can watch your GitHub repositories for new issues and pull requests and post each one to the Slack channel you choose. Which repositories, which events, and what the message carries are all named in the contract you approve first, and a proof run shows the real message before it reaches your team.

Build this automation

What this automation is built from

Real operations each provider publishes, in their own words. HumDay only ever uses the specific ones your approved contract needs.

Watching GitHub

See all GitHub operations

Acting in Slack

See all Slack operations

How this gets built

  1. Describe the outcome. The button above drops this job, already worded, into the composer — edit it until it says exactly what you want.
  2. Approve the contract. Before anything is built you see what it will do in GitHub and Slack, what it will never do, and what happens when something fails.
  3. See it proven. The generated program runs and shows you the result — including the duplicate rule working — before it is allowed near either account.
  4. Grant access, then go live. You approve the specific operations it may use on each side — and only those.

Related automations

Questions about this automation

Do I need to write code to post new GitHub issues and pull requests to Slack?
No. You describe the job in plain words and HumDay works out which GitHub and Slack operations it needs, writes the program, and shows you the result before anything runs live.
What do I need before this can run?
A GitHub account and a Slack account. You connect each one when the automation is ready, and you are shown exactly which operations it will use on each side before you grant access.
Will it ever act without my approval?
No. The contract you approve names everything the automation may do, anything that writes to Slack is held behind an approval you grant explicitly, and the generated program cannot reach any service the contract did not name.
How do I know it works before it touches my accounts?
Every automation runs a proof first: the generated program executes against realistic data and shows you the outcome — including what it does with duplicates and failures — before it is allowed near your live GitHub or Slack account.
What happens when something fails?
The contract states the failure behaviour up front — what is retried, what stops the run, and when you are told. A failure is reported to you rather than silently swallowed, and the run's evidence shows exactly what happened.

Where this came from

Operations are read from the published API descriptions for GitHub and Slack. Descriptions are each provider’s own words, not ours. See everything the GitHub and Slack integration can do.