PERSONAL PRODUCTIVITY
Answer decision-history questions in Slack from the register
Lets anyone ask a plain-English question in Slack about past decisions; an AI searches the Postgres decision register and replies with the matching decisions, their rationale.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack app mention or DM with a questionSlack
- ActionParse question into search terms with OpenAIOpenAI
- ActionQuery Postgres decision registerPostgres
- LogicHandle no-results fallback
- ActionCompose grounded answer with OpenAIOpenAI
- OutputReply in Slack with answer and source linksSlack
What it does
Turns your decision register into a question-answering assistant inside Slack. Someone @-mentions the bot asking "why did we drop the legacy billing flow?" and it searches the Postgres register, retrieves the relevant decisions, and replies with the answer plus the original rationale, owner, and a link back to the source thread.
When to use it
Use it once you have a populated register and want answers without anyone opening Notion or writing SQL. Perfect for onboarding new hires, settling "didn't we already decide this?" debates, and surfacing the reasoning behind past calls on demand.
How it works
- 1A Slack app mention or DM triggers the workflow with the user's question.
- 2An OpenAI step turns the question into search terms and filters.
- 3The workflow queries the Postgres decision register for matching entries.
- 4A logic step handles the no-results case with a helpful fallback message.
- 5An OpenAI step composes a grounded answer citing the matched decisions, owners, and dates.
- 6The reply is posted in Slack with permalinks to the original decision threads.
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.