Mattering Automations GitHub integration

Connect GitHub to Mattering Automations: issues, pull requests, and repo data as workflow steps, plus webhook triggers that start workflows from pushes, PRs, and new issues.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations GitHub integration adds GitHub to your automation canvas: create and manage issues, query pull requests and repo data, and start workflows the moment code is pushed, a pull request opens, or an issue is filed.

Setup takes a few minutes: create a personal access token in GitHub, attach it as a credential in Mattering, and optionally register a webhook for the trigger nodes. This guide walks through each step and ends with the full node reference.

Before you start

A GitHub account with access to the repositories you want to automate.
A Mattering workspace with access to the Automations app.
For trigger nodes: permission to manage webhooks on the target repository (repo admin).

Create a GitHub personal access token

Mattering authenticates to GitHub with a personal access token. Fine-grained tokens are recommended because they scope access to specific repositories.

In GitHub, open Settings > Developer settings > Personal access tokens (github.com/settings/tokens).

Choose Fine-grained tokens > Generate new token, name it (for example, Mattering Automations), and select the repositories it may access.

Grant Issues and Pull requests read and write permissions, plus Metadata read (required by GitHub).

Click Generate token and copy it.

GitHub shows the token exactly once. If you navigate away before copying, generate a new one; fine-grained tokens also expire by default, so note the expiry you choose.

Connect GitHub to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose GitHub from the list.

Click Create new credential, paste your token, and save.

The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.

Click Test Connection: Mattering calls GitHub's user endpoint and reports which account it authenticated as.

Click Connect. All 11 GitHub nodes appear in your canvas palette.

How webhook triggers deliver

GitHub pushes events to Mattering the moment they happen; no polling, no schedules.

Event happens

A push, pull request, or issue in GitHub

Signed delivery to your webhook URL

Mattering verifies the signature and reads the event type

Your workflows run

Every active automation containing the trigger node fires

Verify it works

After connecting, open any automation canvas and check the palette: a GitHub section should list the query, action, and trigger nodes. Drop GitHub Repo Info onto the canvas, set a repository you can access, and run a test step; a successful response returns the repo's metadata.

For triggers, open the trigger node's config panel: it shows your webhook URL with a copy button. Add it in the repository under Settings > Webhooks > Add webhook with content type application/json, and select the events to deliver. GitHub sends a ping to verify; after that, matching events run every active automation containing that trigger.

Node reference

11 nodes, generated from the connector itself so this reference always matches what ships.

Trigger nodes (start workflows from events) 3

GitHub Issue Opened

trigger_github_issue_opened

Fires when an issue is opened

GitHub PR Opened

trigger_github_pr_opened

Fires when a pull request is opened

GitHub Push

trigger_github_push

Fires when code is pushed to a repository

Read and query nodes 3

GitHub Issues

query_github_repo_issues

List issues in a GitHub repository

GitHub PRs

query_github_pull_requests

List pull requests in a GitHub repository

GitHub Repo Info

query_github_repo_info

Get repository metadata

Action nodes 5

Close GitHub Issue

action_github_close_issue

Close a GitHub issue

Create GitHub Issue

action_github_create_issue

Create a new issue in a GitHub repository

Create GitHub Label

action_github_create_label

Create a label in a GitHub repository

GitHub Comment

action_github_create_comment

Add a comment to a GitHub issue or PR

Update GitHub Issue

action_github_update_issue

Update an existing GitHub issue

Using the integration

On the automation canvas

GitHub nodes chain with every other node: a new issue can create an assigned task in Mattering Productivity, an AI step can classify and label it, and a push to main can update a release checklist.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can file issues, comment, and query repos through the same nodes your workflows use.

Webhook triggers

Push, PR opened, and issue opened events start workflows without polling. Place the trigger node in an automation, set the automation to active, and register the webhook URL once per repository.

Troubleshooting

Test Connection fails with a 401

The token is invalid, expired, or lacks Metadata read permission. Fine-grained tokens expire by default; generate a new one and update the credential on the connector.

Nodes work but a specific repository returns 404

Fine-grained tokens only see the repositories selected at creation. Edit the token's repository access in GitHub, or create a new token that includes the repo.

The trigger never fires

Check three things: the automation containing the trigger node is set to active, the webhook is registered on the repository with content type application/json, and the webhook's recent deliveries in GitHub show a 200 response from Mattering. GitHub's ping event responds with pong when the URL is right.

The trigger fires for events from the wrong repository

All repositories pointing at the same webhook URL feed the same triggers. Add a condition step after the trigger that checks the repository field of the payload when an automation should only react to one repo.

The GitHub MCP

What connecting GitHub unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

GitHub is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.