Does the Slack integration use official Slack OAuth?

Yes. The integration uses Slack's official OAuth 2.0 authorization flow. You authorize the WunderGraph Cosmo app through the standard Slack permissions dialog.

What Slack permissions does the integration require?

The integration requests permission to post to the channel you select during authorization. It does not access messages, files, or other channels.

Can I send notifications to a private channel?

Yes, if you authorize the integration with access to that channel during the OAuth flow.

Can I have multiple Slack integrations?

Yes. You can create multiple named Slack integrations per organization, each pointing to a different channel with a different event subscription. This lets different teams receive the events relevant to them.

What events can trigger Slack notifications?

The current event type is FEDERATED_GRAPH_SCHEMA_UPDATED. When this event fires, any Slack integration subscribed to it posts a notification to its configured channel.

Do I need to write any code?

No. The entire setup is done through Cosmo Studio UI. Click "Integrate," authorize via Slack, name the integration, select events, and save.

Does this work with Slack Enterprise Grid?

Yes. The integration works with any Slack workspace, including Enterprise Grid, subject to the workspace's own app installation policies.

Slack Integration for Federated GraphQL | Cosmo by WunderGraph

The problem

Teams live in Slack. Schema alerts don't.

Engineers check Slack, not dashboards. Getting federation events there without building custom infrastructure has been harder than it should be.

Building a Slack bot takes significant engineering time

A custom bot needs OAuth setup, message formatting, hosting, and ongoing maintenance. For something as common as schema change notifications, that time is wasted.

Routing webhooks through middleware adds complexity

Sending webhooks to a middleware layer that reformats and posts to Slack introduces another failure point. If the middleware goes down, notifications stop.

Teams miss changes because they live in Slack

Engineers check Slack, not dashboards. If schema change alerts land anywhere else, they get ignored until something breaks.

Our solution

Native Slack integration with zero code

Cosmo connects directly to the Slack API using official OAuth 2.0. Authorize once, select a channel, subscribe to events. Notifications land in Slack the moment a schema change occurs.

From click to notifications in 2 minutes

In Cosmo Studio, go to the Slack integrations section and click "Integrate".
You are redirected to Slack to authorize the WunderGraph Cosmo app.
Select the channel where you want notifications to appear.
After authorization, name the integration and choose which events to subscribe to.
Cosmo posts formatted notifications to your channel via the Slack API when subscribed events occur.
Add more integrations to route different events to different channels or teams.

No code. No middleware. No infrastructure to maintain.

Slack Integration

Before & After

Before Cosmo	With Cosmo
Building a custom Slack bot for schema notifications	Native one-click integration, no code required
Routing webhooks through middleware to Slack	Direct Slack API connection, no intermediary
Maintaining bot infrastructure	Zero maintenance overhead
Separate Slack setup per team	Multiple named integrations per organization, each independently configured

vs. alternatives

Cosmo vs. building your own

	Cosmo	Webhook + middleware	Custom bot
Setup time	2 minutes	30+ minutes	Hours/days
Code required	None	Some	Significant
Maintenance	None	Medium	High
Official OAuth	Yes	No	Yes
GraphQL-aware messages	Yes	Requires custom formatting	Requires implementation

How Cosmo Slack integration works

01

OAuth 2.0. Official Slack flow.

Authorize

Click "Integrate" in Cosmo Studio. Slack redirects you through the official OAuth 2.0 flow. Authorize the WunderGraph Cosmo app and select a channel.

02

Named. Event-filtered.

Configure

Name the integration for easy identification. Select which event types it should receive. A single integration can cover all events, or you can narrow it to specific ones.

03

Slack API direct. Sub-second.

Receive

When a subscribed event occurs, Cosmo posts a formatted notification directly to your chosen channel via the Slack API. No middleware, no relay.

04

Multiple integrations per org.

Scale

Add more integrations for different teams or channels. Each integration is independently named, configured, and subscribed. Different teams receive the events they care about.

What's included

Everything in the Slack integration

OAuth, channel selection, event filtering, and multi-channel routing. Nothing to install or maintain.

Official OAuth 2.0

Authorization goes through Slack's official OAuth flow. The WunderGraph Cosmo app requests only the permissions needed to post to the channel you select.

Any channel, any workspace

Public or private channels. Standard Slack workspaces or Enterprise Grid. Any channel you can authorize the app to post to.

Multiple named integrations

Each integration has its own name, channel, and event subscription. Route different events to different channels. Give each one a descriptive name so teams know what to expect.

Zero maintenance

There is no bot to host, no middleware to keep running, and no credentials to rotate. Cosmo manages the Slack API connection.

Get schema changes in Slack in 2 minutes

Authorize the integration in Cosmo Studio. Notifications land in your channel the moment a schema event fires.

Start Free Read the Docs

Get federated graph notifications directly in Slack