Short answer: Drop the "Slack → Raw API Request" 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 |
|---|---|---|---|
HTTP Method method | options | Optional | HTTP Method. Options: POST, GET |
Endpoint endpoint | string | Required | Slack API method name (without the https://slack.com/api/ prefix). |
JSON Body body | json | Optional | JSON request body (for POST). Pass {} for GET. |
{"method": "{{trigger.method}}","endpoint": "chat.postMessage","body": "e.g. Hi there, thanks for reaching out."}
{"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.