Plug into Clay / n8n / Zapier

HTTP-request node configuration for the three most common no-code pipelines: auth header, URL templates, and output mapping.

Markdown mirror: /docs/guides/clay-n8n-zapier.md

There's no SDK to install — VendorStacks is plain JSON over HTTPS with one header, which is exactly what no-code HTTP nodes want. The three configs below all do the same thing: enrich a row that has a domain column.

Clay — HTTP API enrichment column

Field	Value
Method	`GET`
Endpoint	`https://vendorradar-production.up.railway.app /v1/check?url={{domain}}`
Headers	`Authorization`: `Bearer vr_live_…` (store the key as a Clay secret)
Output columns	`found` · `vendor_stack.sms_messaging[0].vendor` · `vendor_stack.payments[0].vendor` · `credit_balance`

Clay retries non-2xx responses automatically; that's safe here because failed calls are never charged. Add a formula column on vendor_stack to compute your fit tier in-table.

n8n — HTTP Request node

Node settings

Method:            GET
URL:               https://vendorradar-production.up.railway.app
/v1/check
Query parameters:  url = {{ $json.domain }}
Header parameters: Authorization = Bearer {{ $credentials.vendorStacksKey }}
Options → Timeout: 120000   # only matters if you add fresh=true
On error:          Continue (error output) — route 402 to a Slack alert

Put the key in an n8n credential (Header Auth type), not inline in the node. For batch runs, add a Wait node of 1s between iterations to stay under 60 rpm without tripping 429 handling.

Zapier — Webhooks by Zapier (Custom Request)

Zap step

Action:  GET
URL:     https://vendorradar-production.up.railway.app
/v1/check?url={{domain}}
Headers: Authorization | Bearer vr_live_…

Zapier flattens the JSON response into fields you can map into your CRM step — vendor_stack sms_messaging 1 vendor becomes a pickable field. Reverse-lookup segments work the same way against /v1/prospect; loop pages with the built-in Looping app, 1 credit per page of 10.