PERSONAL PRODUCTIVITY
Log Slack decisions to a Postgres register on /decided
Detects a decision keyword or slash-style phrase in Slack messages, parses the decision and owner.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Slack message in monitored channelsSlack
- LogicMatch decision marker (e.g. DECISION:)
- ActionNormalize fields with OpenAIOpenAI
- ActionInsert row into Postgres decisions tablePostgres
- OutputReply in Slack with new record IDSlack
What it does
Watches your channels for an explicit decision marker — a message starting with "DECISION:" or a tagged phrase — then structures it and stores it in a Postgres table. Because the source of truth is a real database, you can build dashboards, search, and reports on top of your decisions instead of scrolling chat history.
When to use it
Best for engineering and ops teams that already run internal tooling on Postgres and want decisions queryable alongside other operational data. Use it when you need decisions in a system you control, with stable schema and SQL access, rather than a SaaS document.
How it works
- 1A Slack message event fires on new messages in monitored channels.
- 2A logic step matches the decision marker and ignores everything else.
- 3An OpenAI step normalizes the text into decision, rationale, owner, and tags.
- 4The workflow inserts a row into the Postgres `decisions` table with the author, channel, timestamp, and permalink.
- 5A confirmation reply posts in Slack with the new record ID so people can reference it later.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.