IMPLEMENTATION GUIDE
Keep enrichment outside the signup request
Accept the signup first, then enqueue enrichment from your backend. Extract the company domain from the work email, normalize it, and filter personal email providers before requesting company data. Keep your API key on the server. A signup should still succeed when an enrichment request fails; treat enrichment as a follow-up job rather than a prerequisite for opening the account.
Create a Loop in the EnrichLoops dashboard with your HTTPS webhook destination. Send the domain to that Loop, or use the company enrichment endpoint and poll the task. The initial response contains a queued task, not a completed company profile. Store its task ID alongside your account ID so your worker can apply the result to the right signup.
Turn company fields into explicit qualification rules
Use primary industry, employee count or range, and headquarters to evaluate account fit. For example, a team selling to software companies with 50–200 employees could flag signups that meet those criteria for sales assistance. This is an illustrative rule, not a built-in EnrichLoops score. Your app decides which attributes matter and which action follows.
Keep missing data separate from a poor fit. If headcount is unavailable, let the account continue through your normal onboarding and mark its qualification as incomplete. Avoid treating an absent field as zero employees. Keep the source fields with the score so your team can see why an account was routed.
Process results safely and control repeat lookups
For webhook delivery, verify the signature using your Loop signing secret before updating a record. Match the completed task to the account you stored, and track the delivery ID so a repeated webhook does not trigger duplicate assignments or messages. If you choose polling, check the task status before reading the company data.
A successful company lookup costs one credit. Repeat lookups within the 14-day company freshness window cost zero credits, and failed lookups are not charged. Group signups from the same domain around one company record and inspect the returned freshness timestamps before making time-sensitive decisions. Company enrichment adds business context; people enrichment is a separate lookup when you also need professional details about the contact.
Validate the flow before routing real accounts
Test a company domain, a personal email address, two signups from the same company, and a record with incomplete data. Confirm that signup stays fast, webhook retries do not repeat actions, and accounts without a match can still use the product. Start with the monthly free credits, review the results on your own signup sample, and then enable the routing rules you have validated.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentThe data product this flow uses.LoopsWebhook delivery so the form never waits on a lookup.Common questions
Does enrichment slow down signup?
Accept the signup first and enqueue enrichment afterward. EnrichLoops returns a queued task; your backend receives the completed profile by polling or a Loop webhook, then applies your rules.
Can I qualify a signup from a personal email?
A personal email domain does not identify the signup’s company. Ask for a company website when appropriate, or leave the account unqualified until you have a business identifier.