Check identity fields
Confirm that the name and contact channel refer to the intended person or organization. Do not let a model invent a plausible email to satisfy a schema. Route incomplete records for review. A field that passes format validation can still be inaccurate or belong to someone else.
Map the API contract
Read expected field names and validation rules before constructing the request. Keep richer research metadata separate from fields the destination supports. Happitap’s lead-submission flow includes name and contact details; an arbitrary agent response should not be posted unchanged. Test which combinations of required and optional values are accepted.
Preserve review context
Keep source references, review status, and unresolved questions in the research workflow. Record the review process so unexpected records can be investigated without rerunning the entire task. The submitted contact fields may be a useful operational summary, but they are not a replacement for the evidence behind the research.
Test boundaries before scheduling
Use fictional values to test missing details, malformed addresses, long fields, and repeated submissions. Keep credentials server-side and use the intended workspace hostname. Confirm error handling before regular runs. A successful API response establishes acceptance of a request, not the truth of the research that produced it.
Continue reading
Guide / AI workflows
Where AI fits in a responsible lead research workflow
Use AI to structure lead research while keeping source checks, human review, and integration testing in the process.
Read the guide →Guide / AI workflows
Prevent duplicate leads in a recurring automation
Decide how retries and repeat runs behave before submitting the same source records every day.
Read the guide →Guide / Lead data
How to prepare a lead spreadsheet for CSV import
A practical guide to cleaning names, email addresses, and phone numbers before importing a lead spreadsheet.
Read the guide → Browse all guides →