Pre-publish YouTube QA from your Airtable calendar

Build me a pre-publish QA agent for my YouTube content calendar. It should watch my Airtable base and fire whenever a video draft is ready for human review, then run the draft through vidIQ before I post it.

Trigger: poll Airtable with the New or Updated Record event on my Videos base / Videos table. The agent should only act when the row's Status field flips to "Ready for review" (make the exact status value configurable). Ignore other status changes.

Once a matching row fires, use Airtable's Get Record to read the full row. The fields it needs are: working title, planned thumbnail URL (or attachment URL), target topic / keyword, channel name, and the row id. Carry the row id through so we can write back at the end.

Then call vidIQ through its MCP server to score the draft. Three calls:

• vidiq_score_title on the working title.

• vidiq_score_thumbnail on the planned thumbnail URL.

• vidiq_keyword_research on the target topic to pull search volume, competition, and related keywords.

With those results, reason about the weak spots. Identify the highest-opportunity keyword (good volume, lower competition) from the keyword research output. Draft two or three sharper alternate titles tuned to that keyword. Flag any thumbnail issues the score surfaces (low contrast, small face, no focal point, text too small, etc.) in plain language.

Then post a single Slack message via Send a Message to my content channel (let me set the channel id at setup). The message should include:

• Video name and channel.

• Title score and thumbnail score from vidIQ.

• Target keyword with its volume and competition, plus the higher-opportunity keyword if it found one.

• The recommended title (the strongest of the alternates) and the runner-up options below it.

• Any thumbnail issues to fix.

• A clear verdict at the bottom: GO if both scores clear the bar, REWORK if either is weak (let me tune the thresholds).

Optional but on by default: write the scores and the recommended title back to the same Airtable row using Update Record, so the calendar carries the review history. Use fields like Title Score, Thumbnail Score, Recommended Title, and QA Verdict (create them if they do not exist and let me map the field names at setup). If write-back is turned off, skip this step.

Keep it to one workflow, one Slack message per fire, and do not re-process a row unless the status flips back into Ready for review again.