Verify your GoHighLevel contacts before a campaign

The workflow

1. In the sub-account open Contacts, select the contacts (or a Smart List), then More (the three dots next to + Add Contact) > Export and confirm. Track the job under Contacts > Bulk Actions and download it there; only Agency Admins and Location Admins can download, and files stay available for 30 days.
2. Upload the CSV on the verify page, signed in; the first 100 checks are free. The email column is found by its header or contents and every other column is kept.
3. When the job finishes, download the valid, risky and invalid files. Each keeps all of your original columns.
4. Pick a tag for each result you will use, for example email-invalid. HighLevel has no direct undo for imports, and tagging on upload lets you filter and reverse the change later.
5. Go to Contacts > Import Contacts, upload the invalid file as a CSV (HighLevel takes CSV only, a single sheet, under 30 MB to be safe), map Email and the Contact ID column, and choose Update rather than Create. Add the tag during the upload.
6. Watch Contacts > Bulk Actions for the job; Show Stats gives the totals and the Error tab has a downloadable log. Then add a condition to your workflows: tag email-invalid is not present.

Columns to map

• Contact ID where possible; when updating, HighLevel checks Contact ID first, then Email, then Phone.
• Email, plus a tag applied at upload for each result file.
• Leave a DND column out: HighLevel applies DND to all channels at once, which could stop SMS to someone whose only problem is a bad email.

What to do with risky and catch-all results

Risky contacts can still be real leads that answer by SMS or phone. Tag them email-risky and keep them in SMS and call workflows, but route email through a slower sequence. Treat invalid as unreachable by email only, not as a reason to delete the contact.

What people use it for

• An agency cleaning a client's lead list before the first email campaign in a new sub-account.
• Checking contacts that arrived through funnel forms and Facebook lead ads before a nurture sequence.
• Keeping sending-domain reputation clean in an account that mixes email and SMS workflows.

Using the result

Each address comes back valid (the mail server confirmed the mailbox), risky (delivery could not be confirmed: a catch-all domain, a role address such as info@, or a provider that hides mailbox status) or invalid (it will bounce, or it is a throwaway address).

Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.

Comparing tools? See email verifiers for GoHighLevel compared, with prices checked on each vendor’s site.

Common questions

Which plans include API access for GoHighLevel?

API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.

Can SimpleVerifier run inside a HighLevel workflow?

There is no native step. A workflow's webhook action could call the SimpleVerifier API with your key (API access needs a plan that includes it), but we do not ship or support a HighLevel template; the CSV route above is the documented one.

I manage many sub-accounts. How do I do all of them?

HighLevel exports are per location, so repeat the export and import in each sub-account. You can upload the files one after another; the free checks apply once per account.