Connect an account
Open Connections → API connections and choose GitHub. Give the connection a name and enter a personal access token. The token is encrypted on the server; the editor stores only its connection ID. You can keep separate connections for different accounts or repositories and select one in each GitHub step.
Limit the token to the repositories and permissions your workflow needs. Connection presence does not prove that a repository is accessible: test a Get Repository step against the intended repository before publishing.
Available actions
| Action | Purpose |
|---|---|
| Get Repository | Read repository details |
| Create Issue | Open an issue |
| Comment on Issue | Add an issue or pull request comment |
| Close Issue | Close an existing issue |
| Trigger Repository Dispatch | Send an event handled by a GitHub Actions workflow |
| Star Repository | Star a repository as the connected user |
For example, issue creation requires Issues: write permission. Repository dispatch requires Contents: write and a workflow in the repository that handles the event. GitHub can impose rate limits and additional organization authorization. Use its permission reference to choose the required permissions.
Build a workflow
Create an empty workflow, add the GitHub extension, then connect a Manual trigger to Get Repository. Choose your connection, owner and repository. Test the step, then use its typed output in conditions or other platform actions.
A GitHub action does not subscribe to repository events. Native GitHub event subscriptions are not provided by these actions. The generic Webhook trigger remains available for integrations with an appropriately verified event source.
Rotate or remove access
Replace the token from Connections when rotating it. Existing nodes keep their connection ID. Disable or delete a connection to block subsequent requests. Revocation at GitHub is separate from deleting the local connection.
The integration pins the supported 2022-11-28 REST contract. See
GitHub API versions.