Short answer: Drop the "GitLab → List GitLab Issues" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
State state | options | Optional | State. Options: Open, Closed, All |
Labels labels | string | Optional | Comma-separated label names to filter by |
Per Page per_page | string | Optional | Per Page. e.g. "20" |
Order By order_by | options | Optional | Order By. Options: Created, Updated, Priority |
{"project_id": "e.g. 123","state": "{{trigger.state}}","labels": "e.g. bug, P1","per_page": "20","order_by": "{{trigger.order_by}}"}
[{"iid": 42,"state": "opened","title": "Fix CI","labels": ["bug"],"web_url": "https://gitlab.com/group/project/-/issues/42"}]
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.
Triggered by anything in the catalog. Free tier available. No credit card.