Skip to content
Microsoft SQL Server logoGitHub logo

Connect Microsoft SQL Server to GitHub

Move data between Microsoft SQL Server 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.

Microsoft SQL Server triggers
1
Microsoft SQL Server actions
6
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with Microsoft SQL Server and GitHub

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

  • New or Updated Row in Microsoft SQL Server creates Create Issue in GitHub

    Fires when a row is added to, or changed in, a table

  • New Pull Request in GitHub creates Find Rows in Microsoft SQL Server

    Triggers when there is activity on a pull request.

  • New or Updated Row in Microsoft SQL Server creates Get issue information in GitHub

    Fires when a row is added to, or changed in, a table

  • New Pull Request in GitHub creates Insert Row in Microsoft SQL Server

    Triggers when there is activity on a pull request.

  • New or Updated Row in Microsoft SQL Server creates Create comment on a issue in GitHub

    Fires when a row is added to, or changed in, a table

  • New Pull Request in GitHub creates Update Rows in Microsoft SQL Server

    Triggers when there is activity on a pull request.

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 Microsoft SQL Server 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.