Write a Monday status from ticket titles
n8n handles this as a draft: Done, next, and blocked, using only the titles I paste. No invented progress. Do not post in Slack.
Unverified · docs.n8n.io · 16 Oct 2026
Loading the catalog…
Loading the catalog…
An n8n agent reads one Slack channel, classifies messages, and posts a digest only to you. It does not reply in the channel.
n8n's build-and-manage-agents doc says agents can take actions in Slack and that the feature is in preview. An admin can disable agents instance-wide.
Post the digest to your own DM or a private channel, not back into the source.
Run it on yesterday's messages before you add the schedule.
Preview software can change. Keep a human scan for real incidents until the classes look right.
These are editorial labels so you can compare playbooks. They are not measurements.
No. Status is unverified. Paste the prompt, keep the version that worked, and do not treat the time or cost lines as measurements.
n8n's docs say to use an agent when the work is too open-ended for a fixed path. Classification with a digest fits that. A pure keyword route can stay a normal workflow.
Official documentation URL, checked when this seed was written. The prompt and steps are an original AI Playbook Gems playbook, not a quotation of a customer story, and have not been re-run.
Machine-readable copy: JSON
n8n handles this as a draft: Done, next, and blocked, using only the titles I paste. No invented progress. Do not post in Slack.
Unverified · docs.n8n.io · 16 Oct 2026
An n8n agent uses a sheet as its knowledge source and answers in a private chat. The sheet stays read-only.
Unverified · docs.n8n.io · 6 Oct 2026
n8n handles this as a draft: Billing, bug, how-to, and unknown. One sentence why. Do not reply to customers.
Unverified · docs.n8n.io · 16 Oct 2026