Skip to content
Netlify logoGitHub logo

Connect Netlify to GitHub

Move data between Netlify and GitHub the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Netlify triggers
4
Netlify actions
4
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with Netlify and GitHub

A few flows teams run between Netlify and GitHub. Use one as a starting point, or build your own from scratch.

  • New Deploy Started in Netlify creates Create Issue in GitHub

    Fires immediately when a deploy job starts on your Netlify site.

  • New Pull Request in GitHub creates Start Deploy in Netlify

    Triggers on any pull request activity: opened, edited, closed and more.

  • New Deploy Started in Netlify creates Get Issue Information in GitHub

    Fires immediately when a deploy job starts on your Netlify site.

  • New Pull Request in GitHub creates Get Site in Netlify

    Triggers on any pull request activity: opened, edited, closed and more.

  • New Deploy Started in Netlify creates Create Comment on Issue in GitHub

    Fires immediately when a deploy job starts on your Netlify site.

  • New Pull Request in GitHub creates List Site Deploys in Netlify

    Triggers on any pull request activity: opened, edited, closed and more.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Netlify and acts in GitHub, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.