SUMMARIZATION

On-demand card decision capture with Coda dedupe

An inbound webhook (from a Trello Power-Up button or external trigger) summarizes a specific card's thread and upserts a decision-log row in Coda.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerInbound webhook with card IDHTTP webhook
  • ActionFetch card comments and detailsTrelloTrello
  • ActionSummarize current decision and revision noteOpenAI
  • LogicCheck Coda for existing card rowCodaCoda
  • OutputUpsert decision row in Coda trackerCodaCoda

What it does

Fire a webhook with a Trello card ID and this workflow summarizes that card's comment thread into a decision entry, then upserts it into a Coda tracker: it creates a new row the first time and updates the existing row on later calls. This keeps exactly one current decision record per card instead of duplicates.

When to use it

Use it when you want decision capture on demand, triggered from a Trello Power-Up button, a slash command, or another tool, rather than on a fixed event. Best for teams that revise decisions mid-flight and need the Coda log to always reflect the latest call.

How it works

  1. 1An HTTP webhook receives a request carrying the target card ID.
  2. 2The flow fetches that card's comments and details from Trello.
  3. 3An OpenAI call produces the current decision, rationale, and revision note.
  4. 4A logic step checks Coda for an existing row matching the card ID.
  5. 5The flow upserts the decision row in Coda, creating or updating in place.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect TrelloKanban boards for everything.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect CodaDocs, packs, automations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.