Short answer: Drop the "Slack → Delete File" 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 |
|---|---|---|---|
File ID file | string | Required | Slack file ID (starts with F). Find via List Files. Not the filename. |
{"file": "e.g. F0123ABC456"}
{"ok": true,"raw": {}}
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.