DOCUMENT OPS

Discord RFP Go/No-Go Triage Router

Scores each Discord-submitted RFP against your bid criteria and routes qualified opportunities to a Linear project while declining the rest with a logged reason.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Discord RFP attachmentDiscordDiscord
  • ActionExtract criteria fields with OpenAIOpenAI
  • LogicScore against go/no-go thresholds
  • ActionCreate Linear project + requirement issuesLinearLinear
  • OutputReply in Discord with go/no-go verdictDiscordDiscord

What it does

Applies your go/no-go rules to every incoming RFP and decides whether it's worth pursuing. Qualified RFPs become a Linear project with requirement issues; disqualified ones get logged so you keep a paper trail of what you passed on.

When to use it

Use it when RFP volume exceeds your capacity to bid on everything and you need consistent, criteria-based filtering instead of gut calls. Best for teams with clear minimum thresholds like deal size, region, or required certifications.

How it works

  1. 1A new RFP attachment in the Discord channel triggers the flow.
  2. 2OpenAI extracts deal size, deadline, required capabilities, and disqualifiers from the document.
  3. 3A logic branch scores the RFP against your configured thresholds and decides go or no-go.
  4. 4If go, a Linear project is created with one issue per requirement so the bid team can start immediately.
  5. 5If no-go, the decision and reason are recorded and the flow replies in Discord with the verdict either way.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  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.