Skip to content
GitHub logoBrowserless logo

Connect GitHub to Browserless

Move data between GitHub and Browserless 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
Browserless triggers
0
Browserless actions
5

Automation ideas

What you can build with GitHub and Browserless

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

  • New Pull Request in GitHub creates Capture Screenshot in Browserless

    Triggers when there is activity on a pull request.

  • New Pull Request in GitHub creates Generate PDF in Browserless

    Triggers when there is activity on a pull request.

  • New Pull Request in GitHub creates Scrape URL in Browserless

    Triggers when there is activity on a pull request.

  • New Star in GitHub creates Capture Screenshot in Browserless

    Trigger when there is activity relating to repository stars.

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 Browserless, 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.