GitHub Integration — Automate GitHub with AI on Beauto

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

Category: developer tools · 871 actions available

What you can automate with GitHub

Beauto connects GitHub with 900+ other apps so you can build AI-powered workflows in minutes. Trigger automations from GitHub events, enrich GitHub data with AI, or sync GitHub with the rest of your stack — without writing code.

  • Sync GitHub data with Gmail, Slack, Notion, HubSpot, Google Sheets, and more
  • Trigger AI agents on new GitHub events and route the output anywhere
  • Schedule recurring GitHub tasks — daily reports, cleanups, or bulk updates
  • Use natural language to describe the workflow; Beauto builds it for you

GitHub actions Beauto supports

  • Abort Repository Migration — Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
  • Accept a repository invitation — Accepts a PENDING repository invitation that has been issued to the authenticated user.
  • Add app access restrictions — Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal re
  • Add a repository collaborator — Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and
  • Add assignees to an issue — Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
  • Add email for auth user — Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existi
  • Add field to user project — Tool to add a custom field to a user-owned GitHub Projects V2 project. Use when you need to add fields like status, priority, or custom data to organize project items.
  • Add item to user project — Tool to add an issue or pull request to a user-owned GitHub project. Use when you need to add existing repository items to a project board.
  • Add labels to an issue — Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
  • Add org runner labels — Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
  • Add or update team membership for a user — Adds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
  • Add or update team project permissions — Adds a classic project to a team or updates the team's permission on it. This endpoint grants or updates permissions for a team on a specific classic project (not Projects V2). The authenticated user must have admin perm
  • Add or update team repository permissions — Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
  • Add a repository to an app installation — Adds a repository to a GitHub App installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
  • Add repo to org secret with selected access — Adds a repository to an existing organization-level GitHub Actions secret that is configured for 'selected' repository access.
  • Add selected repo to org secret — Grants an existing repository access to an existing organization-level Dependabot secret when the secret's visibility is set to 'selected'; the repository must belong to the organization, and the call succeeds without ch
  • Add runner labels — Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
  • Add selected repository to an organization secret — Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
  • Add selected repository to an organization variable — Grants a repository access to an organization-level GitHub Actions variable, if that variable's visibility is set to 'selected_repositories'.
  • Add a selected repository to a user secret — Grants a specified repository access to an authenticated user's existing Codespaces secret, enabling Codespaces created for that repository to use the secret.
  • Add social accounts for the authenticated user — Adds one or more social media links (which must be valid, full URLs for platforms supported by GitHub) to the authenticated user's public GitHub profile.
  • Add status check contexts — Adds status check contexts to a protected branch's required status checks. This action appends new status check contexts to the existing list of required status checks for a protected branch. The branch must already have
  • Add sub-issue to an issue — Tool to add a sub-issue to a parent GitHub issue using GraphQL. Use when you need to establish a parent-child relationship between issues. Requires the 'sub_issues' GraphQL feature to be enabled.
  • Add team access restrictions — Adds teams to the list of teams with push access to a protected branch. This action grants additional teams push access to a protected branch. Unlike 'Set team access restrictions' (PUT), this action adds to the existing
  • Add user access restrictions — Adds users to the list of people allowed to push to a protected branch in an organization repository. Important notes: - This action only works on organization-owned repositories (not personal repos) - The branch must al
  • Add users to codespaces access for an organization — Adds organization members to the list of users granted Codespaces access billed to the organization. IMPORTANT: This endpoint requires the organization's Codespaces billing access to be set to 'selected_members' mode. If
  • Get GitHub API root — Retrieves a map of all top-level GitHub REST API resource URLs and their templates.
  • Approve a workflow run for a fork pull request — Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
  • Assign an organization role to a team — Assigns an existing organization-level role (identified by `role_id`) to a team (identified by `team_slug`) within a GitHub organization (`org`), provided the organization, team, and role already exist.
  • Assign an organization role to a user — Assigns a specific organization role to a user who is a member or an outside collaborator in a GitHub organization, using a valid role ID.
  • Block a user — Blocks an existing individual GitHub user (not an organization or your own account), preventing them from interacting with your account and repositories.
  • Block a user from an organization — Blocks a GitHub user from an organization, preventing their contributions, collaboration, and forking of the organization's repositories. Requires admin or 'Blocking users' organization permission (write access).
  • Cancel a GitHub Pages deployment — Cancels an existing, ongoing or queued GitHub Pages deployment for a repository using its `pages_deployment_id`.
  • Cancel sponsorship — Tool to cancel an active GitHub sponsorship using GraphQL. Use when you need to terminate a sponsorship relationship between a sponsor and a sponsorable entity. Either sponsor ID/login and sponsorable ID/login must be pr
  • Cancel a workflow run — Cancels a workflow run in a GitHub repository if it is in a cancellable state (e.g., 'in_progress' or 'queued'). Returns 202 Accepted on success.
  • Check if a gist is starred — Checks if a gist is starred by the authenticated user. Returns `is_starred: true` if the gist is starred (HTTP 204), or `is_starred: false` if not starred (HTTP 404). Use this to verify star status before starring/unstar
  • Check if pull request merged — Checks if a specified GitHub pull request has been merged, indicated by a 204 HTTP status (merged) or 404 (not merged/found).
  • Check if a user can be assigned — Verifies if a GitHub user can be assigned to issues in a repository; assignability is confirmed by an HTTP 204 (No Content) response, resulting in an empty 'data' field in the response.
  • Check if a user can be assigned to an issue — Checks if a specified GitHub user can be assigned to a given issue within a repository.
  • Check if a user follows another user — Checks if a GitHub user `username` follows `target_user`; returns a 204 HTTP status if true, 404 if not or if users are invalid.

GitHub triggers

  • New Workflow Artifact Created — Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artif
  • Branch Changed — Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection se
  • New Branch Created — Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
  • Check Run Status / Conclusion Changed — Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cance
  • Check Suite Status / Conclusion Changed — Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progr
  • New Code Scanning Alert Created — Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, s
  • New Repository Collaborator Added — Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborat
  • Commit Event — Triggered when a new commit is pushed to a repository.
  • New Deployment Created — Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target envi
  • GitHub Deployment State Changed — Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original
  • New Deployment Status Created — Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions su
  • Follower Changes — Triggers when new followers are detected on your GitHub account.
  • New Git Reference Created — Triggers when a new Git reference (branch or tag) matching a specified prefix is created in a repository. Fires an event for each newly created branch or tag whose name matches the configured prefix. Use ``r
  • Issue Added Event — Triggered when a new issue is added to the repository.
  • New Issue Assigned to Me — Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true i
  • GitHub Issue Comment Changed — Triggers when a specific GitHub issue comment changes. Monitors the following fields for changes: - ``body`` -- the text content of the comment (detects edits) - ``updated_at`` -- the last-updated timestamp
  • New GitHub Issue Comment — Triggers when a new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload includes the comment ID, text
  • New Issue Created — Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user.
  • New Issue Event — Triggers when a new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, rena
  • GitHub Issue Labels Changed — Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes:

Related integrations

Browse all 900+ integrations →

Get started with GitHub on Beauto

Sign up free, connect your GitHub account in one click, and describe the workflow you want in plain English. Beauto's AI handles the rest — no API keys or code required.

Try Beauto free · Browse all 900+ integrations · How it works