Discord Make integrationAutomate Discord with Make.

List Channel Messages pulls the recent messages of one channel into your scenario, one bundle per message, ready to be counted, archived or sent somewhere else.

Get a Message fetches one precise message, the one you point it at, and hands back what Discord holds on it.

Send a Message posts text into a channel, into a thread, or straight to one member. This is where most Discord scenarios end.

Edit a Message rewrites a message that is already posted, in place, rather than stacking a new one on top. The channel keeps one readable line instead of a pile of updates.

Delete a Message takes a post out of the channel. The scenario does the tidying, nobody scrolls back through the history by hand.

List Channel Invites hands you the invites that exist for one channel, with what Discord keeps on each of them, one at a time.

List Channels gives you the channels your bot can see on the server. It is the usual way to find the right one before another module writes into it.

Get an Invite reads one invite back. Make's documentation names the module without describing it, so the name is all anyone knows about it.

Delete an Invite removes a single invite link. Here too the documentation lists the module without a word of explanation: what a test shows you is what you get.

Create a Guild Channel opens a new channel on the server without anyone clicking through Discord. The scenario prepares the space and people just walk in.

Create a Channel Thread opens a thread instead of a whole channel. The conversation gets its own corner and the main channel stays readable. One request, one thread, and the scenario is the one that opens it.

Create a Channel Invite produces a fresh invite link for a channel, ready to go out by email, inside a message, or in a document.

Update a Channel changes a channel that already exists rather than creating one more. The scenario adjusts it, and the shape of the server stops depending on somebody's memory.

Delete a Channel takes a channel off the server. It is the last step of a clean-up scenario, not an everyday move.

Post a Reaction with an Emoji drops an emoji onto a message. It is the cheapest way a scenario has to say that it saw something go by.

Search Guild Members looks for members on the server and returns the ones that match, zero, one or several. This is the module for when you start from a name and not from an identifier.

List Guild Members walks through the members of the server your bot sits on and passes them to the next module, one by one. A search module like this one can hand back many bundles, or none at all.

List Guild Members with Reactions on Message tells you who reacted to a given message with a given emoji. The reaction becomes an attendance list.

Update a Guild Member changes what the server knows about one member, without a moderator opening Discord. The scenario updates while the team is on something else.

Add a Role to a Guild Member gives someone a role, and with the role everything that role opens on your server.

Remove a Role from a Guild Member takes the role away, and the access with it. This is the half of the job most communities forget.

List Guild Events returns the events planned on the server, so a scenario can read the calendar before it does anything else. It reads the agenda as data, not as something a person has to go and check.

Get a Guild Event brings back a single event, the one you already have in hand, with what Discord keeps on it. An action module like this one works on one item at a time.

Create a Guild Event puts a session on the server calendar, straight from wherever your dates already live. Nobody retypes a date twice, and nobody forgets to put the session in front of the community.

Update a Guild Event edits an event that is already published, which saves you the second announcement and the confusion that comes with it. The event already out there becomes the correct one, instead of sitting next to a correction.

Delete a Guild Event takes a cancelled session off the server calendar.

Create a Webhook Bot gives a channel its own voice: a small bot whose only job is to drop messages there. A webhook is an address that something outside comes to post to.

Send a Message by Webhook Bot publishes through the webhook bot you created rather than through your main connection. It is the counterpart of Create a Webhook Bot: one sets the voice up, this one uses it.

Delete a Webhook Bot removes that voice for good.

Update a Current Bot changes the bot behind the connection you are using, from inside a scenario rather than from Discord's own settings.

Make an API Call is the door to everything the other modules do not cover. It calls Discord's API directly, on the same connection and with the same authorization.