Step 2: Connect the Data Source API

Configure the API request that triggers the competitor data scrape.

1. Open Fetch Rival Pages and set Method to POST.
2. Set URL to https://api.brightdata.com/datasets/v3/trigger.
3. Enable Send Body and Send Headers.
4. In Body Parameters, set dataset_id to gd_l7q7dkf244hwjntr0, url to ={{$json.competitorUrl}}, and format to json.
5. In Header Parameters, set Content-Type to application/json.
6. Set Authentication to genericCredentialType and Generic Auth Type to httpHeaderAuth.
7. Connect Fetch Rival Pages to Analyze Offer Signals.

Credential Required: Connect your httpHeaderAuth credentials in Fetch Rival Pages.

Step 3: Set Up Competitive Analysis Processing

This step calculates scores, insights, and threat levels from competitor data.

1. Open Analyze Offer Signals and confirm the JavaScript is set to compute competitiveScore, threatLevel, and recommendations.
2. Adjust your baseline values directly in the code if needed (e.g., const yourCommissionRate = 10; and const yourCookieDuration = 30;).
3. Ensure the output includes the comparison object and analyzedAt timestamp.
4. Connect Analyze Offer Signals to Branch by Risk Level.

⚠️ Common Pitfall: If competitorUrl is missing in input data, Fetch Rival Pages will fail. Confirm your trigger data includes it before testing.

Step 4: Configure Risk-Based Routing and Alerts

Route high-risk rivals to critical alerts and all rivals to logging/reporting in parallel.

1. Open Branch by Risk Level and verify the conditions check ={{ $json.threatLevel }} equals Critical or High.
2. Confirm parallel routing: Branch by Risk Level outputs to both Update Rival Dashboard and Archive Intelligence Log in parallel.
3. For the high-risk path, connect in parallel to Critical Threat Slack Alert and Build Strategy Report.
4. For the non-critical path, connect in parallel to Routine Status Slack Update and Build Strategy Report.
5. In Critical Threat Slack Alert, keep the message template intact so it renders insights with {{ $json.insights.join('\n') }} and recommendations with {{ $json.recommendations.join('\n') }}.
6. In Routine Status Slack Update, verify it uses the quick comparison template for low/medium threats.

Credential Required: Connect your Slack credentials in Critical Threat Slack Alert and Routine Status Slack Update.

Step 5: Configure Reporting, Logging, and Summary Outputs

Store data in Google Sheets, generate strategy emails, and calculate a market summary.

1. In Update Rival Dashboard, set Operation to appendOrUpdate, Document to [YOUR_ID], and Sheet to gid=0 (Competitor Analysis).
2. Map columns in Update Rival Dashboard, such as Date to ={{ $now.toFormat('yyyy-MM-dd') }} and Threat Level to ={{ $json.threatLevel }}.
3. In Archive Intelligence Log, set Operation to appendOrUpdate, Document to [YOUR_ID], and Sheet to gid=1 (Historical Log).
4. Ensure key columns in Archive Intelligence Log are mapped, such as Timestamp to ={{ $now.toISO() }} and Competitor to ={{ $json.competitorName }}.
5. In Build Strategy Report, confirm the code generates emailSubject and emailBody for downstream messaging.
6. Configure Send Affiliate Briefing with Subject set to ={{ $json.emailSubject }}, and set From Email and To Email to [YOUR_EMAIL].
7. In Compute Market Summary, keep the assignment expressions that compute totals, such as ={{ $input.all().length }} and ={{ $input.all().filter(item => item.json.threatLevel === 'Critical').length }}.
8. Verify the summary text in Compute Market Summary references its own output using {{ $('Compute Market Summary').item.json.totalCompetitors }}.

Credential Required: Connect your Google Sheets credentials in Update Rival Dashboard and Archive Intelligence Log.

Credential Required: Connect your Email credentials in Send Affiliate Briefing.

Step 6: Test and Activate Your Workflow

Run a full test to confirm alerts, sheets, and emails are generated correctly.

1. Click Execute Workflow and inspect the run from Scheduled Rival Scan through Compute Market Summary.
2. Confirm that Branch by Risk Level routes correctly: critical/high results trigger Critical Threat Slack Alert while others trigger Routine Status Slack Update.
3. Check that Google Sheets rows were appended in both Update Rival Dashboard and Archive Intelligence Log.
4. Verify you receive an email from Send Affiliate Briefing with a subject from ={{ $json.emailSubject }}.
5. Once results are correct, toggle the workflow to Active for production scheduling.