Which GitHub steps convert automatically?

Create Issue and Create Issue Comment become HTTP Request nodes against the GitHub REST API with your n8n GitHub credential. GitHub sources become a GitHub Trigger node.

Which events does the GitHub Trigger support?

Over 40 repository events, including push, pull request, pull request review, issues, issue comment, release, star, fork, deployment and check runs.

Which credential should I use?

n8n recommends an API access token: a classic personal access token with the repo scope. OAuth2 works for the GitHub node and GitHub Trigger too.

Is this about Pipedream's GitHub Sync?

No. This page is about GitHub steps inside workflows. Pipedream's GitHub Sync (workflows stored as files in a repo) is an input format the converter reads directly.

Pipedream GitHub steps in n8n

Updated 2026-10-21 · 3 min read · n8n: GitHub (Native n8n node)

GitHub steps in Pipedream connect repositories to the rest of the stack: a new issue goes to Slack or Jira, a release triggers a deploy, a form creates an issue. n8n has a native GitHub node and a webhook-based GitHub Trigger; the most used actions and the trigger convert automatically.

The n8n side

GitHub node (n8n-nodes-base.github):

Resource	Operations
File	Create, Delete, Edit, Get, List
Issue	Create, Create Comment, Edit, Get, Lock
Pull Request	Create, Get, Update, Merge, Close, Reopen, Create Comment, Get Diff, …
Release	Create, Delete, Get, Get Many, Update
Repository	Get, Get Issues, Get Pull Requests, Get License, Get Profile, List Popular Paths, List Referrers
Review	Create, Get, Get Many, Update
Organization	Get Repositories
User	Get Repositories, Invite
Workflow	Disable, Dispatch, Enable, Get, Get Usage, List

GitHub Trigger: creates a repository webhook for the events you choose (over 40 options, or all events).

What maps where

Pipedream (app `github`)	In n8n	Status
Create Issue (title, body, labels, assignees, milestone)	HTTP Request `POST /repos/{owner}/{repo}/issues`	automatic
Create Issue Comment	HTTP Request `POST /repos/{owner}/{repo}/issues/{n}/comments`	automatic
Create or Update File Contents	GitHub → File → Create / Edit	manual
Create Branch	HTTP Request `POST /repos/{owner}/{repo}/git/refs`	manual
Search Issues and Pull Requests	HTTP Request `GET /search/issues`	manual
Create Gist	HTTP Request `POST /gists`	manual
New Commit, New Branch Created, New or Updated Issue, New or Updated Pull Request, New release, …	GitHub Trigger (starts with `push`; set owner, repo and events)	automatic node, set events
Code step with `@octokit/rest` and `this.github.$auth.oauth_access_token`	Code node; token becomes `GITHUB_OAUTH_ACCESS_TOKEN`, package listed	automatic, review

Credentials

n8n's GitHub credential page lists:

API access token – works with all GitHub nodes. n8n recommends a classic personal access token with the repo scope; fine-grained tokens have limitations with some operations.
OAuth2 – works with the GitHub node and the GitHub Trigger.
For GitHub Enterprise Server, change the server URL in the credential.

The trigger needs permission to create webhooks on the repository (admin on the repo, or the admin:repo_hook scope).

Typical migration: bug form to issue and Slack

Pipedream: HTTP trigger (bug form) → Create Issue → Slack Send Message. n8n after conversion: Webhook → Code (trigger) → HTTP Request (GitHub issue) → HTTP Request (Slack). Two credentials and one URL change.

Typical migration: release notes

Pipedream: New Release → OpenAI Chat (summarise) → Discord Send Message. n8n: GitHub Trigger (release) → HTTP Request (OpenAI) → Code → HTTP Request (Discord webhook). All three steps convert automatically; set the trigger's owner, repository and event.

Pitfalls

Polling vs webhooks. Some Pipedream GitHub sources polled (for example New Commit on a branch). The n8n trigger uses webhooks, so you get events faster, but filters such as "only branch main" become an If node on ref.
Rate limits. 5,000 requests per hour for personal access tokens and OAuth tokens (15,000 on Enterprise Cloud), 60 unauthenticated. Over the limit returns 403 or 429 with x-ratelimit-remaining: 0.
Webhook secret. Repository webhooks can carry a secret; if the repo had Pipedream's webhook, delete it after the switch so events are not processed twice.
Issue numbers vs IDs. REST paths use the issue number, not the global ID.

How to move your GitHub workflows

Export the workflows from Pipedream, or point the converter at the GitHub Sync folder.
Upload on /convert; the free report shows the automatic GitHub steps and the trigger events to set.
Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

Guide: Pipedream to n8n; Octokit code goes through the code step checker. Related: Jira, Discord, Slack.

FAQ

Which GitHub steps convert automatically?: Create Issue and Create Issue Comment become HTTP Request nodes against the GitHub REST API with your n8n GitHub credential. GitHub sources become a GitHub Trigger node.
Which events does the GitHub Trigger support?: Over 40 repository events, including push, pull request, pull request review, issues, issue comment, release, star, fork, deployment and check runs.
Which credential should I use?: n8n recommends an API access token: a classic personal access token with the repo scope. OAuth2 works for the GitHub node and GitHub Trigger too.
Is this about Pipedream's GitHub Sync?: No. This page is about GitHub steps inside workflows. Pipedream's GitHub Sync (workflows stored as files in a repo) is an input format the converter reads directly.