Pipedream GitHub Sync → n8n and Git

Pipedream GitHub Sync and n8n Git source control solve the same problem, versioned workflows, but they work differently, and n8n's version is limited to paid plans. This page covers both directions: using a GitHub Sync repository as the input for a migration, and keeping your n8n workflows in Git afterwards.

Pipedream GitHub Sync as migration input

GitHub Sync connects a Pipedream project to one GitHub repository. Pipedream serializes the project's workflows to YAML (workflow.yaml), supports branches and pull requests, and deploys when you merge to the production branch.

Why it matters for migration: the official Export Workflows button writes to a File Store, and File Stores are listed for Advanced plans and above. If your project already syncs to GitHub, the repository is a second input that doesn't depend on that button.

Limits to know:

• Pipedream hasn't published a definition of the YAML ("Not yet, please stay tuned!" in its FAQ), so tools read it by example.
• Our converter finds no trigger configuration in GitHub Sync files, so it adds a Manual Trigger and asks you to set the real trigger (Webhook, Schedule) by hand. The official export includes triggers, so use it when you can.
• Legacy (v1) workflows can't be in projects, so they are not in the repository either.

Our free report accepts a GitHub Sync repository as a ZIP (download it from GitHub) as well as the official export.

n8n source control

n8n's built-in Git integration is called source control and environments (docs):

• Plans: Business and Enterprise. The n8n pricing page lists it for Cloud Enterprise and self-hosted Business; it is not in Community Edition (features).
• Model: each n8n instance connects to a branch; you push from one environment and pull into another (for example dev → prod).
• What is committed: workflows (with tags and owner email), credential stubs (ID, name, type), variable stubs, data table schemas (without rows), projects and folders (push and pull).
• Push sends the saved version, not the published one.

	Pipedream GitHub Sync	n8n source control
Format	YAML (spec unpublished)	n8n workflow JSON
Deploy	Merge to production	Pull into the target instance, then publish
Secrets in repo	Not documented	Credential stubs only
Plans	Docs don't state a general plan tier	Business, Enterprise

Git without a paid plan

On Community Edition or n8n Cloud Starter/Pro, use the public API instead:

mkdir -p workflows
cursor=""
while :; do
  page=$(curl -sS "$N8N_URL/api/v1/workflows?limit=250${cursor:+&cursor=$cursor}" -H "X-N8N-API-KEY: $N8N_API_KEY")
  echo "$page" | jq -c '.data[]' | while read -r wf; do
    echo "$wf" | jq . > "workflows/$(echo "$wf" | jq -r .id).json"
  done
  cursor=$(echo "$page" | jq -r '.nextCursor // empty')
  [ -z "$cursor" ] && break
done
git add -A workflows && git commit -m "n8n backup $(date +%F)"

The API returns at most 250 workflows per page, so the loop follows nextCursor (pagination). Run it on a schedule (cron, CI, or an n8n workflow with the n8n node). To restore, import the JSON. The API isn't available on the n8n Cloud free trial.

Next steps

• Getting the official export instead: export Pipedream workflows
• Hosting choice and which plan has Git: n8n Cloud vs self-hosted
• Full guide: migrate Pipedream to n8n

Not affiliated with Pipedream, GitHub or n8n.