Engineering workflows that start in your inbox.
GitHub is connected to this+that via the Model Context Protocol. Workflows triggered by email or Slack can read repositories, open issues, check PR status, and query commit history — then act on what they find, across every channel your team uses.
Model Context Protocol — built-in, no extra setup
GitHub is one of the built-in MCP servers in this+that. Connect it once by authorizing with your GitHub account, and every workflow you build can reach into your repositories as an action step. We use read and write access scoped to the repositories you choose — create issues, read PR status, comment on threads, query open issues by label or assignee. The MCP connection is managed from your this+that settings and can be revoked at any time from your GitHub account.
Engineering workflows, triggered by messages
Describe the workflow. this+that handles the trigger, the GitHub action, and the notification.
"When a customer email mentions a bug or error, create a GitHub issue in the relevant repo and reply with the issue number"
Bug reports from email go straight into GitHub. The customer gets a confirmation; the engineer gets a ticket.
"When a PR is mentioned in a Slack message in #engineering, add a DoBox task for the reviewer with a link"
Slack-to-GitHub-to-DoBox. PR review reminders surface in the task view without anyone manually tracking them.
"Every Monday, send me a digest of open PRs with no review activity in the past 3 days"
Stale PR detection on a schedule. The digest lands in your inbox — no GitHub dashboard required.
"When a GitHub issue is closed, email the original requester with the resolution summary"
Closing the loop with the person who reported it. No manual follow-up email to write.
"When a high-priority GitHub issue is opened, post it to #engineering in Slack and assign a DoBox task"
Issue-triggered notifications across every channel simultaneously. One event, three outputs.
"Weekly: summarize the commits and merged PRs from the past 7 days and send to the product team"
Engineering changelog as an automated email digest. Product always knows what shipped.
GitHub access within workflows
Read repositories and issues
Query open issues by label, assignee, milestone, or date. Use the data as conditions in IF/ELSE workflow logic.
Create issues
Open new issues with a title, body, labels, and assignee — triggered by an email, a Slack message, or a schedule.
Read and comment on PRs
Check PR status, list reviewers, read review comments. Add comments as a workflow step.
Query commit history
List recent commits by author, branch, or date range — useful for digest workflows sent to non-technical stakeholders.
GitHub + Slack + email = the full engineering workflow
The most useful engineering workflows connect all three. A customer emails a bug report — GitHub gets the issue, Slack gets the alert, the customer gets an automated reply with the issue number. A PR is reviewed and merged — the product team gets an email summary, the QA channel gets a Slack notification. Connect Notion via MCP alongside GitHub and release notes can be drafted automatically from merged PR descriptions.
Connect GitHub to your engineering workflow.
Start with your inbox analysis, then add GitHub to turn the workflows you describe into automation that runs itself.
Free to use · No credit card required