# Automated creation and closing of GitLab merge requests on schedule
This automation template is designed for developers and DevOps engineers who want to streamline merge request management in GitLab. The workflow runs on a schedule, checks for existing MRs on a specified branch, and either creates new ones or closes existing ones, triggering auto-merge after pipeline success.
## Who it´s for
- Developers automating CI/CD in GitLab.
- DevOps engineers managing multiple merge requests.
- Teams implementing regular automated deployments.
## What the automation does
- Checks for open MRs on a given branch on schedule.
- Creates a new MR if none exists, adds notes.
- Closes existing MRs if found.
- Requests auto-merge 30 seconds after creation, once pipeline succeeds.
- Processes all input items sequentially.
## What´s included
- Ready-to-use n8n workflow.
- Trigger and handler logic based on cron_schedule.
- Integrations with GitLab API via HTTP requests.
- Basic setup and adaptation instructions.
## Requirements for setup
- GitLab account with API access.
- API token with required permissions (api scope).
- Configured n8n instance.
## Benefits and outcomes
- Eliminates manual MR creation and closure.
- Prevents conflicts from stale or duplicate MRs.
- Accelerates feature branch deployment to staging.
- Ensures regular branch synchronization on schedule.
- Integrates into existing CI/CD pipelines without code changes.
## Important: template only
Important: you are purchasing a ready-made automation workflow template only. Rollout into your infrastructure, connecting specific accounts and services, 1:1 setup help, custom adjustments for non-standard stacks and any consulting support are provided as a separate paid service at an individual rate. To discuss custom work or 1:1 help, contact via chat
No feedback yet