Pipedream GitHub → n8n

6 Pipedream GitHub actions and 7 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: github.

Actions

Pipedream action	n8n	Fit	Notes
github-create-issue	Github issue → create	Check output	owner/repository use the resourceLocator 'url' mode: the node's extractValue regexes pull owner and repo out of https://github.com/<owner>/<repo>, so the PD 'owner/repo' string needs no split. PD also accepts a bare repo name (no '/') and resolves the owner…
github-create-issue-comment	Github issue → createComment	Direct	Same endpoint as PD, so PR numbers work too. Bare repo names (no owner) need the authenticated user's login prepended (PD resolves it at runtime).
github-update-issue	Github issue → edit	Check output	editFields is sent as the PATCH body. labels/assignees REPLACE the existing set in both PD and n8n. state values open/closed match the n8n options exactly. The milestone cannot be set (no editFields option), so it needs an HTTP Request PATCH with {milestone}.
github-get-repository	Github repository → get	Direct	Bare repo names (no owner) need the authenticated user's login prepended.
github-search-issues-and-pull-requests	Http Request	Check output	The n8n Github node has no search operation, so this uses the HTTP Request fallback with the exact endpoint PD calls (GET /search/issues?q=). The githubApi credential's authenticate block adds 'Authorization: token <PAT>'.
github-create-or-update-file-contents	Github file → create	Check output	PD upserts: it GETs the file and adds its sha when it exists. n8n splits this into file:create (fails with 422 if the file exists) and file:edit (looks up the sha, fails with 404 if the file is missing). The template uses 'create'. If the workflow rewrites…

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
github-new-or-updated-issue	Github Trigger	Check output	PD silently falls back to polling (timer) when the user is not a repo admin. The n8n trigger only supports webhooks and needs admin rights on the repo; for non-admin repos use Schedule Trigger + Github repository:getIssues (sort by updated) with your own…
github-new-or-updated-pull-request	Github Trigger	Check output	Webhook only, needs repo admin (PD fell back to polling without admin). No dedupe in n8n.
github-new-commit	Github Trigger	Check output	Webhook only, needs repo admin (PD fell back to polling). Each push yields one execution, versus PD's one event per commit.
github-new-star	Github Trigger	Check output	Webhook only, needs repo admin. PD deduped by sender id (one event per user ever), while n8n emits every star/unstar delivery that passes the filter.
github-webhook-events	Github Trigger	Check output	Both need repo admin. Both skip the initial ping/zen delivery. PD dedupes on x-github-delivery, while n8n does not. events is an expression so that events missing from n8n's dropdown (e.g. workflow_run, branch_protection_rule, pull_request_review_thread)…
github-new-issue	Github Trigger	Check output	REMOVED from the registry on 2022-06-24 (commit 6e5eabe8, replaced by github-new-or-updated-issue). The prop is spelled 'repoFullName' (capital N), the value is 'owner/repo'. Historical source at sha 60e45e06.
github-new-pull-request	Github Trigger	Check output	REMOVED from the registry on 2022-06-24 (commit 6e5eabe8, replaced by github-new-or-updated-pull-request). Prop 'repoFullName' (capital N). Historical source at sha 60e45e06.

Credentials

Create a GitHub credential in n8n (type githubApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a GitHub node?+

Yes. 5 of the 6 Pipedream GitHub actions listed here map to a native n8n node; 1 map to n8n's HTTP Request node with the GitHub credential.

Will my Pipedream GitHub connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a GitHub credential in n8n (type githubApi) and select it on the converted nodes.

Are Pipedream GitHub triggers supported in n8n?+

7 of the 7 Pipedream GitHub event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the GitHub API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly ClickUp Discord Dropbox Email (SMTP)Gmail Google Calendar Google Drive Google Gemini Google Sheets All apps →