DocuQuery 1: ingestion
Drive folder in, Pinecone index out: extract text, chunk, embed, and keep the index in sync as files are added, changed or removed.
Real workflows lifted from the projects in the work index, with credentials stripped and identifiers blanked. Download the JSON, import it into your own n8n, connect your credentials, and you have the working shape of the system rather than a screenshot of one.
Drive folder in, Pinecone index out: extract text, chunk, embed, and keep the index in sync as files are added, changed or removed.
Slack /ask in, a cited answer out, with a Sources list naming document, page and department. Says when the documents don't cover it.
The shared error workflow the other two route into, so a failure anywhere surfaces in one place instead of dying quietly.
The DM side of the appointment setter: greet, qualify, then book, with each step as its own node on the canvas.
From An appointment setter that books inside the Instagram DM
The intake webhook that receives call, email and note events and hands them to the service that decides what they mean.
The webhook-driven workflow that sends candidate follow-ups once screening has decided who gets them.
Qualified leads get enriched, written to Airtable and announced in Slack. The last hop of a three-workflow chain.
From Distressed-property leads that qualify before they cost money
A new ledger file landing in a folder kicks off the audit and a Slack alert when it finds something.
In n8n, open Workflows, choose Import from File, and pick the JSON. Nodes that need credentials show a warning until you connect your own. Anything reading "set this in n8n after import" is a value I blanked on purpose.
Credential references, workflow ids, pinned test data, and any Airtable, Slack or similar identifiers. The logic, the expressions and the JavaScript inside Code nodes are untouched.
The whole system. Most of these call a service that does the deciding; the workflow is the plumbing around it. The write-up for each project says which is which.
These are the n8n halves. The services they call, the evals and the decisions are in the work index. Bring me the problem and I'll say which half you actually need.