Chat channels: assigning work and getting results

Slack, Discord, Jandi and KakaoWork all follow **the same rules.** There are two directions, and **you set them up separately.** One or both is fine.

**1. Assigning work from a channel**

Mention your staff in a channel and work starts.

@Bosskit pull together this week's revenue as a table

You get a reply right there: "Work started". If it couldn't start, **the reason comes back too**: not enough credits, you just asked the same thing, quiet hours, or too many jobs already running. Nothing goes silent.

One thing is needed: **invite your staff to the channel.** Messages in channels they aren't in never reach us.

You don't have to decide what runs. The right team picks it up from what you said. If it isn't sure, it asks back, and you put the team name in front and say it again. If a channel is only ever used for one kind of job, you can pin a single workflow to it on the integrations screen.

**2. Getting results in a channel**

This is the easy one to miss. **Finishing a job does not automatically post to your channel.** It posts only when the workflow ends with a **publish** step pointed at that channel.

Without that step, results are saved to Artifacts only. That's not a fault. That's how it works. Add a publish step if you want results in the channel too.

**Where to check**

- Did work start from a channel, and if not why → the **run history** under Work > Automation. It keeps **what didn't start and the reason**, not just what did - Something made but never delivered to a channel → Artifacts says so on the item - What went outside and when → the audit log

How each service connects (one login, or pasting a URL) is written on its card in Integrations.