Gate paid ad creative with Spendict before sending to ad platforms
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch
What it does
Quick Overview This workflow takes ad copy, sends it to Spendict’s assess endpoint to score and classify it, and then routes the result based on the returned launch recommendation so only ads that pass the gate proceed to your next step. How it works 1. Runs when you manually click “Test workflow”. 2. Defines the ad payload (headline, primary text, target platform, and product context) to be evaluated. 3. Sends the ad copy to Spendict’s /api/v1/assess endpoint to receive scores and a launchrecommendation verdict. 4. Branches based on the verdict, routing run to the “ship it” path and fixfirst to the “hold” path, with all other values sent to a fallback output. Setup 1. Create a Spendict account, generate an API key, and configure HTTP Header Auth with Authorization: Bearer <yourkey for the Spendict request. 2. Replace the sample ad fields (headline, primary text, platform, and product context) with your ad generator output, webhook input, or queue payload. 3. Connect your downstream actions to the run, fixfirst, and fallback outputs to decide how to ship, revise, or regenerate ads based on the verdict.