Manage repositories, issues, and pull requests
846
Available Tools
46
Triggers
Get started with Agent Jam and connect GitHub along with 700+ other apps to supercharge your workflow.
Monitors for newly created GitHub Actions workflow artifacts. Optionallyfilters by artifact name to restrict monitoring to specific artifacts.Monitors a specific branch for:- New commits pushed (head commit SHA changes)- Protection status toggled (branch becomes protected or unprotected)- Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.Monitors a single check run for changes to: status (queued, in_progress,completed, etc.), conclusion (success, failure, neutral, cancelled, skipped,timed_out, action_required), started_at, and completed_at.Monitors all check suites associated with a git reference (branch, tag, orcommit SHA) for changes to status (queued, in_progress, completed, etc.) andconclusion (success, failure, neutral, cancelled, skipped, timed_out,action_required, startup_failure, stale). Optionally filters by GitHub App ID.Fires an event for each newly created code scanning alert detected inthe configured repository. Alerts can be filtered by Git reference,scanning tool, state, and severity. The payload includes the alertnumber, rule details, tool information, state, severity, and thelocation of the most recent instance.Monitors the full list of collaborators on a repository and fires an eventfor each newly added collaborator. The payload includes the collaborator'sGitHub username, account ID, profile URL, avatar URL, permission flags(pull, triage, push, maintain, admin), and assigned role name.Fires an event for each newly created deployment detected in theconfigured repository. Deployments can optionally be filtered by targetenvironment. The payload includes the deployment ID, commit SHA, ref,task, environment, creator details, and timestamps.Monitors the following aspects of a single deployment:- ``environment`` -- the target environment name- ``original_environment`` -- the original environment name before normalization- ``description`` -- the human-readable deployment description- ``task`` -- the deployment task name- ``sha`` -- the commit SHA being deployed- ``ref`` -- the branch, tag, or SHA reference being deployed- ``updated_at`` -- the last-updated timestamp- ``transient_environment`` -- whether the environment is temporary- ``production_environment`` -- whether this is a production deploymentWhen any of these fields change, an event is emitted containing the fullcurrent deployment details and a list of which fields changed.Fires an event for each newly created deployment status on the monitoreddeployment. Deployment statuses represent state transitions such aspending, in_progress, success, failure, error, inactive, and queued.The payload includes the status state, creator, environment, description,timestamps, and relevant URLs.Fires an event for each newly created branch or tag whose name matchesthe configured prefix. Use ``ref_prefix`` to control what is monitored:- ``heads/`` to watch all branches- ``heads/feature/`` to watch only feature branches- ``tags/`` to watch all tags- ``tags/v`` to watch tags starting with 'v'The payload includes the full reference name, node ID, the SHA and typeof the Git object the reference points to, and the reference API URL.Fires an event for each GitHub issue that is newly assigned to theauthenticated user. Pull requests are automatically excluded -- onlytrue issues are emitted. Issues can optionally be filtered by labelsand state. The payload includes the issue number, title, body, state,labels, assignees, creator, repository details, and timestamps.Monitors the following fields for changes:- ``body`` -- the text content of the comment (detects edits)- ``updated_at`` -- the last-updated timestamp- ``reactions_*`` -- all individual reaction counts (thumbs up/down, laugh, confused, heart, hooray, eyes, rocket) and the total countWhen a change is detected, the payload includes the full current commentdata plus a ``changed_fields`` list indicating exactly which fieldswere modified.Only genuinely new comments are emitted; edits to existing comments donot produce duplicate events. The payload includes the comment ID, textbody, author details, timestamps, and direct links to the comment onGitHub.Pull requests are automatically excluded -- only true issues produce events.Results can be filtered by labels, assignee, creator, and mentioned user.The payload includes the issue number, title, body, state, labels, assignees,comment count, creator details, timestamps, and direct links to the issue onGitHub.Covers all issue timeline events such as issues being closed, reopened,assigned, unassigned, labeled, unlabeled, milestoned, demilestoned,renamed, locked, or unlocked. Events can optionally be filtered by type.The payload includes the event type, timestamp, the actor who triggeredthe event, the affected issue details, and any associated commitreferences.Fires whenever a label is added to, removed from, or has its metadata(color, description) modified on the monitored issue. The payloadincludes:- ``current_labels`` -- the full set of labels currently on the issue- ``added_labels`` -- labels that were newly added- ``removed_label_names`` -- names of labels that were removed- ``changed_label_names`` -- labels whose metadata changed without being added or removedMonitored properties: state (open/closed), state_reason, title, body,assignees, labels, milestone, lock status, active_lock_reason, commentcount, and closed_at timestamp.When a change is detected, the payload includes the full current issuedetails, the list of changed field names, and their previous values.Monitors issues for any changes such as title edits, body edits, label changes,assignee changes, state transitions (opening, closing, reopening), milestoneupdates, and comment additions. Only pre-existing issues that receive updatesare emitted; newly created issues are excluded. Pull requests are also excluded-- only true issues fire events.Monitors all review comments across all reviews on the specified pull requestand emits an event for each newly created comment. Edits to existing commentsdo not fire new events.Monitors all commits on the specified pull request and emits an event foreach newly added commit. This covers force-pushes and additional commitspushed to the PR's head branch.Emits an event for each newly created pull request. Supports filtering byrepository, owner/organisation, author, assignee, label, state, base branch,head branch, and draft status.The payload includes the full current reviewer list (users and teams withdetails), which reviewers were added, which were removed, and the previousreviewer list for reference.Emits an event for each newly submitted review on the monitored pull request,covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, andDISMISSED.The payload includes the full current PR details, the list of changed fieldnames, and their previous values.Updates include title edits, description changes, label changes, assigneechanges, reviewer requests, draft status changes, base branch changes, beingclosed, merged, or reopened. Only pre-existing PRs that receive an updatewill fire the trigger; newly created PRs are excluded.Supports optional filters: state, base branch, head branch, author, label,and draft status.Monitors the README in a configurable directory and branch/tag/commit. Thepayload includes the current README metadata (filename, path, SHA, size,URLs), the previous and current git blob SHAs, and a list of which trackedfields changed.Monitors a single release (identified by release ID) for newly uploadedassets such as binaries, archives, or checksum files. One event is emittedper new asset, containing full asset metadata.Monitors the release title, body/notes, draft flag, prerelease flag,published timestamp, target branch/commit, and the set of attached assets.The payload includes the full current release details, a list of whichfields changed, and the previous values for comparison.Monitors a specified path within a repository on a given branch or tag.For a single file, fires ``content_changed`` when the file is modified.For a directory, fires ``content_changed``, ``content_added``, or``content_removed`` for modified, new, or deleted entries respectively.content.Monitors notifications for issues, pull requests, commits, releases,check suites, security alerts, and other repository activity. Supportsfiltering by read/unread status and by direct participation.Requires a Personal Access Token (classic) with the ``notifications``Monitors the repository's tags and fires an event for each newly createdtag. The payload includes the tag name, the commit SHA and URL it pointsto, and archive download URLs.Monitors open secret scanning alerts and fires an event for each newlydetected alert. Supports filtering by secret type (e.g., personal accesstokens, AWS keys) and by token validity status (active, inactive, unknown).The payload includes the alert number, secret type, validity status,resolution state, timestamps, URLs, and flags for push protection bypass,public exposure, and multi-repo detection.Monitors a repository's GitHub Actions workflows and fires an event foreach newly added workflow. The payload includes the workflow's name, filepath, state, creation and update timestamps, and URLs for the API, webinterface, and status badge.This is useful for detecting matrix-expanded jobs that are added after theinitial workflow run creation, or any other scenario where jobs aredynamically added to an existing run.The payload includes the full current job state, a list of which fieldschanged, and the previous status/conclusion values for easy comparison.Monitors a single workflow run for newly added artifacts such as build outputs,test results, or coverage reports. Each new artifact detected fires a separateevent.Monitors the repository for any new workflow runs and fires an event foreach one. Optional filters allow narrowing to a specific branch, actor,or event type.Monitors a single workflow run and fires an event whenever it transitionsbetween states (e.g., queued to in_progress, or in_progress to completed)or when its conclusion is set (e.g., success, failure, cancelled).