Connect Discord and Figshare
Describe what you want to happen between Discord and Figshare in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Discord
242 documented operations. See all Discord operations
- 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
Figshare
136 documented operations. See all Figshare operations
- POSTCreate new Article
/account/articles - POSTCreate new Institution Account
/account/institution/accounts - POSTPOST Institution Curation Review Comment
/account/institution/review/{curation_id}/comments - POSTPublic Articles Search
/articles/search - POSTPublic Projects Search
/projects/search - POSTCreate project
/account/projects
How a Discord and Figshare automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Discord and Figshare, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Discord and OData for namespace microsoft.graphintegration
- Figshare and OData for namespace microsoft.graphintegration
- Cloudflare and Discordintegration
- Cloudflare and Figshareintegration
- Discord and NetBoxintegration
- Figshare and NetBoxintegration
- Discord and GitHubintegration
- Figshare and GitHubintegration
- Discord and Mistintegration
- Figshare and Mistintegration
Questions about connecting Discord and Figshare
- Can Discord connect with Figshare?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Discord to Figshare?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Discord and Figshare?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Discord and Figshare?
- Discord publishes 242 documented operations and Figshare publishes 136. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Discord or Figshare is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Discord and Figshare. Descriptions are each provider’s own words, not ours.