Subdomain Finder API + Intercom

Send the response straight into Intercom — connected through Zapier, Make, or n8n, no code required.

WhenIntercomNew conversation
trigger
RunSubdomain Finder APIReturns the response
action
ThenIntercomCreate user

The Subdomain Finder API in Intercom.

Intercom connects businesses with customers through messaging. Integrating APIs with Intercom enables intelligent lead qualification, automated data enrichment, and context-aware conversations. Give your team the data they need instantly.

Workflows worth wiring.

Validate visitor email addresses before starting conversations
Enrich lead profiles with company data from business APIs
Score conversations based on external data signals
Automatically tag users based on their domain or company type

Ready-made ideas.

New conversation started in Intercom Fetch subdomains for customer domain → add count and key hosts as conversation note

Customer Domain Intelligence in Intercom

Give support agents domain context by showing subdomain count and key hosts in Intercom chats.

New user identified in Intercom Fetch subdomains for user domain → tag user based on count threshold for segmentation

Domain Complexity Tag in Intercom

Segment Intercom users by domain complexity using their subdomain count for targeted messaging.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Intercom as the trigger app and "New conversation" as the event. Connect your account.
  2. 2
    Add the API action. Add APIVerve as the action, select the Subdomain Finder API, and map your trigger data to the request.
  3. 3
    Send it back. Add a second Intercom action for "Create user" and map the returned fields (like rootDomain) into it.
  4. 4
    Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
  1. 1
    Add the trigger. Create a scenario and add a Intercom module set to "New conversation". Authenticate your account.
  2. 2
    Call the API. Add an HTTP module pointing at api.apiverve.com/v1/subdomainfinder with your x-api-key header. Pass the trigger's data as the input.
  3. 3
    Parse & map. Add a JSON module to read the response, then a Intercom module for "Create user". Map fields like data.rootDomain into place.
  4. 4
    Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
  1. 1
    Add the trigger node. Start a workflow with a Intercom trigger node for "New conversation" and connect your credentials.
  2. 2
    Add an HTTP Request node. Point it at api.apiverve.com/v1/subdomainfinder using Header Auth (x-api-key). Feed in the trigger data.
  3. 3
    Map with expressions. Add a Intercom node for "Create user" and reference the response with expressions such as {{ $json.data.rootDomain }}.
  4. 4
    Execute & activate. Execute manually to verify, then activate the workflow for production.

What Intercom receives.

rootDomaindomain, records
subDomainsarray of 47
count47
totalFound47

Intercom + Subdomain Finder API FAQ

How do I enrich Intercom users with external data?
Trigger on new users or conversations, extract identifiers like email or company domain, call enrichment APIs, and update Intercom user attributes.
Can I validate emails in Intercom before agents respond?
Yes. Set up automations that validate new user emails and add tags or notes indicating validity. Agents can see this information before engaging.
How do I prioritize Intercom conversations with API data?
Enrich users with external data (company size, plan value, etc.) and use Intercom's rules to prioritize based on these custom attributes.

Connect the Subdomain Finder API to Intercom. One key, no code, live in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales