Turn GitHub activity into automated action
React to pushes, PRs, issues and workflow runs on GitHub, then act back automatically
Connect GitHub and use what happens in your repositories to drive automations, then let InfraNest act back on GitHub for you.
- React to repository events: trigger automations on pushes, pull requests, reviews, issues, comments, releases, check runs and suites, workflow runs, deployments, and branch or tag creation and deletion.
- Act on GitHub automatically: open, comment on, close or reopen issues, add or remove labels, assign issues, request reviews, merge pull requests, trigger or rerun workflows, cancel runs, set commit status, create releases, and create deployments or update their status.
- Choose what InfraNest can see: pick specific repositories, or all of them, when you connect — and change that selection on GitHub at any time.
- Connect more than one account: link your personal account and an organisation separately, each as its own connection.
NoteRequesting a review from a team only works when you connect an organisation, not a personal account.
What it looks like in InfraNest
When this happens
GitHub workflow run
A GitHub Actions workflow run changed state — started, completed, failed or succeeded.
Runs at 09:00 · Europe/Amsterdam · it’s 15:49 there now
Next runs:Sat 19 Sept, 09:00Sun 20 Sept, 09:00Mon 21 Sept, 09:00
This automation only runs when you click “Run now”.
Only if — optional filters
MatchAllAnyNoneof these conditions
Tip: a value can reference another field or the time using a placeholder.
Do this — actions run in order, stop at the first failure
In plain English
When GitHub workflow run if Status equals completed, then Create GitHub issue and Send notification.
What you can do
Once GitHub is connected, this is what InfraNest can do with it.
- 14 GitHub triggers (push, PR, issue, workflow run, deployment...)
- 19 GitHub actions (merge PR, trigger workflow, create release...)
- Per-repository access, chosen at connect time
- Multiple GitHub accounts as separate connections
How to connect it
- 1
Open the GitHub integration
Go to Integrations and open GitHub.
- 2
Start automatic setup
Select Connect, then Set up automatically to install the InfraNest app on GitHub.
- 3
Pick your repositories
In the GitHub window, choose the account or organisation, then select All repositories or just the ones you want InfraNest to see.
- 4
Confirm the connection
You're returned to InfraNest and the connection appears under Accounts. Prefer a token instead? Choose Use a token and paste a personal access token with repo access.
That’s it — GitHub is connected.
Full setup guideSet up with AI
I use GitHub, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Personal access token, or connect in one click. Walk me through creating that in GitHub: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
Questions
#What can InfraNest see and do once it's connected?
InfraNest can watch activity in the repositories you selected — pushes, pull requests, issues, workflow runs, deployments, releases and checks — and take actions back on GitHub as part of an automation, such as merging a pull request, triggering a workflow or opening an issue. You choose which repositories are included when you connect, and can adjust that later on GitHub.
#Should I use the automatic setup or a token?
The automatic setup, which installs the InfraNest app, is recommended — it scopes access to only the repositories you pick and needs no token to rotate. Use a token instead if you can't install an app, for example on a self-hosted GitHub instance.
#What happens if I revoke the token or uninstall the app?
If you disconnect GitHub from the Integrations hub, InfraNest uninstalls the app and loses access; if the same installation is shared with another workspace, that one is left in place. If a personal access token is revoked or expires, automations that rely on the GitHub connection will stop working until it's reconnected.
#Can I change which repositories InfraNest has access to later?
Yes. Open the InfraNest app on GitHub under your account or organisation's Settings → GitHub Apps → InfraNest and adjust the selected repositories at any time.
#Can I connect both my personal account and my organisation?
Yes, each is set up separately and appears as its own connection. Note that team-based actions, like requesting a review from a team, only work through an organisation connection.
Often connected together
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes