Filter leads by mail provider, and name the columns you import

Importing a CSV now lists the columns that become custom fields under Other columns. Rename one (save z123 as p234), add it to a custom field you already have, or choose Don’t import. A column whose header matches one of your fields apart from capitals and spaces starts on that field, so repeat imports fill the same {{variable}}.

Each column shows its first value from the file and the {{variable}} it gives you, and the import tells you before it starts if a name would not work, such as one taken by FoxReach’s own variables like first_name.

New custom fields added on a lead’s page follow the same naming rules, and a value without a name is no longer dropped without a word.

Exporting leads to CSV now includes every custom field. Fields that the most recently added lead did not have were left out of the file.

Fenn and the MCP server can set and change custom fields on a lead, and rename or skip columns when importing a CSV.

A Mail provider filter on the Leads page: pick Google, Microsoft, Zoho, Yahoo / AOL, GoDaddy or Other to see only the leads whose email is hosted there. Each option shows how many of your leads it holds.

Behind a security filter shows the leads whose mail passes through a filter such as Proofpoint, Mimecast or Barracuda before it reaches their inbox. Not checked yet shows the leads FoxReach has not looked up.

The first time you use the filter, FoxReach checks your leads in the background. On a large list this takes a few minutes; a note above the table says how many are left and the list updates by itself.

The public API can filter leads by provider too, and count them by provider.

Leads on Microsoft 365 for US government are now recognised as Microsoft for provider matching.

API: read, update and delete a single inbox thread, list a campaign's leads and its sending accounts, and see how a campaign's mailboxes and leads split across mail providers.

The MCP server for AI assistants now covers the whole public API: 89 tools, up from 64, including inbox threads, webhooks, email verification, warmup details and mailbox orders.

A webhook event for leads added to a campaign, so automations can react when a list lands in a campaign.

Fenn can open and update individual inbox threads, show a campaign's provider mix and filter leads by mail provider. It no longer creates webhooks in chat, so a webhook's signing secret never appears in a conversation.

Looking up a lead by email through the API now matches that exact address. Before, a % or _ in the address could match other leads.

The developer docs have a reference page for every public API endpoint, with its parameters, errors and example requests, including email accounts, Lead Finder, managed mailboxes, tracking domains, verification and warmup.

Docs pages, parameters and code samples for things that are not available to everyone yet are marked Beta.

The docs use the new FoxReach orange.

The docs have a new home on foxreach.io: faster pages, a search box that finds any section (Ctrl K), and a Try it window on every API page that sends a real request with your API key and shows the response.

Click any screenshot in the docs to see it full screen.

Every docs page has Copy page, which copies it as plain text, and an Open menu to read it as Markdown, open it in your AI assistant with the page already loaded, or copy the docs server address for your code editor.

Filtering leads by tag in the public API with more than 50 tags, or a tag longer than 100 characters, now returns a clear error instead of a server error.

The webhook examples in the Python and TypeScript SDK docs use the method names the SDKs actually have.