Using FieldSwap with Make.com

A scenario that takes an identity value from an earlier module — say the email address on a new CRM lead — sends it to FieldSwap, and gets a resolved field back (a phone number, an employer, a deliverability score, …) to use in later modules such as updating the record or routing the lead.

FieldSwap is the action in the middle of your scenario. The trigger ("watch HubSpot contacts", "watch Google Sheets rows", …) and the final write-back module are whatever apps you already use.

You need two things:

• A FieldSwap workspace with available credits.
• An API key. Create one in the API keys tab — it looks like fs_live_… and is shown only once, so paste it somewhere safe before leaving the page.

Add a module and pick HTTP → Make a request. Configure it like this:

In Request content, paste the JSON below, then map the field from your trigger module in place of the email value (shown here as {{lead_email}}):

{
  "input":  { "type": "email", "value": "{{lead_email}}" },
  "output": "phone"
}

Set input.type to whatever you're sending (email, phone, linkedin, full_name, ip) and output to the field you want back. The full list is in the Field types reference.

Run the scenario once. With Parse response on, FieldSwap's reply becomes mappable fields:

{
  "request_id": "8f1d2c20-…",
  "person_id":  "0a4e5b66-…",
  "output": {
    "type": "phone",
    "value": { "phone_e164": "+14155551234" },
    "fresh": true
  },
  "hit_source": "vendor",
  "credits_remaining": 9847,
  "status": "ok"
}

The resolved value lives under output → value. Map output: value: phone_e164 into your write-back module. Each output type has its own shape — see Field types.

FieldSwap returns 200 OK even when it has no data, so always check the status field rather than relying on the HTTP status. Add a Filter on the link leaving the HTTP module that only continues when:

status   (Text operator: Equal to)   ok

A status of not_found means we identified the person but no vendor had the requested field; opt_out means the person opted out of enrichment. In both cases output is empty and there's nothing to write back.

Every lookup costs 1 credit, whether or not a value comes back — you pay per query, not per match. To avoid burning credits on rows that can't be enriched, put a Filter before the HTTP module (e.g. only run when the email field isn't empty).

Requests are rate-limited to 60 per minute per workspace, shared across all your API keys. For large batches, lower the scenario's number of consecutive cycles or add a Sleep module; on a 429 Make's built-in error handling can retry. For sustained higher volume, contact us to raise the limit.

Every response carries an x-request-id header — quote it when you email support@fieldswap.io.