Short answer: Drop the "Shopify → List Collections" 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 |
|---|---|---|---|
Limit limit | string | Optional | Number of collections (max 250) |
Title title | string | Optional | Filter by exact title match |
Product ID product_id | string | Optional | Shopify product ID — numeric. Find via List Products. |
{"limit": "50","title": "{{trigger.title}}","product_id": "e.g. 123456789"}
{"custom_collections": [{"id": 841564295,"title": "Summer Sale","handle": "summer-sale","body_html": "<p>Hot summer deals</p>","sort_order": "best-selling","published_at": "2025-06-01T00:00:00-04:00","products_count": 12}]}
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.