Five workflow automations delivered for Chimpy

Five workflow automations delivered for Chimpy: a Wispr Flow recap to Slack, a twice-daily digest of Slack and email, invoice PDFs filed to Drive, dictation cleanup, and a Friday summary of the week and open items. The project was completed and received a 5.0/5 Upwork review in September 2026. The original estimate of roughly 5 to 6 hours a week covers only the first four workflows. The arithmetic is below; measured savings are not available yet.

Who Chimpy is, and what they asked for

Chimpy calls itself Europe's largest powerbank rental service. Zürich, since 2013, reusable solar-charged powerbanks rented and returned through retail. Their own page says they've made more than 10 million rentals. Inside, the team runs on Google Workspace for meetings, mail and files, Slack for talk, and Wispr Flow for dictation. Ordinary tools. The gaps are between them.

A team lead there originally sent me a brief with four items. The Friday Weekly Summary became the fifth delivered workflow. I'm quoting the parts that matter, in their words, because a brief this clear makes the work easier to scope.

On meeting recaps:

"Once that recap is ready, I can post it to Slack, either a specific channel (e.g. 'marketing') or a 1:1 DM with a specific person, in one or two clicks maximum."

On the daily noise:

"An automation that runs twice a day and compiles a digest of: Slack messages I received or was tagged in; work-related emails. LinkedIn is a nice-to-have. Flag if it's feasible given LinkedIn's API restrictions, but Slack and email are the priority and must work."

On invoices:

"Invoices arrive either by email or through various SaaS tools I use. I need these PDFs automatically detected and uploaded into a specific Google Drive folder, without me manually downloading or uploading anything."

On dictation:

"Right now I manually paste the transcript into Claude and ask it to rewrite it, then copy it out again. I want this collapsed into a single click."

Notice what's not in there. No AI strategy. No platform. Four leaks, each one a thing they do by hand today. That's the brief I'd want from you.

The build, in the order I'm doing it

Each one is a small workflow, scheduled or event-driven, that talks to Google Workspace and Slack through their official APIs, with a language model for the summarising and rewriting steps. I use Claude for those. The order below is mine, not the brief's. Each step builds a part the next one reuses.

1. Dictation cleanup, first

Smallest build, used most often. A hotkey takes the text you just dictated, sends it with a short style guide built from the client's own past messages, and returns the tightened version in a small review window. One more key pastes it. Wispr Flow already strips filler words and can rewrite selected text by voice. What the custom build adds is one house style, in one key, with a look before it goes.

It went first for two reasons. The client feels it on day one, twenty times a day. And building that style guide teaches me how they write, which the recap and the digest need too. What it can't do: know what you meant when the transcript heard Tuesday as Thursday. That's why the review window stays.

Full write-up: cleaning up Wispr Flow dictation with one key.

2. Meeting recap to Slack, second

Jari Brontesi, marketing manager at Chimpy, dictates the recap in Wispr Flow. The workflow transcribes it in the structure and tone he wants, then automatically pastes the result into his Slack account. The useful part is the whole handoff: spoken notes become a familiar, readable recap in the place his team already works. This is the current workflow; the earlier Google Meet and shortcut design has been replaced.

Full write-up: Wispr Flow recaps to Slack.

3. The twice-daily digest, third

A scheduled trigger fires at 09:00 and 14:00 in the client's time zone, not the server's. On a self-hosted n8n instance the default is New York unless you set it, and I've seen a digest land at three in the afternoon because nobody did. It pulls Slack DMs and mentions since the last run, then Gmail threads since the last run. Polling on a schedule, not push: Gmail's push route needs Pub/Sub and a watch renewed every seven days, and for a twice-a-day digest that's machinery for nothing. The model then writes one line per sender: who, what they want, what they're waiting on. Every line carries a permalink to the Slack thread or the Gmail thread, so you jump straight there. It's third because it's the biggest, and because the summaries need a few real weeks of tuning before they're trusted.

Full write-up: the twice-daily Slack and email digest.

4. Invoice PDFs to Drive, last

Watch the inbox for PDFs that look like invoices: a sender allowlist, subject words, the text inside the PDF. Add scheduled pulls from the SaaS tools that expose invoices. Rename to a convention, date, vendor, amount. Upload into one Drive folder through the parents field, and skip duplicates. It never pays anything and never deletes anything. It's last not because it's hard but because a mistake here costs most, and the allowlist is better built from a month of real invoices than from a guess.

Full write-up: saving invoice PDFs to Google Drive automatically.