PERSONAL PRODUCTIVITY
Dropbox rename approval gate with Slack confirm buttons
When a new Dropbox file breaks the naming convention, the workflow proposes a corrected name and asks an owner to approve or reject it in Slack before renaming.
How it runs
The automated pipeline, trigger to output.
- TriggerDropbox file-added webhookDropbox
- LogicPropose canonical name; skip if compliant
- ActionPost Approve/Reject proposal to SlackSlack
- ActionReceive human decision via webhookHTTP webhook
- LogicBranch on approved vs rejected
- ActionRename file in Dropbox if approvedDropbox
- OutputPost outcome to Slack threadSlack
What it does
Instead of renaming silently, this workflow proposes a fix and waits. A drifted upload triggers a Slack message with Approve and Reject buttons showing the suggested canonical name. On approval, Dropbox performs the rename; on reject, the file is left untouched and the decision is recorded.
When to use it
Use it for folders where a wrong rename could break links or downstream references, so a person should sign off. It is the right middle ground when full automation feels too aggressive but manual renaming is too slow.
How it works
- 1A Dropbox webhook fires on a new file in the watched folder.
- 2The convention engine generates a proposed canonical name; compliant files exit early.
- 3An incoming webhook posts the proposal to Slack with Approve and Reject actions.
- 4The workflow pauses for the human decision delivered back via webhook.
- 5A branch routes the response: approved files are renamed in Dropbox, rejected ones are skipped.
- 6The outcome is posted back to the Slack thread for the record.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.