How to automate your daily business brief to Slack
Read your connected tools each morning and send a brief with priorities, blockers, and sources to Slack.
Posted by
Related reading
How to install and use OpenCode plugins
Install an OpenCode plugin, check that it loaded, and use Plannotator to review a plan in your browser and send a specific change back to the agent.
How to create agents in OpenCode
Create primary agents and subagents in OpenCode. Add a Markdown file to your project, choose its mode, and run it with a working example.
How to connect an MCP server to OpenCode
Connect an MCP server to OpenCode, check its tools, and run a prompt that uses them. Includes configuration, authentication, and troubleshooting.
Ask Pipa to read your connected tasks, customer requests, and calendar, then send a morning brief to Slack.
The short version
Connect your tools, ask for a brief in Slack, and run it once. Check the sources. Then choose a time and channel and confirm the schedule preview.
Step 1. Install Pipa and connect your sources
Start with the Pipa Local install guide, then connect OpenCode to Slack. Add the tools you want in the brief with an OpenCode MCP server. Pipa can't read a tool you haven't connected.
Step 2. Ask for a brief and run it now
Name the tools and the Slack channel. Ask for a link to each item:
Give me a morning business brief in this Slack channel. Read [TASK_TOOL], [CUSTOMER_TOOL], and today's calendar. List my top three priorities, blockers with owners, and anything due today with its time. Link each item to its source. Keep it under 200 words. If a source can't be reached, name it and leave out its findings. Don't mistake a read failure for no activity. Don't invent items. Run it once now; don't schedule it yet.
Replace the bracketed names with your tools. Open the links in the first brief. If an item is missing, check the connection and your request before scheduling it.
Morning brief, Thu (illustration) Priorities 1. Reply to the renewal thread (customer inbox link) 2. Review the deploy checklist (task link) 3. Prep the 2pm call (calendar link) Blockers - Invoice approval waits on [OWNER] (accounting link) Due today - Renewal reply by 3pm (customer inbox link)
A real brief links to the items it read, not just the tools.
Step 3. Schedule the brief
Once the first brief looks right, say "send this every morning at 8am in #morning-brief, New York time." Check the time, timezone, and channel in the preview. Pipa doesn't create the routine until you confirm it.
For more ways to schedule work, see the OpenCode scheduling guide.
Local limits
Pipa Local runs on your computer, so keep it awake with Pipa running when the brief is due. Missed occurrences are skipped rather than backfilled. Managed profiles do not execute Local routines.
FAQ
How do I connect my tools?
I use Composio for my connections, but it isn't required. Pipa can use the MCP tools available to your OpenCode agent. Check that OpenCode can read each source before running the brief.
Can I send the brief to any Slack channel?
Yes, if Pipa is in the channel and your setup allows it. If you set a channel allowlist, include that channel. Check the destination in the schedule preview before you confirm it.
How do I test the brief before scheduling it?
Ask for the brief once in Slack and check its source links and priorities. The schedule preview checks the time and channel; it does not run the brief. After saving a routine, find its ID with pipa routine list and use pipa routine run ROUTINE_ID for one manual run without changing the schedule.