Create an issue on GitLab on every GitHub release
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Cron, Function (legacy). 2 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (legacy Cron node). Along the way it connects GitHub and GitLab.
How it runs
Trigger: On a schedule (legacy Cron node).
- Get latest release (GitHub): get many (release)
- List issues (GitLab): work with repository
- Merge: merges the data from its input branches
- No issue for release? (Function): runs custom JavaScript (legacy Function node)
- Create issue (GitLab): uses GitLab
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Cron: replace with Schedule Trigger.
- Function (legacy) in No issue for release?: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
| Function (legacy) No issue for release? | Code node, mode 'Run Once for All Items' |
Nodes used (5)
- GitHub
n8n-nodes-base.github - Cron
n8n-nodes-base.cron - Merge
n8n-nodes-base.merge - Function
n8n-nodes-base.function - GitLab
n8n-nodes-base.gitlab
From the author
For every release on GitHub this workflow will create an issue on GitLab. 1. Copy workflow to your n8n 2. Fill in missing fields (credentials & repo names) Based on Cron node to be able to track github repos you're not a member of (as you won't be able to…