HumDay

Automate Discord

HumDay reads Discord’s own published API description and derives 242 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Discord

What Discord is

Discord is a voice, video and text communication platform organised into servers and channels, with messages, threads, roles, webhooks and application commands.

API host: discord.com

What HumDay can do in Discord

139 documented operations change something in Discord. The 64 most useful are listed here.

  • PUTUpdate the target users for an existing invite./invites/{code}/target-users
  • PUTSet a voice channel's status./channels/{channel_id}/voice-status
  • POSTCreate an exception to a recurring guild scheduled event/guilds/{guild_id}/scheduled-events/{guild_scheduled_event_id}/exceptions
  • PUTUpdate the external moderation metadata for a lobby message./lobbies/{lobby_id}/messages/{message_id}/moderation-metadata
  • DELETEDeletes the specified lobby if it exists./lobbies/{lobby_id}
  • PUTUpdate the external moderation metadata for a user message (DM)./partner-sdk/dms/{user_id_1}/{user_id_2}/messages/{message_id}/moderation-metadata
  • PUTModifies the incident actions of the guild/guilds/{guild_id}/incident-actions
  • DELETEDelete an exception to a recurring guild scheduled event/guilds/{guild_id}/scheduled-events/{guild_scheduled_event_id}/exceptions/{exception_id}
  • PATCHModify an exception to a recurring guild scheduled event/guilds/{guild_id}/scheduled-events/{guild_scheduled_event_id}/exceptions/{exception_id}
  • PATCHApprove or reject guild join request/guilds/{guild_id}/requests/{request_id}
  • POSTUpdate channels/users/@me/channels
  • POSTUpdate messages/channels/{channel_id}/messages
  • PATCHUpdate @me/users/@me
  • POSTUpdate send soundboard sound/channels/{channel_id}/send-soundboard-sound
  • DELETEDelete channel id/channels/{channel_id}
  • PATCHUpdate channel id/channels/{channel_id}
  • POSTUpdate bulk delete/channels/{channel_id}/messages/bulk-delete
  • POSTUpdate lobbies/lobbies
  • PUTUpdate lobbies/lobbies
  • DELETEDelete message id/channels/{channel_id}/messages/{message_id}
  • PATCHUpdate message id/channels/{channel_id}/messages/{message_id}
  • POSTUpdate stage instances/stage-instances
  • PATCHUpdate channels/guilds/{guild_id}/channels
  • POSTUpdate channels/guilds/{guild_id}/channels
  • POSTUpdate messages/lobbies/{lobby_id}/messages
  • POSTUpdate typing/channels/{channel_id}/typing
  • POSTUpdate invites/channels/{channel_id}/invites
  • POSTUpdate threads/channels/{channel_id}/threads
  • POSTUpdate webhooks/channels/{channel_id}/webhooks
  • POSTUpdate followers/channels/{channel_id}/followers
  • POSTUpdate scheduled events/guilds/{guild_id}/scheduled-events
  • PATCHUpdate channel linking/lobbies/{lobby_id}/channel-linking
  • PATCHUpdate @me/applications/@me
  • POSTUpdate token/partner-sdk/token
  • DELETEDelete message id/channels/{channel_id}/messages/pins/{message_id}
  • PUTUpdate message id/channels/{channel_id}/messages/pins/{message_id}
  • POSTUpdate threads/channels/{channel_id}/messages/{message_id}/threads
  • DELETEDelete guild id/users/@me/guilds/{guild_id}
  • POSTUpdate crosspost/channels/{channel_id}/messages/{message_id}/crosspost
  • DELETEDelete reactions/channels/{channel_id}/messages/{message_id}/reactions
  • DELETEDelete code/invites/{code}
  • PATCHUpdate guild id/guilds/{guild_id}
  • PATCHUpdate lobby id/lobbies/{lobby_id}
  • DELETEDelete @me/channels/{channel_id}/thread-members/@me
  • PUTUpdate @me/channels/{channel_id}/thread-members/@me
  • DELETEDelete webhook id/webhooks/{webhook_id}
  • PATCHUpdate webhook id/webhooks/{webhook_id}
  • POSTUpdate bot/partner-sdk/token/bot
  • DELETEDelete channel id/stage-instances/{channel_id}
  • PATCHUpdate channel id/stage-instances/{channel_id}
  • PATCHUpdate application id/applications/{application_id}
  • DELETEDelete message id/channels/{channel_id}/pins/{message_id}
  • PUTUpdate message id/channels/{channel_id}/pins/{message_id}
  • DELETEDelete user id/channels/{channel_id}/recipients/{user_id}
  • PUTUpdate user id/channels/{channel_id}/recipients/{user_id}
  • DELETEDelete user id/channels/{channel_id}/thread-members/{user_id}
  • PUTUpdate user id/channels/{channel_id}/thread-members/{user_id}
  • DELETEDelete overwrite id/channels/{channel_id}/permissions/{overwrite_id}
  • PUTUpdate overwrite id/channels/{channel_id}/permissions/{overwrite_id}
  • POSTUpdate prune/guilds/{guild_id}/prune
  • PATCHUpdate roles/guilds/{guild_id}/roles
  • POSTUpdate roles/guilds/{guild_id}/roles
  • POSTUpdate emojis/guilds/{guild_id}/emojis
  • PATCHUpdate widget/guilds/{guild_id}/widget

What HumDay can read from Discord

These are the operations a schedule or a trigger can watch.

  • GETGet the target users for an invite./invites/{code}/target-users
  • GETGet the target users job status for an invite./invites/{code}/target-users/job-status
  • GETGet a list of users subscribed to a guild scheduled event exception/guilds/{guild_id}/scheduled-events/{guild_scheduled_event_id}/{guild_scheduled_event_exception_id}/users
  • GETList join requests for guild, optionally filtered by application status/guilds/{guild_id}/requests
  • GETReturns all subscriptions containing the SKU, filtered by user./skus/{sku_id}/subscriptions
  • GETGet the count of users subscribed to a guild scheduled event/guilds/{guild_id}/scheduled-events/{guild_scheduled_event_id}/users/counts
  • GETGet a subscription by its ID./skus/{sku_id}/subscriptions/{subscription_id}
  • GETRead messages/channels/{channel_id}/messages
  • GETRead @me/users/@me
  • GETRead search/guilds/{guild_id}/messages/search
  • GETRead pins/channels/{channel_id}/messages/pins
  • GETRead user id/users/{user_id}
  • GETRead search/channels/{channel_id}/threads/search
  • GETRead channel id/channels/{channel_id}
  • GETRead guilds/users/@me/guilds
  • GETRead connections/users/@me/connections
  • GETRead gateway/gateway
  • GETRead sticker packs/sticker-packs
  • GETRead message id/channels/{channel_id}/messages/{message_id}
  • GETRead pins/channels/{channel_id}/pins
  • GETRead channels/guilds/{guild_id}/channels
  • GETRead messages/lobbies/{lobby_id}/messages
  • GETRead invites/channels/{channel_id}/invites
  • GETRead webhooks/channels/{channel_id}/webhooks
  • GETRead soundboard default sounds/soundboard-default-sounds
  • GETRead scheduled events/guilds/{guild_id}/scheduled-events
  • GETRead @me/oauth2/@me
  • GETRead thread members/channels/{channel_id}/thread-members
  • GETRead bot/gateway/bot
  • GETRead new member welcome/guilds/{guild_id}/new-member-welcome
  • GETRead keys/oauth2/keys
  • GETRead regions/voice/regions
  • GETRead userinfo/oauth2/userinfo
  • GETRead @me/applications/@me
  • GETRead search/guilds/{guild_id}/members/search
  • GETRead code/invites/{code}

How automating Discord works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Discord account.
  4. Grant access, then go live. You approve the specific Discord operations it may use — and only those.

Popular Discord integrations

Connect Discord to the tools people pair it with most.

Automate Discord with these

Categories

Questions about Discord automation

Can HumDay connect to Discord?
Yes. HumDay reads Discord's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 242 operations are documented.
Do I need to write code to automate Discord?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Discord account.
What can HumDay do in Discord?
139 of the 242 documented operations change something in Discord, and 103 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Discord account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Discord is held behind that approval.

Where this came from

The operations above are read from the API description Discord publishes themselves at raw.githubusercontent.com/discord/discord-api-spec/main/specs/openapi.json. Descriptions are the provider’s own words, not ours.