BlueSteps x Maxionlabs

Job feed: how it works and what happens next

Everything from the 26 Oct walkthrough in one place. The full Operating Manual is in the jobs@ Drive folder "BlueSteps Job Feed".

How it works

 SUNDAY
 Kadoa scrapes new jobs into the Google Sheet
        |
        v
 MONDAY 12am ET  (n8n, on your account)
 +--------------------------------------------------------------+
 |  1. Read the settings sheet                                  |
 |     prompts, title keywords, job cap, who gets the email     |
 |  2. Read the Kadoa sheet                                     |
 |  3. Keep good job titles, skip every link already sent       |
 |  4. More jobs than the cap?  --->  stop, email the fix       |
 |  5. Run your 6 prompts on each job  (your OpenAI key)        |
 |  6. Check every row against Kulsoom's validation guide       |
 +--------------------------------------------------------------+
        |                                   |
        v                                   v
   READY file                        NEEDS-REVIEW file
   upload as is                      first column says why
        |                                   |
        +--------->  email to jobs@  <------+
                         |
                         v
        7. Remember every link it sent, so it never sends it twice

 MONDAY MORNING  (Kulsoom, about 10 min)
 fix or delete review rows  ->  spot-check 5 rows  ->  upload to Magento

 ANY STEP FAILS  --->  "FAILED" email to jobs@ that starts with HOW TO FIX IT

Want to change a prompt, keyword, the cap or who gets the email? Change the cell in the settings sheet. The next run uses it, no code.

What's built

The weekly run above, on your n8n, your Google (jobs@) and your OpenAI key.
Kulsoom's guide enforced on every row: plain characters only, "Confidential" when there's no company, United States spelled one way, zips keep their leading zero, city holds a city only, no phones, emails or links in descriptions.
Safety rails: the job cap, the sent-links memory, and a failure email with the fix for every failure we know about.
Settings sheet, Operating Manual, and an AI change kit for Sid's team, so bigger changes don't need me.
Tested on 20 jobs you already published: 19 came out clean, the 20th was flagged for review for a real reason (no city).

What's left

Magento cross-check. Once Sergey's export arrives, the feed also skips anything already live on the site.
Test run. The files go to Kulsoom to spot-check.
Second run on Monday 2 Nov. Two good runs and it goes into production.
Handoff. Walkthrough video at the top of the manual, and the Drive folder plus the change guide shared with Sid.

Timeline

Mon 26 Oct	Sergey's export arrives. Magento cross-check goes in.
Tue 27 Oct	Test run on the latest Kadoa jobs. Both files emailed to Kulsoom to spot-check.
Mon 2 Nov	Second run, emailed to jobs@ and Kulsoom. Kulsoom checks it again.
After 2 good runs	Into production. It runs on its own every Monday from then on.

What I need from you

SidSergey's Magento export of the live job links, today.
KulsoomSpot-check the test files and tell me anything that looks off.
KulsoomThree quick calls: US jobs only? Is gpt-4.1 the right model? States in full (Texas) or short (TX)?
SidA look at the Kit folder and the change guide, so your team knows where everything is.

Next steps

Sid sends Sergey's export, I wire in the Magento check.
Tuesday test run, files emailed to Kulsoom.
Monday 2 Nov run, Kulsoom checks again.
Both good: it goes into production, I hand the guide and kit to Sid, and we close out.

Questions: reply on the email thread, or check Section 3 of the Operating Manual first.