PERSONAL PRODUCTIVITY

Quick-Log a Decision via Slack Slash Command

A /decision slash command in Slack lets anyone instantly log a decision with owner and rationale; the workflow validates the input, records it in Coda.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • Trigger/decision slash command invokedSlack
  • ActionParse command into structured fields with OpenAIOpenAI
  • LogicOwner + decision present? Else return inline error
  • ActionWrite decision row to Coda registerCodaCoda
  • OutputPost confirmation card to Slack channelSlack

What it does

Gives the team a frictionless way to log a decision in the moment it is made. Type /decision followed by what was decided, and the workflow parses owner, rationale, and an optional decide-by date, writes a structured row to your Coda register, and drops a confirmation card in the channel so everyone sees it was captured.

When to use it

Use this when decisions happen in live conversation and you want capture to be a single command rather than a context switch. Perfect for fast-moving teams who will never open a separate tool but will type one slash command in Slack.

How it works

  1. 1A user invokes the /decision slash command in Slack, triggering the workflow via webhook.
  2. 2An OpenAI step parses the free-text command into structured fields: decision, owner, rationale, and optional deadline.
  3. 3A logic step checks for a missing owner or empty decision and returns an inline error prompting the user to retry if so.
  4. 4The validated decision is written as a new row in the Coda register with status Confirmed and the invoking user as the source.
  5. 5A confirmation message with the parsed fields is posted back to the originating Slack channel for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect CodaDocs, packs, automations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.