n8n

Call Treffer from any workflow with n8n's HTTP Request node.

This page covers the values you need for Treffer. For the node itself, follow n8n's HTTP Request docs.

Fastest setup

Copy the cURL example of the endpoint you want into the node's cURL import. It fills in URL, method, headers and body in one go.

Email finder

curl -X POST 'https://api.treffer.io/v1/email/finder' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "first_name": "Christian",
    "last_name": "Hecker",
    "domain": "traderepublic.com"
  }'

import requests

response = requests.post(
    "https://api.treffer.io/v1/email/finder",
    headers={"X-API-Key": "YOUR_API_KEY"},
    json={
        "first_name": "Christian",
        "last_name": "Hecker",
        "domain": "traderepublic.com",
    },
    timeout=120,
)
print(response.json())

Inputs: full_name, or first_name and last_name. Plus domain or company_name; the domain gives the more reliable match.

Company profile

curl -X POST 'https://api.treffer.io/v1/companies/profile' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "domain": "traderepublic.com"
  }'

import requests

response = requests.post(
    "https://api.treffer.io/v1/companies/profile",
    headers={"X-API-Key": "YOUR_API_KEY"},
    json={
        "domain": "traderepublic.com",
    },
    timeout=120,
)
print(response.json())

Inputs: domain or name, or both; the domain gives the more reliable match.

All request and response fields: email finder, company profile.

Keep the key in a credential

Store the API key as a Header Auth credential instead of a literal header: name X-API-Key, value your key. The key stays out of the workflow and out of workflow exports.

Configuration

• • Method POST, URL exactly as documented, no trailing slash.
• • Send the inputs as a JSON body. Map incoming fields with expressions.
• • Set the node timeout to at least 120000 ms. Lookups run against live sources and can take up to 90 seconds.

Waterfalls and errors

A miss is not an error: HTTP 200, found false, 0 credits. Branch with an IF node on found and send misses to your fallback provider. No error handling needed for a miss.

For real errors, enable the node's retry on fail. A 429 tells you how long to wait in its Retry-After header, see rate limits and errors.

Privacy Policy Terms of Service Imprint