GitHub logo
Slack logo

Workflow template

Send new GitHub pull requests to Slack

Announce newly opened GitHub pull requests in Slack, including drafts. Show the PR number, title, repository, author, branch direction, draft flag and GitHub link in one plain-text message.

How it works

From a PR opening to a Slack announcement

1 Trigger · 1 Action
GitHub1 · Trigger

Pull Request

Receive opened pull_request events from your selected repository. Draft PRs are included; edits, new commits, reviews, closures and reopenings are excluded by the prepared filter.

Slack2 · Action

Notify the team about a new pull request

Post the PR number, title, repository, author, source-to-target branches, draft flag and link to the chosen Slack channel. Use plain text with link and media previews disabled.

The result

A channel notice with the proposed branch change

The announcement helps the team notice a new PR and follow its source link. It does not assign a reviewer or wait for review readiness.

Example Slack pull request notice

New GitHub pull request #58: Improve the customer portal onboarding guide Repository: example-studio/customer-portal Opened by: alex-example Branches: docs/onboarding-guide -> main Draft: false https://github.com/example-studio/customer-portal/pull/58

Fictional PR. The full PR body, code changes and attachments remain outside the prepared message.

Before activation

Set up your workflow

  1. Select a GitHub repository

    Connect the FastHook GitHub App with access to the repository and select it in the trigger browser. Keep opened in Actions. This includes newly opened drafts.

  2. Choose the Slack review channel

    Connect Slack and select a channel where the FastHook bot can post. Review its members because PR titles, branch names and repository details will be visible there.

  3. Activate and open a fictional PR

    Wait for the GitHub trigger to connect, then open a fictional PR. Check the Slack announcement’s source-to-target branches and draft flag, and confirm the GitHub link points to that PR.

Details and limitations
  • An opening event includes drafts. A new draft PR can produce an announcement with Draft true. The workflow does not wait for ready-for-review or assign reviewers. The message reports the opening event rather than current review status.

  • Later PR activity is excluded. Existing PRs are not imported. Edits, commits, submitted reviews, closures and reopenings do not produce another alert under the opened filter, and the earlier Slack message is not updated.

  • Channel access and repeat notices. The prepared message copies selected metadata with link and media previews disabled. Channel membership does not grant GitHub access to a private PR. Manual reruns can post duplicate notices.

Questions about this template

Why did a draft PR send a Slack message?

The prepared filter is opened, which includes draft PRs. The message shows the draft flag and does not wait until the PR is ready for review.

Will new commits or reviews update the Slack notice?

No. The recipe handles PR openings only. New commits, edits, reviews, closures and reopenings do not send or update messages through this workflow.

Does the alert assign a reviewer or include a code diff?

No. It sends identifying PR metadata and a source link. Reviewer assignment, PR bodies, code changes and attachments are outside the prepared action.

Can channel members open a private PR automatically?

No. They can read the copied metadata in Slack, but they still need GitHub permission to open the source PR.

Explore connected apps