Step 2: Connect NocoDB and Slack for Status Updates

Update row status in NocoDB and post alerts to Slack when the workflow starts and finishes.

1. In Mark Status Started, set Operation to update, and confirm Project ID and Table are set to your NocoDB IDs.
2. Credential Required: Connect your nocoDbApiToken credentials in Mark Status Started.
3. In Post Start Alert, set Channel to your Slack channel and keep the message template with expressions like {{ $json.primary_topic }}.
4. Credential Required: Connect your slackApi credentials in Post Start Alert.
5. In Store Content Brief and Mark Status Complete, replace Project ID and Table values from [YOUR_ID] with real IDs.
6. Credential Required: Connect your nocoDbApiToken credentials in both Store Content Brief and Mark Status Complete.
7. In Post Completion Alert, set the Slack channel and keep the message template using {{ $('Consolidate All Data').item.json.primary_topic }} and related expressions.
8. Credential Required: Connect your slackApi credentials in Post Completion Alert.

Step 3: Map Incoming Fields and Start Parallel Processing

Normalize incoming data from the webhook and fan out into the AI, competitor, status, and alert branches.

1. In Assign Key Fields, confirm each assignment uses the expressions like {{ $json.body.data.rows[0]['Primary Topic'] }}, {{ $json.body.data.rows[0]['Competitor URLs'] }}, and {{ $json.body.data.rows[0].Language }}.
2. Verify that Assign Key Fields outputs to Topic Broadening Agent, Format JSON + Add URLs, Consolidate All Data, Mark Status Started, and Post Start Alert in parallel.
3. In Format JSON + Add URLs, keep the JavaScript that splits and cleans competitor_urls into competitorUrls.

Step 4: Set Up AI Keyword Expansion and Metrics Enrichment

Generate keyword ideas with AI, then enrich them with volume, CPC, and difficulty metrics.

1. In Topic Broadening Agent, keep the prompt text and confirm Has Output Parser is enabled.
2. Attach Structured JSON Parser as the output parser to enforce the JSON schema shown in its JSON Schema Example. This is a sub-node, so add credentials on the parent model node instead.
3. Credential Required: Connect your openAiApi credentials in ChatGPT Core Model (this is the language model powering Topic Broadening Agent).
4. Ensure Topic Broadening Agent outputs to both Separate Primary Keywords and Merge Topic and Metrics in parallel.
5. In Separate Primary Keywords, set Field to Split Out to output.primary_keywords.
6. Separate Primary Keywords outputs to both Volume and CPC Lookup and Keyword Difficulty Check in parallel.
7. Credential Required: Connect your dataForSeoApi credentials in Volume and CPC Lookup and Keyword Difficulty Check.
8. In Volume and CPC Lookup, set Language Name to {{ $('Assign Key Fields').item.json.language }} and Location Name to {{ $('Assign Key Fields').item.json.location }}.
9. In Keyword Difficulty Check, set Language Name Required to {{ $('Assign Key Fields').item.json.language }} and Location Name Required to {{ $('Assign Key Fields').item.json.location }}.
10. Aggregate metrics using Aggregate Volume CPC and Aggregate Difficulty, then combine with Combine SV CPC KWD using Mode combine and Combine By combineByPosition.
11. Merge topic data with metrics using Merge Topic and Metrics set to Mode combine and Combine By combineByPosition.

Step 5: Run Competitor Analysis and Consolidate Data

Analyze competitor URLs and combine insights with keyword data before drafting the final strategy.

1. In Split Rival Links, set Field to Split Out to competitorUrls.
2. In URL Ranking Retrieval, set Target to {{ $json.competitorUrls }}, Limit to 10, and map Language Name Required and Location Name Required using {{ $('Format JSON + Add URLs').item.json.language }} and {{ $('Format JSON + Add URLs').item.json.location }}.
3. Credential Required: Connect your dataForSeoApi credentials in URL Ranking Retrieval.
4. Attach ChatGPT Analysis Model as the language model for Rival Content Review and keep the prompt template that uses {{ $('Format JSON + Add URLs').item.json.primary_topic }} and {{ $('Split Rival Links').item.json.competitorUrls }}.
5. Credential Required: Connect your openAiApi credentials in ChatGPT Analysis Model (this powers Rival Content Review).
6. Aggregate competitor insights using Aggregate Rival Insights.
7. Combine all streams in Consolidate All Data with Mode combine, Combine By combineByPosition, and Number Inputs 3.

Step 6: Draft the SEO Strategy and Send Outputs

Generate the final strategy brief and write the results back to NocoDB while notifying Slack.

1. In Final SEO Strategy Draft, keep the full prompt and ensure it reads from {{ $json.data.toJsonString() }} and {{ $json.output.toJsonString() }}.
2. Attach ChatGPT Strategy Model as the language model for Final SEO Strategy Draft.
3. Credential Required: Connect your openAiApi credentials in ChatGPT Strategy Model (this powers Final SEO Strategy Draft).
4. Confirm Final SEO Strategy Draft outputs to Store Content Brief, Mark Status Complete, and Post Completion Alert in parallel.
5. In Store Content Brief, map primary_topic_used to {{ $('Consolidate All Data').item.json.primary_topic }} and report_content to {{ $json.output }}.
6. In Mark Status Complete, set Id to {{ $('Consolidate All Data').item.json.id }} and Status to Done.

Step 7: Test and Activate Your Workflow

Validate the workflow end-to-end and then enable it for production use.

1. Click Execute Workflow and send a sample POST payload to Inbound NocoDB Webhook with fields like Primary Topic, Competitor URLs, Target Audience, Content Type, Location, and Language.
2. Confirm Post Start Alert fires in Slack and Mark Status Started updates the NocoDB row.
3. Verify metrics are combined through Aggregate Volume CPC, Aggregate Difficulty, and Combine SV CPC KWD, and competitor insights are aggregated via Aggregate Rival Insights.
4. Check that Final SEO Strategy Draft outputs the content brief, and Store Content Brief creates a record in NocoDB.
5. Ensure Mark Status Complete updates the row to Done and Post Completion Alert posts the finished notification.
6. When everything looks correct, toggle the workflow to Active to run automatically for new webhook events.