Connecting apps to channels

Every app you add to Yeethook can be connected to one or more Slack channels. Connections control which events go where.

How connections work

A connection links one app to one channel. When Yeethook receives an event for that app, it checks which channels are connected and delivers the event to each one. If no channels are connected, the event is logged but not delivered.

You can optionally add an event type filter to each connection. Without a filter, all events for that app go to that channel. With a filter, only the selected event types are delivered.

Connecting from the app side

Open the actions menu on any app card (Apps page) and click Channel connections. A sheet opens showing all connected channels. From here you can:

• Connect a new channel — select a channel from the dropdown and click Connect.
• Disconnect a channel — click the disconnect button next to any connected channel.
• Edit event filter — click the filter icon next to a connection to choose which event types are forwarded to that specific channel.

Connecting from the channel side

Open the actions menu on any channel card (Channels page) and click Manage connections. A detail sheet opens showing all connected apps. From here you can:

• Connect a new app — select an app from the dropdown and click Connect.
• Disconnect an app — click the disconnect button.
• Edit event filter — filter which event types this app sends to this channel.

Event type filters

By default, a connection forwards all event types the app is subscribed to. If you add a filter, the connection only forwards the selected types. The filter selector shows the same category-based event type list as the app's event subscriptions, but limited to the types the app is actually subscribed to.

This is how you set up routing like "crashes to #bugs, reviews to #releases":

1. Connect your app to the #bugs channel. Edit the filter to only include crash and feedback event types.
2. Connect the same app to the #releases channel. Edit the filter to only include version state and build processing events.

Common routing patterns

Single channel. Connect all apps to one channel with no filters. Every event lands in the same place. Simple and works well for small teams.

By concern. Route events by what they mean to your team. Crash reports and TestFlight feedback to #bugs, app review and build processing to #releases, subscription events to #revenue.

By app. Give each app its own channel. Useful when different teams own different apps and only want their own events.

Hybrid. Combine approaches. Route crash reports from all apps to a shared #bugs channel, but give each app its own channel for everything else.