Short answer: Drop the "Canny → List Posts" 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 |
|---|---|---|---|
Board ID boardID | string | Required | Board ID |
Sort sort | options | Optional | Sort. Options: Newest, Top, Trending |
Limit limit | number | Optional | Limit |
{"boardID": "{{trigger.boardID}}","sort": "{{trigger.sort}}","limit": "{{trigger.limit}}"}
{"posts": [{"id": "post123","score": 42,"title": "Add dark mode","status": "open","commentCount": 5}],"hasMore": true}
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.