The team ships.
Customers hear about it.
On Friday afternoon a schedule reads the week’s commits, leaves out the internal work, and writes a short “What’s new” post in plain language for your customers. You approve or edit it with a note, and it’s posted to Slack. Quiet weeks post nothing.
- This week’s commits git log
- Write the post Claude API · sonnet
- Anything to announce? yes / no
- Review post you
- Post to Slack webhook
What the pipeline does for you
Written for customers
Refactors, CI, tests and dependency bumps are left out. Each change is described by what customers can now do.
Silent when there’s nothing to say
A week with no commits, or nothing customer-facing, skips the review and the post. The run still succeeds.
Marketing gets the final word
The post waits at an approval gate. Reject with a note like “lead with exports” and it’s rewritten.
Nothing to install for the reader
The post lands in a Slack channel, or anywhere else that takes a webhook, such as a newsletter tool through Zapier.
Four steps, once
- Import the Weekly what’s new pipeline and point its workspace at a clone of your repository.
- Describe your audience in its variables and add a Slack incoming webhook URL.
- Triggers → Add trigger → Schedule, with 0 15 * * 5.
- Click Run once to see this week’s post now.
The post is only as good as your commit messages, since they’re all the model sees. The docs show how to use merged pull request titles instead.
Same engine, different jobs
For engineering
Issues → pull requests
Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.
See how it runs →Schedule → Pull requestNightly maintenance
A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.
See how it runs →GitHub → CommentSpecs from vague issues
A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.
See how it runs →Beyond engineering
Support reply drafts
New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.
See how it runs →Webhook → CRMInbound lead research
Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.
See how it runs →Build your own
Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.