Development teams want the GitHub events that matter in Slack, not every notification. FlowMattic catches repository events on your WordPress site, filters them, and posts new issues, pull request summaries, failed builds, releases and security alerts to the channel or person who should act, with GitHub actions such as requesting reviewers in the same workflow.
45 triggers 55 actions 8 example workflows 6 ready-made templates Unlimited runs
When this happens in GitHub45 triggers
Do this in Slack14 actions
1. TriggerNew / Updated Issue2. ActionSend Channel MessageWhen GitHub fires New / Updated Issue, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateA Filter keeps only issues that were just opened, so the channel shows the repository, title, link and author without noise from every edit or label change.
New / Updated IssueFilterSend Channel Message
View the template Ready-made templateAn AI Agent reads the pull request title and description and posts a short plain-language summary, so reviewers know what changed before opening the diff.
New / Updated Pull RequestFilterAI AgentSend Channel Message
View the template Ready-made templateA Router reads each new issue's label, sending bugs to the bugs channel and feature requests to the product channel, so each group sees its own queue.
New / Updated IssueFilterRouterSend Channel Message
View the template Ready-made templateA Router checks how many lines a pull request adds. Big ones get extra reviewers requested on GitHub and a heads-up in Slack, small ones go through as usual.
New / Updated Pull RequestRouterRequest Pull Request ReviewersSend Channel Message
View the template A Filter passes only completed runs whose conclusion is failure, and the workflow name, branch and run link go to the build channel so someone fixes it before the next merge.
Workflow Run CompletedFilterSend Channel Message
When a release is published, its version and notes go to an announcements channel, so support and sales know what shipped without asking engineering.
New ReleaseFilterSend Channel Message
Lookup Table maps GitHub usernames to work emails. The pull request author is found in Slack and gets a direct message with the review, so changes are picked up the same day.
Pull Request ReviewLookup TableFind User by EmailSend Direct Message
A Filter keeps newly created Dependabot alerts, which post to a private security channel with the package and severity, keeping vulnerability details away from public channels.
Dependabot AlertFilterSend Private Channel Message
When you finish, each newly opened issue in your repository is posted to a Slack channel.
Add a GitHub connection and a Slack connection under Connects. The GitHub account needs access to the repository you want to watch.
Create a workflow with the GitHub New / Updated Issue trigger, choose the repository and open a test issue so FlowMattic captures it.
Add a Filter that continues only when the event's action is opened, so edits, labels and closes are skipped.
Add a Slack step with Send Channel Message, pick the channel, map the repository, title, link and author, test it and switch the workflow on.
1. Trigger in GitHub
New / Updated Issue
3. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From GitHub | To Slack |
|---|---|
| Repository full name | Message text |
| Issue title | Message text |
| Issue URL | Message link |
| Issue author login | Message text |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
GitHub and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Filter, Router and AI Agent decide what reaches Slack, so channels carry the issues, failures and releases people need.
Actions such as Request Pull Request Reviewers or Add Labels to Issue run alongside the Slack post, so the alert and the follow-up happen together.
Runs are unlimited on every plan and happen on your own server, so a monorepo with constant activity needs no bigger plan.
Yes. Start from New / Updated Pull Request, Filter on the action you want, such as opened or closed, and add Send Channel Message. Add an AI Agent step for a summary.
Yes. Build one workflow per repository, or use a Router on the repository name and give each path its own Slack step.
Yes. After Workflow Run Completed and a Filter for failures, map the actor's username to an email with Lookup Table, find them with Find User by Email and send a direct message.
Not in this pair, as Slack has no triggers here. A form or a Webhook can start a workflow that runs GitHub Create Issue and posts the link to Slack.
Yes. Use a Schedule, fetch open ones with List Pull Requests, format the list with Text Formatter and post it with Send Channel Message.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. GitHub integration 1.0.0, Slack integration 1.0.
