PERSONAL PRODUCTIVITY
Dropbox naming-convention auto-corrector with Slack rename log
Watches a Dropbox folder for new files, renames any that violate your naming convention to the canonical format.
How it runs
The automated pipeline, trigger to output.
- TriggerDropbox file-added webhook on watched folderDropbox
- LogicNormalize filename to canonical convention
- LogicSkip if name already compliant
- ActionRename file in Dropbox to canonical nameDropbox
- OutputPost old/new name + rule to SlackSlack
What it does
New files dropped into a watched Dropbox folder get checked against your naming convention (date prefix, project code, separators). Files that drift are renamed in place to the canonical pattern, and every rename is announced in Slack with the old and new name plus the rule that fired.
When to use it
Use it when a shared Dropbox folder collects uploads from many people and filenames keep arriving inconsistent — spaces instead of hyphens, missing date prefixes, wrong project codes. Instead of nagging the team, the workflow fixes names automatically and keeps a transparent log so nobody is surprised by a moved file.
How it works
- 1A Dropbox webhook fires when a file is added to the watched folder.
- 2The convention rules normalize the filename — lowercasing, swapping spaces for hyphens, and enforcing the `YYYY-MM-DD_projectcode_description` shape.
- 3A check compares the proposed name to the original; compliant files exit early and do nothing.
- 4For drifted files, Dropbox renames the file to the canonical name.
- 5Slack receives a message listing the old name, new name, and the specific rule that triggered the correction.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.