← All N8N workflows
Automation & utilitiesHTTP RequestIfSchedule TriggerEdit FieldsLoop Over Items

api to check existing merge request and create new merge request and api to close existing merge request

Configured with HTTP Request, Schedule Trigger, Loop Over Items, Wait. Review the connections and setup before adapting this template.

Workflow preview
Web / APIAPI to Check existingmerge requestHTTP RequestRoutingIs ExistsIfWeb / APICreate New MergeRequestHTTP RequestRoutingLoop Over ItemsLoop Over ItemsWeb / APIAPI to CLOSE existingMerge RequestHTTP RequestWeb / APIAdd Custom Notes ToMerge RequestHTTP RequestWait30 secs wait to approvemerge request and…WaitWeb / APIMerge When PipelineSucceedsHTTP RequestTransformsetValueForMergeEdit FieldsTriggerSchedule TriggerSchedule Trigger

Node categories in this workflow

  • Web / API
  • Routing
  • Wait
  • Transform
  • Trigger

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
API to Check existing merge requestWeb / APIHTTP RequestSee node parameters
Is ExistsRoutingIfSee node parameters
Create New Merge RequestWeb / APIHTTP RequestPOST
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
API to CLOSE existing Merge RequestWeb / APIHTTP RequestPUT
Add Custom Notes To Merge RequestWeb / APIHTTP RequestPOST
30 secs wait to approve merge request and pipeline to finish1WaitWaitSee node parameters
Merge When Pipeline SucceedsWeb / APIHTTP RequestPUT
setValueForMergeTransformEdit FieldsSee node parameters
Schedule TriggerTriggerSchedule TriggerSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

api to check existing merge request and create new merge request and api to close existing merge request

api to check existing merge request and create new merge request and api to close existing merge request

Purpose and structure

This folder contains the api to check existing merge request and create new merge request and api to close existing merge request workflow. Its executable nodes use httpRequest, if, scheduleTrigger, set, splitInBatches, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Schedule Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0717_HTTP_Schedule_Create_Scheduled.json MIT; preserve source notices.

More in Automation & utilities