Subdomain Finder API + Typeform

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

WhenTypeformNew response
trigger
RunSubdomain Finder APIReturns the response
action
ThenTypeformCreate form

The Subdomain Finder API in Typeform.

Typeform creates beautiful, conversational forms that people love to fill out. Connecting APIs to Typeform enables real-time response validation, automated follow-ups, and intelligent data routing. Process form submissions instantly with enriched context.

Workflows worth wiring.

Validate email addresses from form submissions before adding to your CRM
Enrich lead capture forms with company data based on email domains
Route form responses to different workflows based on API validation results
Score leads automatically using external data APIs

Ready-made ideas.

New Typeform response submitted Fetch subdomains for domain in response → store count and totalFound alongside form data

Domain Analysis on Form Submission

Enrich Typeform submissions with subdomain count data when respondents provide a domain.

New Typeform response submitted Fetch subdomains for submitted domain → store host list and count for assessment scoping

Security Assessment Intake via Typeform

Automatically scope security assessments by discovering subdomains from Typeform intake forms.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Typeform as the trigger app and "New response" 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 Typeform action for "Create form" 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 Typeform module set to "New response". 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 Typeform module for "Create form". 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 Typeform trigger node for "New response" 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 Typeform node for "Create form" 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 Typeform receives.

rootDomaindomain, records
subDomainsarray of 47
count47
totalFound47

Typeform + Subdomain Finder API FAQ

How do I validate Typeform responses with external APIs?
Trigger automations on new Typeform responses. Call validation APIs with submitted data, then route to different workflows based on validation results.
Can I enrich Typeform submissions before sending to my CRM?
Yes. Intercept submissions in your automation, call enrichment APIs to gather additional data, then send the combined information to your CRM.
How do I handle invalid form submissions?
Set up conditional paths in your automation. Valid submissions proceed to your main workflow, while invalid ones can trigger follow-up emails or be logged for review.

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

Scaling up?

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

Contact sales