Automate GitHub from your browser

Use GitHub in workflows that start from the page you're on — straight from your browser to GitHub, nothing in between.

What you can do

Each action, one node.

Each action is a node you drop on the canvas. Pair it with any of the 10 triggers — a schedule, a right-click, a page change.

Example actions · Full list in the docs

Issue · CreateAction

Pull request · GetAction

Repository · GetAction

Release · Get latestAction

Issue · GetAction

Pull request · ListAction

Popular pairings

Better together.

GitHub

GitHub + any website

Read a table, a price or a listing on the page you're on and send it to GitHub.

GitHub

GitHub + on-device AI

Classify, summarise or rewrite with a model that runs in your browser before it reaches GitHub.

Templates

Templates that use GitHub

Browse all templates →

No published templates use GitHub yet. Docs recipe ↗

How to connect

Three steps. No surprises.

Full setup guide in the docs →

Create a token in GitHub
Generate an access token or API key in your GitHub settings. Give it only the access your workflows need.
Paste it into a credential
Add a GitHub credential in AWFlow and paste the token. Save it locally in this browser, or to your account when signed in.
Try it in a node
Pick the credential in a GitHub node and press Run in the editor. If the step succeeds, the credential works.

FAQ

Good questions.

Does my GitHub data go through AWFlow servers?

No. When a step runs, your browser sends the request to GitHub. AWFlow's servers never relay the call.

Do I need an AWFlow account?

No. Local mode works without an account and keeps the GitHub credential in this browser. Signed in, you choose per credential: this browser or your account. Installing a template from the Marketplace needs sign-in.

Does it run when my browser is closed?

No. Workflows run while your browser is open. A Wait of a minute or more in the extension survives closing the tab and picks up where it left off, for up to 30 days.

Does it cost anything per run?

No. Workflows run in your browser, so there are no per-task fees. GitHub applies its own usual limits.