Back to Help Center

Inbound Channels

Inbound channels are entry points for calling Zemu AI workers from Slack, Discord, LINE WORKS, and other external chat tools. If a user wants to talk to Zemu from an external chat tool, configure it on the Inbound Channels page, not in the Triggers page.

Overview

Add and manage inbound routes that call AI workers from Slack and other external chat tools.

Basics

How to add a route

Open the Inbound Channels page, choose Slack, Discord, or LINE WORKS, and create a connection profile. After OAuth completes, add a Channel Route under that profile and configure the AI worker, response language, execution model, DM policy, group policy, channels, whether mention is required, and enabled state.

Selecting Slack channels

Slack and Discord Channel Routes select channels from lists fetched from the service. Users should not manually enter channel IDs. LINE WORKS can show a manual entry field when no channels are returned. Different channels can be routed to different workers.

Start and response rules

Separate routes that listen to normal channel posts from routes that require mentioning the Zemu app. DM policy supports open, allowlist, pairing, or disabled, and group policy supports all channels, selected channels, or disabled. Discord does not support DMs in this screen, so configure channel routes according to the page guidance.

Notifications, files, and route matching

Notification language and execution model are route-level settings. Slack attachments are presented to the worker up to five files and fetched only when needed. If multiple routes match one Slack post, Zemu prioritizes a worker name in the message; if unclear, it returns candidate workers rather than launching several.

Checklist

  1. Create the Slack or supported connection profile from the Inbound Channels page.
  2. Add a Channel Route and set channel name, AI worker, start condition, and model.
  3. Test `@Zemu /agents`, `@Zemu /help`, and mention-based execution from the real Slack channel.