Communication

Discord + StackGo

Discord and the compliance workflow around it.

Discord publishes 8 trigger events and 16 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Communication Across the workflow Not connected yet
What Discord is

Discord is an all-in-one voice and text chat for gamers.

Description supplied by Discord.

Where it fits

Across the workflow, not at a step

A chat or support tool does not sit at one step of a compliance workflow. It carries the workflow to the people who have to act on it — which is why it belongs here, and why pinning it to Intake or Monitor would be wrong.

A check can start from
  • Role Assigned to User
What StackGo sends to Discord

An outcome, never the client’s identity data. Discord would be told what happened; the verification detail stays in your system of record.

  • What happened
  • Who it was for
  • When
  • Where the record is

Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.

Everything else Discord publishes

Discord’s public integration surface

The rest of what Discord exposes on Zapier, beyond the ones above. This is the raw material a connector would use.

7 more events
  • New Message Posted to Channel
  • New User Added
  • New Reaction on Message (Legacy)
  • New Reaction on Message
  • New Forum Message
  • New Forum Post
  • New Mention
16 actions
  • Add Role
  • Create new Forum Post
  • Remove User Role
  • Rename Channel
  • Send Channel Message
  • Send Direct Message
  • Send message in Forum Post
  • Custom Actions (Beta)
  • API Request (Beta)
  • Find Channel
  • Find User
  • List Forum Channels
  • List Guild Roles
  • List Members
  • List of Emojis
  • List Text Channels (Includes Announcement Channels)

Names are Discord’s own, read from its public Zapier listing on 28 August 2026.

Questions

Common questions about Discord

What is Discord integration?

There is no StackGo connector for Discord yet. Discord publishes 8 trigger events and 16 actions through Zapier, including “Role Assigned to User”, so building one is realistic. Requests decide the build order.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

Discord sits beside the work, not inside it.

The compliance work happens in the five workflows below. Discord is where a check can start, or where the result lands.

Want Discord connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.