Skip to main content

Communication

Communication integrations are the channels AI Expedite reads from and writes to on your behalf — email and chat. Two are supported today: Gmail for email and Discord for community / team channels. Both pair with the email and discord system-agent hooks at Agents → System Agents, where you decide which agent answers each event.

📷 Screenshot: Communication-integration rows on Settings → Integrations.

Gmail​

Lets the platform send email on your behalf and (with the inbound surface still in development) read inbound mail for triage.

Connecting​

Two paths converge:

  • From Launch → Communication → Gmail — connect inline from the page that uses Gmail most heavily.
  • From Settings → Integrations — the Gmail row exposes the same OAuth handshake.

Both routes hand you Google's standard consent flow. After consent, the connected account shows up in the Gmail tab's Connected Accounts list with the date it was linked. Multiple Gmail accounts per workspace is supported — useful when you have separate support@ and marketing@ aliases.

What it powers​

  • Outbound mail — the Communication agents draft and send through whichever Gmail account you configure on each agent's binding.
  • The email.reply system hook — fires when an author asks AI to draft a reply; the bound agent reads the thread context and composes.
  • The email.classify system hook — fires automatically as inbound mail arrives, tagging it for routing.
  • The email.received system hook — fires on inbound mail; default agent reviews the email, decides whether it needs a human, and writes a summary into Inbox.
  • Inbox triage view — currently a "coming soon" placeholder on the Gmail tab; the underlying webhook plumbing is connected and producing events.

Removing an account​

The remove button on each row revokes the OAuth grant and stops the workspace sending or reading through that account. Past sent messages on Gmail's side are untouched; only the integration link is severed.

Discord​

Connect a Discord guild so AI Expedite can post launch announcements, support replies, and changelog updates into your channels — and so you can read those channels from within the workspace.

Connecting​

  • From Launch → Communication → Discord — connect inline.
  • From Settings → Integrations — same OAuth handshake.

Discord's flow has two sub-pieces: an OAuth grant for your user, and a bot install into the guild(s) you want the workspace to post into. Both are walked in the same modal.

Multiple Discord accounts (separate guild memberships) per workspace is supported.

What it powers​

  • Channel viewer — the account → guild → channel pickers in the Discord tab, with messages rendered in the right pane.
  • Agent-posted bot messages — when a Communication agent or social agent publishes into a Discord channel, the messages render with a small bot badge so you can tell them apart from human posts.
  • Webhook events — message-received, reaction-added, member-join events surface in Inbox under the Integrations category.
  • System Discord noise — joins, role changes, channel creates render demoted in the channel viewer so they don't crowd the real conversation.

Per-guild scoping​

The bot install is scoped to specific guilds; you choose which during the install. To add more guilds later, re-run the install flow and pick the additional guild(s) — the existing connections aren't disturbed.

Adding more channels​

Slack, Microsoft Teams, and other chat platforms aren't connected today. The communication abstraction is generic enough to add adapters without UI rework — when those adapters land, they slot into the same Communication tab pattern.