Kiwi for Discord
Have the agent on a Kiwi step post its result to a Discord channel and open a thread for questions, through Discord's HTTP API.
- Your agent works in Discord through its own connection. Kiwi does not call Discord and never holds its credentials.
- A workflow skill can list Discord among the tools it requires. When you supply your agent's available tools to a skill check and Discord is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Discord, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Discord connection, with
report_configuration. - The agent submits links to its work in Discord as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Discord
- Post a message to a channel, or reply to an earlier message.
- Start a thread from a message, or a new thread in a forum channel, to keep a run's updates together.
- React to a message, for example to acknowledge a request.
- Post through a channel webhook, which needs only the webhook URL rather than a bot.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Discord
Give your agent access to the Discord API as its documentation describes. The credentials stay with your agent.
Example skill
Publish instructions like these as a workflow skill that lists Discord among its required tools.
Read the Discord channel ID and the release summary from the run's inputs. Post the summary to the channel with the pull request and run links. Start a thread from that message for questions about the release. Submit the message URL as the step's outputs. Answering questions in the thread is for the release owner. If Discord rejects the post for missing permissions, call report_blocker.