n8n Workflow: Validate US Property Request via HTTP

Validate a US Property Request Before Any Separate Evidence Purchase (HTTP Check)

This n8n workflow validates a US property request by calling the CivicDataForge free quote API over HTTP—confirming the quote is valid, uncharged, and correctly scoped—then returns a typed “scope ready” result. It retrieves no permit evidence and makes no purchase.

What this workflow does

• Manual trigger: Runs when you start it manually in n8n.
• Builds a JSON payload: Creates a request containing the task, the public property address (address, city, state), a purpose field, and retention settings.
• Calls CivicDataForge free quote API: Sends the payload to the endpoint at https://civicdataforge.pages.dev via the HTTP Request node and captures the full response.
• Validates the response: Checks HTTP status, JSON contract, charged=false, quote ID format, issue/expiry times, and the expected purchase URL/destination. If anything is invalid, it produces no purchase handoff.
• Outputs a typed result: Returns a result indicating whether the scope is ready for a separately authorized evidence purchase handoff, or a rejected state if the response is failed/invalid/expired.

Use cases

• Confirm a property request is still within its quote expiry before starting a separate evidence purchase workflow.
• Gate downstream steps so only requests with charged=false and correct destination URLs progress.
• Quality-check input changes (address/city/state) to avoid invalid or expired scopes.

Technical details

• Category: n8n automation workflow
• Nodes used: Manual Trigger, Set, Code, Sticky Note, HTTP Request
• External integration: CivicDataForge free quote API over HTTPS at https://civicdataforge.pages.dev
• Important: Use only public property inputs; this workflow does not retrieve permit evidence and does not perform any purchase.