Generate your GitLab year-in-review wrapped report automatically
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs when someone submits an n8n form (“GitLab Wrapped 2024”). It uses only n8n's built-in nodes. It also calls gitlab.com over HTTP.
How it runs
Trigger: When someone submits an n8n form (“GitLab Wrapped 2024”).
- Workflow Configuration (Edit Fields (Set)): sets 4 fields: name, apiToken, gitlabUrl…
- Validate PAT Owner (HTTP Request): calls an HTTP API
- Is PAT Owner invalid? (If): checks a condition and branches into true / false
- Search Existing Fork (HTTP Request): calls an HTTP API
- Try to fork (HTTP Request): calls gitlab.com (POST)
- Merge: merges the data from its input branches
- set ProjectId (Code): runs custom JavaScript code
- Set token env var (HTTP Request): calls an HTTP API (POST)
- Set Username env var (HTTP Request): calls an HTTP API (POST)
- Set Year env var (HTTP Request): calls an HTTP API (POST)
…plus 4 more steps. See the full node list below.
HTTP calls to: gitlab.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - Wait
n8n-nodes-base.wait - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - No Operation, do nothing
n8n-nodes-base.noOp
From the author
GitLab Wrapped Generator ✨ Automatically generate your personalized GitLab Wrapped, a stunning year-in-review of your contributions, activity, and stats. Powered by gitlab-wrapped by @michaelangelorivera. 🚀 How it works 1. Forks the gitlab-wrapped project…