Short answer: You can create gitlab merge request in GitLab by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitLab Create GitLab Merge Request action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Project ID or Path project_id | string | Required | Project ID or Path. Example: 123 |
Title title | string | Required | Title. Example: Fix login redirect |
Source Branch source_branch | string | Required | Source Branch. Example: fix/login |
Target Branch target_branch | string | Required | Target Branch. Example: main |
Description description | string | Optional | Description |
Assignee User ID assignee_id | string | Optional | Assignee User ID. Example: 5 |
Labels labels | string | Optional | Labels. Example: bug, review |
{"project_id": "e.g. 123","title": "e.g. Fix login redirect","source_branch": "e.g. fix/login","target_branch": "e.g. main","description": "{{trigger.description}}"}
{"iid": 1,"state": "opened","title": "Fix login","web_url": "https://gitlab.com/group/project/-/merge_requests/1"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.