Skip to content
GitHub logo0CodeKit logo

Connect GitHub to 0CodeKit

Move data between GitHub and 0CodeKit 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.

GitHub triggers
14
GitHub actions
19
0CodeKit triggers
0
0CodeKit actions
75

Automation ideas

What you can build with GitHub and 0CodeKit

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

  • New Pull Request in GitHub creates Current Month in 0CodeKit

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

  • New Pull Request in GitHub creates Specific Month and Year in 0CodeKit

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

  • New Pull Request in GitHub creates Current Week in 0CodeKit

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

  • New Star in GitHub creates Current Month in 0CodeKit

    Triggers when someone stars or unstars the repository.

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 GitHub and acts in 0CodeKit, 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.