CommunicationReal-timeUpdated May 2026

Discord

Plug your Discord server into every workflow

Discord is the de-facto comms layer for communities, indie projects, open-source maintainers, web3 collectives, gaming guilds, and increasingly tight-knit work teams. Tiny Command treats your server like a first-class event source. Three triggers cover the moments a community grows or engages: New Message (filtered by channel or keyword), Member Joined (the welcome moment), and Reaction Added (the engagement signal). On the action side, Send Message, Create Thread, Add Reaction, Edit Message, Delete Message, List Guilds, List Guild Channels, and List Channels cover what a community-ops workflow actually needs to do. The integration uses Discord's bot scopes per guild, so you authorize a bot once per server, and the workflow only sees channels the bot has been added to. Common pattern: a Stripe purchase auto-grants a role and posts a welcome thread in the customer's onboarding channel, or a GitHub release announcement fans out to every server you maintain.

Connect Discord See 3 triggers

3triggers

8actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Discord does.

3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When member joined

Fires when a new member joins a Discord server. Used for welcome bots, auto-role assignment, or onboarding sequences.

See what it returns →

Trigger live

When new message

Fires when a new message is sent in a Discord channel. The standard inbound hook for bots, moderation, and message-driven workflows. Requires the message-content intent for non-mention messages.

See what it returns →

Trigger live

When reaction added

Fires when a reaction is added to a Discord message. Powers reaction-roles, voting, or "thumbs up to claim" automations.

See what it returns →

Actions

Do anything Discord can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Add Reaction	Adds an emoji reaction to a Discord message from the bot. Used as a lightweight ack or to seed a reaction-vote message.	3 fields	View →
Create Thread	Creates a new thread in a Discord channel, optionally attached to a source message. Used to keep topical discussion out of the main channel.	3 fields	View →
Delete Message	Deletes a message from a Discord channel. The bot can delete its own messages, or any message in channels where it has Manage Messages permission.	2 fields	View →
Edit Message	Edits an existing Discord message. The bot can only edit its own messages; great for updating status messages, vote tallies, or live counters without spam.	3 fields	View →
List Channels	Lists all channels in a Discord server (guild) with their type, name, and parent category. Used to populate a channel picker.	1 fields	View →
List Guild Channels	Lists all channels in a Discord server (guild). Functionally the same as List Channels; exists for naming consistency in older flows.	1 fields	View →
List Guilds	Lists all guilds (servers) the bot is a member of with name, owner, and member count. Required first step for any cross-server automation.	0 fields	View →
Send Message	Sends a message to a Discord channel via the bot, with optional embeds, components (buttons/select menus), and reply target. The default Discord notification action.	3 fields	View →

Recipes

Pre-built Discord workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Discord → Slack alerts

AI-triage every Discord event, ping the right channel only when it matters.

Discord → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Discord → Notion database

Turn Discord into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Discord once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Discord field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Discord integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Discord to Tiny Command?

Open the Tiny Command workflow builder, drop in a Discord node, and click Connect. Authorize Discord once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Discord triggers does Tiny Command support?

Tiny Command supports 3 real-time Discord triggers, including "Member Joined", "New Message", "Reaction Added". Each trigger fires within seconds of the event happening in Discord.

What Discord actions can I run from a workflow?

8 Discord actions are available out of the box, covering communication operations like "Add Reaction". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Discord integration real-time?

Yes. Member Joined and every other Discord trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Discord rather than on a polling schedule.

Do I need to write code to use Discord with Tiny Command?

No. Every Discord trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Discord API endpoint directly.

How much does the Discord integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Discord integration itself has no per-app surcharge.