Search context for the n8n review workflow.
Make quality review easier to act on.
Where this work fits
Once AI features were in use, a disappointing result could come from several places. A model call, a search result, and a dashboard count each needed different evidence before the team could decide what to fix.
I built the application-side integration that supplied the review team’s n8n workflow with search context and the candidates actually displayed. I worked on correlating that information and handling delivery failures without interrupting search. The review team maintained the receiving workflow.
Turn an observation into a useful review
#1042- Receive resultWebhook
- Keep the contextFormat review
- Create reviewReview queue
Review Alex Morgan.
#1042 Original search attached
Ready to investigate. Nothing to reconstruct.
Capture the right context without blocking the user.
The review team needed the result the user actually saw. I worked on carrying that context into the review handoff while keeping a delivery failure from interrupting search. For metrics, I checked what each count represented and kept incomplete periods from distorting comparisons.
The skills behind the work
- TypeScript
- Make data shapes and code boundaries explicit while building product behavior.
- Workflow integration
- Carry useful context from a product event into the next person’s review or task.
- Event design
- Represent an action accurately so another part of the product can respond or measure it.
Engineers could inspect model failures and timing. Reviewers received search context to investigate, and product reporting used clearer definitions for the activity being measured.