BlueSteps × Maxionlabs

Job-Feed Automation, Working Session

Everything we tick off today lets the build start immediately. Green across the board = the two-week clock starts now.

📅 Fri, Aug 28 👥 Kulsoom · Sid · Max 🎯 Goal: all inputs locked, build starts

0 of 0 locked0%

Set up live on this call

Both take a few minutes with a screen share and remove the two biggest blockers.

Create the n8n account KulsoomYour email, your billing (~$26/mo, the only running cost of the automation). Then invite maksym@maxionlabs.com as admin. Ownership stays with BlueSteps. Hand over the OpenAI key KulsoomScreen share or paste into n8n directly, never email. Also confirm: which model exactly, and the account's rate-limit tier. A low tier means the Monday run takes hours; upgraded, it finishes in under one. Authorize Google Sheets access for the workflow Kulsoomn8n needs its own credential to read the source sheet and write the output. One OAuth approval from an account that can see the sheet.

Sid's two items

The dedupe step cannot exist without these. They are the last inputs missing.

Magento apply-URL list for dedupe SidEither Magento API access, or the weekly URL sheet saved to one fixed location the workflow can read. The current weekly email version cannot be read by an automation. Where the finished CSV lands Sid + KulsoomRecommendation: a Drive folder plus an email notification each Monday. Decide the folder and who gets the email.

Lock in writing

Sign the SOW with acceptance defined BothInstance 1 produces a clean Monday CSV, Kulsoom spot-checks and uploads it without issues. That is the build delivered. Already agreed by email; the SOW should say the same thing and be signed. State the delivery date MaxAbout two weeks from the day the last input above lands. Named out loud on this call so everyone has the same date. Monday run time + failure alert Kulsoom12 AM in which timezone, and who gets notified if a run fails. A silent failure is the one thing this build is not allowed to do.

Confirm the details

Cheap to answer on a call, expensive to guess in a build.

Walk through David's existing macros Kulsoom / DavidTen minutes of screen share, or a scheduled follow-up. Seeing what runs today beats rebuilding it from a description. Good/bad filter: is the title formula the whole rule? KulsoomThe formula received checks job titles only. Confirm no second sheet, manual pass, or extra rule sits behind it. Prompt set: columns J to AL is complete and current KulsoomWalk one real job through the prompts live so the build replicates exactly what works today. Magento allowed categories + tags, the explicit list KulsoomThe sample CSV shows examples; the validation layer needs the full allowed list to check rows against. A handful of past bad rows + one finished week KulsoomExamples of rows you caught by hand, plus one week's raw input next to its final approved CSV. That becomes the test set the build must pass before you ever see it. When does Kadoa finish writing on Sunday? KulsoomThe Monday run must start after the scrape completes, so the two never race each other.

One design note: the output check is deterministic code (required fields, city/state/zip consistency, valid tags), not a second AI pass. Rules cannot hallucinate; that is the point of the layer.

Parked, on purpose

Instance 2 (Sid's project)Starts after instance 1 is accepted, as agreed: a copy of something already working. Needs the NDA and the second Kadoa account first. If its source or output differs from instance 1, we scope that separately.