Verify Typeform leads with NeverBounce before they hit HubSpot

Build an agent workflow that runs on a cron every 15 minutes during business hours (weekdays, 9am to 6pm local time) and processes new lead-capture responses from a single Typeform form.

On each run, call Typeform Retrieve Responses for the configured form using a since cursor that covers the most recent window (the time of the last successful run, with a small safety overlap). Keep track of which Typeform response IDs have already been processed so the same submission is never written downstream twice within a run or across runs.

For every new response that has an email address, call NeverBounce Verify Single Email to check deliverability. The result code will be one of valid, invalid, disposable, catchall, or unknown, optionally with a typo suggestion.

For valid and catchall results: first call HubSpot Search Contacts to check whether a contact with that email already exists. If it does, skip the create step. If it does not, call HubSpot Create Contact with the form fields mapped onto standard contact properties (email, first name, last name, company, phone, etc.) plus a custom nb_status property set to the NeverBounce result code so the RevOps team can see why the contact was admitted.

For invalid, disposable, and unknown results: do not push the lead into HubSpot. Instead call Google Sheets Append Values to write the row to a Form Rejections tab in the configured spreadsheet. Each row should include the email, response timestamp, NeverBounce result code, any typo suggestion NeverBounce returned, and the original form field values, so marketing or RevOps can later eyeball borderline cases without polluting the CRM.

De-duplicate within the run (and across runs) by tracking the Typeform response IDs already handled. If the same response is encountered twice in the same sweep, process it only once. Surface a short per-run summary noting how many responses were verified, how many landed in HubSpot, and how many were logged as rejections.