GetResponse Email Verification

Verify each new GetResponse subscriber with an n8n workflow and save the verdict in a custom field, or clean a list from a CSV export.

MailTester NinjaGetResponse

Keep your GetResponse lists clean. MailTester Ninja checks each address against the recipient's mail server, without sending any email, and writes the verdict into two GetResponse custom fields. You can then leave invalid addresses out of your newsletters and autoresponders, keep your bounce rate low and protect your sender reputation. Verify every new subscriber automatically, or clean an existing list in one pass.

What you need

  • A GetResponse account and a GetResponse API key: in GetResponse, open Integrations and API, then API, and generate a key.
  • A MailTester Ninja key: a free API token to try it (50 checks a day, one request every 30 seconds) or a paid key for whole lists.
  • For the automatic check: n8n with our official MailTester Ninja node (verified by n8n, on n8n Cloud or self-hosted), or Make or Zapier.

Step 1: add two custom fields in GetResponse

In GetResponse, open Contacts, then Custom fields, and create two text fields:

  • mt_code: the verdict code, ok, ko or mb.
  • mt_verdict: the detailed status, for example Accepted, Rejected, Catch-All or Disposable.

Step 2: verify every new subscriber automatically (n8n)

This workflow runs each time someone subscribes to one of your GetResponse lists. It verifies the address and saves the verdict on the contact.

  1. In n8n, install our node from the nodes panel: search for MailTester Ninja, then click Install (details on our n8n page).
  2. Download the workflow getresponse-verify-new-subscribers.json, then in n8n choose Workflows, then Import from file.
  3. Open the two GetResponse nodes and create a GetResponse credential with your API key. Open the MailTester Ninja node and create a MailTester Ninja API credential with your key.
  4. In Save the verdict in GetResponse, pick mt_code for the first custom field and mt_verdict for the second. In the trigger, choose the lists to watch.
  5. Publish (or activate) the workflow. The trigger registers the GetResponse callback for new subscribers on its own.

With Make or Zapier: watch new contacts with the GetResponse app, verify the address with an HTTP request as shown on our Make and Zapier pages, then update the GetResponse contact with mt_code and mt_verdict.

Step 3: use the verdict in GetResponse

In Contacts, search with a condition on the custom field mt_code and save each search as a segment.

mt_codeMeaningWhat to do in GetResponse
okValid and deliverableKeep the contact in your newsletters and autoresponders.
koInvalid, will bounceExclude the segment from your sends, or remove the contacts.
mbUncertain (catch-all domain, server could not be probed)Send to them in smaller batches, after your valid contacts, and drop those that never engage.
--No verdict (key problem, or free limit reached)Verify again later. Never remove a contact on this answer.

Clean an existing GetResponse list

  1. In GetResponse, open Contacts, select the list and export the contacts as a CSV file.
  2. Drop the file on the MailTester Ninja verifier with a paid key, wait for the results, then click Save.
  3. Open the saved file, delete the explanation lines at the top (everything above the first address), and add this first line: email,name,domain,mx,mt_code,mt_verdict.
  4. In GetResponse, import the file into the same list, map email, mt_code and mt_verdict, skip the other columns, and choose to update existing contacts.
  5. Build the segments from step 3 and leave out ko before your next send.

Developers can do the same through the APIs: read the contacts with GET https://api.getresponse.com/v3/contacts, verify each address with https://happy.mailtester.ninja/ninja?email=ADDRESS&key=YOUR_KEY, then write the verdict with POST https://api.getresponse.com/v3/contacts/{contactId} and a customFieldValues body. Keep about one request per second on a paid key (11 requests per 10 seconds on Pro).

Keep your keys secret

Store both keys in n8n, Make or Zapier credentials rather than in a node field, so an exported workflow never contains them.

Questions

Does the check send an email to my subscribers?

No. MailTester Ninja opens a conversation with the recipient's mail server and stops before any message is sent. Your subscribers receive nothing.

Is anything stored?

No. Each address is checked in real time and we keep no copy of the addresses you verify. The verdict lives only in your GetResponse account.

Why verify people who subscribed on their own?

Signup forms collect typos, disposable inboxes and fake addresses, and lists decay as people change jobs. Mailbox providers read a high bounce rate as a sign of a bad sender, so removing these addresses keeps your GetResponse emails in the inbox.

Try it now

Get a free API token, or see the plans for up to 200,000 checks a day. Full reference: API documentation and OpenAPI specification. Back to all integrations.