Contact data: your tools, ours, or both

Where the data can come from

Your keys are stored encrypted and used only on the server; nobody at Hallway sees them in the app. Lookups through your own accounts use your plan with that vendor and cost no Hallway credits.

Order and modes

In Settings → Contact data an admin picks one of three modes and the order of your own tools:

• My tools first, then Hallway data (default). Your tools are tried in your order; Hallway data is used only for people they did not find.
• Only my own tools. Never spends credits on contact data.
• Only Hallway data. Your keys stay connected but are not used for lookups.

A phone lookup skips tools that cannot return phones (Apollo, Hunter). Clay and webhooks answer a few minutes later, so they always run after the tools that answer at once; if they come back empty and your mode allows it, the person goes on to Hallway data automatically. A lookup that has not been answered within 24 hours counts as not found.

People at a company, by job title

When a show's shortlist has companies rated P1 or P2 but nobody from them, the Shortlist tab offers to look for people by job title through your own Apollo account. The search is free in Apollo and shows the first name, a hint of the last name and the title for up to 3 people at each of up to 20 companies. Nothing is saved at this point. Adding the people you pick reveals their full name, LinkedIn and work email; Apollo charges your account about 1 credit for each person it finds. Hallway charges nothing. These people work at a company on the show; Hallway does not claim that they attend.

Plug in any tool with a webhook

Use this for an enrichment provider we do not list, your own database, or a Make, Zapier or n8n scenario. Paste the endpoint in Settings → Connectors → Any other tool (webhook). It has to be a public https:// address.

1. Hallway sends one request per person

POST https://your-endpoint.example.com/enrich
content-type: application/json

{
  "hallway_request_id": "5b0c…-…",          // echo it back
  "hallway_token": "9f2e…",                  // echo it back (proves the answer is for this lookup)
  "callback_url": "https://…/functions/v1/enrich?clay_callback=1",
  "grade": "email",                          // "email" or "phone"
  "first_name": "Ana", "last_name": "Lee", "full_name": "Ana Lee",
  "company": "Example Retail", "domain": "example-retail.com",
  "linkedin_url": "https://www.linkedin.com/in/…"   // or null
}

Answer the request itself with any 2xx status as soon as you have accepted it; do the lookup afterwards. A non-2xx answer counts as a failed lookup.

2. You post the result to callback_url

POST {callback_url}
content-type: application/json

{
  "hallway_request_id": "5b0c…-…",
  "hallway_token": "9f2e…",
  "email": "ana.lee@example-retail.com",     // or "phone": "+44 20 …" for a phone lookup
}

// Nothing found: send the same two ids without email or phone.

Hallway looks for the first field whose name contains email (or phone) anywhere in the JSON, so nested results from a provider can be passed through as they are. The token can also go in an x-hallway-token header.

In Make, Zapier or n8n

1. Start the scenario with a Custom webhook (Make), Catch Hook (Zapier) or Webhook node (n8n), and paste its URL into Hallway.
2. Add the lookup step of the provider you use, mapping first_name, last_name, domain or company, and linkedin_url.
3. Finish with an HTTP request: method POST, URL = callback_url from step 1, JSON body with hallway_request_id, hallway_token and email (or phone).

What is sent and what is kept

Only what a lookup needs leaves Hallway: name, company, company domain and a public profile link. The result is saved on the person in your workspace with its source, and the raw answer is kept with it so you can see where a contact came from. Contact data found for one workspace is never shared with another.

Using your own data provider is under your agreement with them. Questions: hello@hallwaygtm.com