Slack and Discord Can Now Be Workflow Actions

Two new action steps land in the Workflows editor: slack.chat_post_message and discord.webhook_send. Add either one to a workflow and it will post a message to a channel — the last step in an approval chain, a notification when a run fails, a daily summary, anything you'd otherwise be copying into chat by hand.

No OAuth, no platform credential

Both actions work the same simple way: you paste in your own webhook URL — a Slack Incoming Webhook, or a Discord channel webhook — the same way you'd already fill in a URL field on an http.request step. Piskes never asks for a Slack or Discord login, never stores an app credential for either platform, and never sees anything beyond the webhook URL itself, which is exactly what it already was: a secret you control on your side, not ours. Every request these steps make goes through the same SSRF-safe URL policy that governs the generic http.request action, so a webhook URL is checked and fetched the same careful way a hand-written HTTP call is.

Why these aren't AI Agent tools

If you've used AI Agent's connector tools for things like Stripe or HubSpot, you might expect Slack and Discord to show up there too. They don't, on purpose. AI Agent's connector catalogue is deliberately read-only today — a design decision enforced in the code itself, not just documentation — reserved for the agent's own tool-calling surface until a write capability there gets its own separate review. Posting a message is a write, so these two land as workflow-author-facing automation steps instead, alongside http.request, not as something an AI agent can trigger on its own mid-conversation.

Available now

Because the Workflows editor's action catalogue is served from the backend, no update was needed on your end to see these — open the step picker on any workflow and Slack and Discord actions are already there, ready to configure with a webhook URL and a message.