AI & RAG

Won-Deal Transcript Ingestion and Embedding Pipeline

On a nightly schedule, pulls newly closed-won opportunities from Salesforce, fetches their call transcripts, chunks and embeds them.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionQuery Salesforce for newly Closed Won deals + transcriptsSalesforce
  • LogicFilter empty transcripts and skip already-ingested deals
  • ActionChunk transcripts and generate embeddingsOpenAI
  • OutputUpsert vectors and deal metadata into SupabaseSupabaseSupabase

What it does

Keeps your rebuttal knowledge base current. It identifies opportunities that moved to Closed Won since the last run, gathers the associated call transcripts, splits them into objection-and-response chunks, generates embeddings, and stores everything in a Supabase vector table with deal metadata.

When to use it

Run this as the backbone for any objection-retrieval workflow. Set it nightly so every rebuttal search reflects the deals your team closed yesterday, not a stale snapshot.

How it works

  1. 1A nightly schedule triggers the run.
  2. 2Salesforce is queried for opportunities newly marked Closed Won, including stage, amount, competitor, and linked activity transcripts.
  3. 3A logic step filters out deals with no usable transcript text and de-dupes ones already ingested.
  4. 4Each transcript is chunked and sent to OpenAI for embeddings.
  5. 5Vectors plus deal metadata (industry, deal size, objection tags) are upserted into the Supabase pgvector table, ready for retrieval.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SupabaseTables, auth, storage, edge functions.
  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.