Short answer: Drop the "Slack → List Files" 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 |
|---|---|---|---|
Filter by User user | string | Optional | Slack user ID (starts with U or W). Find via List Users. Not the username or display name. |
Filter by Channel channel | string | Optional | Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #. |
File Types types | string | Optional | Comma-separated types: all, spaces, snippets, images, gdocs, zips, pdfs. |
Max files count | number | Optional | Max files to return per page. |
{"user": "e.g. U0123456789","channel": "e.g. C0123456789","types": "images,pdfs","count": "{{trigger.count}}"}
{"ok": true,"raw": {},"count": 0,"files": []}
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.