PERSONAL PRODUCTIVITY
Auto-Close Commitment Cards on Reply Detection
Watches incoming replies to threads where you made a promise, uses AI to decide whether the commitment was fulfilled.
How it runs
The automated pipeline, trigger to output.
- TriggerNew inbound reply in GmailGmail
- ActionFind matching open commitment card in Trello by threadTrello
- LogicStop if no open card matches the thread
- ActionJudge fulfillment with OpenAI (fulfilled / pending / unclear)OpenAI
- OutputMove card to Done or post review note to SlackSlack
What it does
When a reply lands in your inbox, this workflow matches it to an open commitment card by thread and asks an AI model whether the reply implies the promise was kept (the deliverable was sent, the question answered). If so, it moves the Trello card from "Promised" to "Done" and posts a one-line confirmation to Slack.
When to use it
Use it to keep a commitment board from rotting. Without auto-closing, cards pile up even after you deliver, and the board loses trust. This closes the loop automatically and only flags genuine ambiguity for you.
How it works
- 1A new inbound Gmail message triggers the run.
- 2A Trello step looks up open commitment cards matching the email thread reference.
- 3A logic gate ends the run if no open card matches the thread.
- 4An OpenAI step judges whether the reply indicates the commitment was fulfilled, returning fulfilled, pending, or unclear.
- 5On fulfilled, the Trello card is moved to the Done list; on unclear, it stays put and a Slack note asks you to review.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect TrelloKanban boards for everything.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Weekly Low-Attendance Recurring Meeting Auditor
Every Friday, scans the next week of recurring calendar events, flags those where confirmed attendance keeps dropping below a threshold.
Auto-decline focus-block invites unless the organizer is a VIP
Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…
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.
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.
Weekly Subscription Audit: Find Noisy Lists Worth Unsubscribing
Once a week, analyzes which mailing lists flooded your inbox and how rarely you opened 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.