5-step workflowfull-text search search backend frontend database generated Data & database guided-flow App Builder

Add Persistent Full‑Text Search to Existing App

Integrate a real, searchable index into the current app with a backend API and UI component.

Run this as a guided flow on Flows — verify gates and recovery prompts included →

Flows@flows12d ago

0 runs0 forks0

Chain

Inputs

Step 1

flow-full-text-search-1-determine-searchable-entities-and-choose-engine-579600

Step 2

flow-full-text-search-2-create-migration-to-add-tsvector-columns-and-gin-4141a8

Step 3

flow-full-text-search-3-implement-backend-search-endpoint-4e0883

Step 4

flow-full-text-search-4-build-front-end-search-component-b394ab

Step 5

flow-full-text-search-5-verify-end-to-end-functionality-and-persistency-659c60

Final output

Workflow inputs

No inputs required — hit Run to stream each step in order.

Each step streams from its model and feeds the next. BYOK — you pay your provider directly. Add a key in Settings if a step needs one.

Step 1 · Identify which tables/fields need full‑text search and select a compatible indexing solution.

flow-full-text-search-1-determine-searchable-entities-and-choose-engine-579600

Claude Sonnet 4.6→ {{step_1}}

Awaiting upstream steps…

Step 2 · Persist searchable data in the database and keep it up‑to‑date.

flow-full-text-search-2-create-migration-to-add-tsvector-columns-and-gin-4141a8

Claude Sonnet 4.6→ {{step_2}}

Awaiting upstream steps…

Step 3 · Expose a HTTP API that queries the full‑text index and returns matching records.

flow-full-text-search-3-implement-backend-search-endpoint-4e0883

Claude Sonnet 4.6→ {{step_3}}

Awaiting upstream steps…

Step 4 · Give users a live search box that calls the new API and displays results.

flow-full-text-search-4-build-front-end-search-component-b394ab

Claude Sonnet 4.6→ {{step_4}}

Awaiting upstream steps…

Step 5 · Confirm that new records are searchable and that the index updates automatically.

flow-full-text-search-5-verify-end-to-end-functionality-and-persistency-659c60

Claude Sonnet 4.6→ {{step_5}}

Awaiting upstream steps…

About this workflow

Integrate a real, searchable index into the current app with a backend API and UI component.

What happens when you run it

1
Identify which tables/fields need full‑text search and select a compatible indexing solution.
Runs flow-full-text-search-1-determine-searchable-entities-and-choose-engine-579600 on Claude Sonnet 4.6
2
Persist searchable data in the database and keep it up‑to‑date.
Runs flow-full-text-search-2-create-migration-to-add-tsvector-columns-and-gin-4141a8 on Claude Sonnet 4.6
3
Expose a HTTP API that queries the full‑text index and returns matching records.
Runs flow-full-text-search-3-implement-backend-search-endpoint-4e0883 on Claude Sonnet 4.6
4
Give users a live search box that calls the new API and displays results.
Runs flow-full-text-search-4-build-front-end-search-component-b394ab on Claude Sonnet 4.6
5
Confirm that new records are searchable and that the index updates automatically.
Runs flow-full-text-search-5-verify-end-to-end-functionality-and-persistency-659c60 on Claude Sonnet 4.6

Best for

•Recurring tasks you currently copy-paste between tools.
•When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
•Fork and adapt if your inputs differ materially from the author's use case.

Models used

Claude Sonnet 4.6