Use files for reviewed batches
A CSV import suits an existing contact list or a periodic batch that benefits from human review. It gives the team a file to inspect and map before submission. The tradeoff is responsibility for preparation, timing, and avoiding repeated uploads of the same records.
Use events for ongoing submissions
An event-based connection can send an enquiry when it occurs. This reduces manual transfer work but introduces credential handling, validation, and delivery failure management. Confirm the capabilities on both sides. The presence of a webhook setting does not establish compatibility with every destination or guarantee complete field mapping.
Plan duplicate handling
An event may arrive more than once after a delayed response. A file can also be uploaded twice by people who did not realize processing had started. Define how the workflow recognizes previously submitted source records. Retrying creation without a clear rule can turn a temporary delay into permanent duplicate data.
Start with the smallest reliable process
A validated CSV sample can establish which fields matter before an automation is built. For ongoing enquiries, test provider delivery and the destination record together. Happitap offers imports and integration paths; choose the method your team can operate, review, and troubleshoot rather than the one that merely sounds more automated.
Continue reading
Guide / Integrations
How to test a lead form integration end to end
Verify that a submission creates a usable lead, not merely that configuration was saved.
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 →Guide / Follow-up
A practical lead follow-up routine for small teams
Build a repeatable daily process for reviewing enquiries, preparing useful replies, and recording next steps.
Read the guide → Browse all guides →