Posted on

GetResponse for WordPress: Connect Contact Form 7 to GetResponse

GetResponse for WordPress usually means one thing, namely getting the people who fill in your website forms into GetResponse, without copying them by hand. This guide shows how to connect Contact Form 7 to GetResponse with ChimpMatic, so every form submission reaches the GetResponse list you choose, with the fields you map.

It covers the setup with the free Lite plugin, where to find your API key, how to map fields, how confirmation and consent work in GetResponse, and how to start GetResponse autoresponders and automations from a form. Then it closes with fixes for the problems people meet most often.

Short answer. For GetResponse for WordPress, install ChimpMatic Lite, open your form’s Contact Form 7 Extension tab, choose GetResponse, paste your API key, pick a list, map the email field and save.

Last updated: November 2026

Why use GetResponse for WordPress forms

Most WordPress sites collect email addresses through forms, such as a newsletter box, a contact form, a quote request or a download. Without a connection, those addresses sit in your inbox, and someone has to copy them into GetResponse. That is slow, and people get missed.

Once the form talks to GetResponse directly, every new contact arrives within seconds, with their name and details in the right fields. In addition, the consent checkbox decides who joins, so your list only holds people who asked to hear from you. And because each form has its own settings, a newsletter form and a quote form can feed different lists.

It works with lists and custom fields, and it also leaves contacts already on a list exactly as they are.

It also keeps things simple for your visitors. They fill in one form on your own site, and that is all. There is no second signup box and no trip to a hosted GetResponse page, so the form keeps your site’s look. Meanwhile, the whole setup takes about five minutes and needs no code.

Which WordPress forms to connect to GetResponse

  • Newsletter signup. The obvious one. People asked to join, so send them straight to your main list.
  • Download or lead magnet. Someone trades an email for a guide or checklist. Give the form its own list, so the right follow-up starts.
  • Quote or demo request. These are warm leads. A separate list keeps them apart from newsletter readers, and a consent box keeps it honest.
  • Contact form. Here a message is not a signup. Therefore, add a consent checkbox, so only people who tick it reach GetResponse.
  • Event or webinar registration. A dedicated list makes reminders and follow-ups easy, because you can email exactly those people.

In short, every form that collects an email address can feed GetResponse. The question for each one is simply which list it should join, and whether it needs a consent checkbox.

What you need for GetResponse for WordPress

  • A WordPress site where you can install plugins.
  • Contact Form 7 installed, with a form that already sends its notification email.
  • A GetResponse account with at least one list.
  • ChimpMatic Lite, free on WordPress.org.

GetResponse uses its own words for a few things, so this guide does too. It calls the list a list, each stored person a contact, and each stored detail a custom field.

How to set up GetResponse for WordPress, step by step

Follow the steps in order. Each one is small, but together they decide whether your list fills with complete contacts or bare email addresses.

GetResponse for WordPress: connect Contact Form 7 to GetResponse with ChimpMatic

Step 1: Install ChimpMatic Lite

First, install the free ChimpMatic Lite plugin from WordPress.org and activate it. Contact Form 7 must already be active, because ChimpMatic adds GetResponse to the forms you already have.

Step 2: Check that your form already works

Next, open your form under Contact → Contact Forms and send yourself a test. The notification email should arrive, since ChimpMatic adds the signup on top of it and never replaces it.

Step 3: Open the Contact Form 7 Extension tab

Then open the Contact Form 7 Extension tab in the form editor and choose GetResponse. Every form has its own tab, so each one keeps its own GetResponse settings.

Step 4: Paste your GetResponse API key

After that, paste your API key and connect. Your lists load at once. The section below shows where the key lives in GetResponse.

Step 5: Pick the list

Now choose the list that new contacts should join. If your account has several, compare the names carefully, because a working connection to the wrong list is the most common mistake.

Step 6: Map the fields, save and test

Finally, map the email field and the name, save the form, and send a test from an inbox you control. Then open the list in GetResponse and check the new contact.

If you run several forms, give each a clear name such as “Newsletter” or “Quote request”. Later, it then shows at a glance which form feeds which list.

Test the connection before you rely on it

  1. First, submit the form from an inbox you control, not a made-up address.
  2. Then open the list in GetResponse and find the new contact. Check that the name and every mapped field arrived.
  3. If confirmation is on, click the link in the confirmation email, and check the contact again.
  4. Finally, submit the form once more from the same address, and see what GetResponse does with a returning contact.

That last check tells you how GetResponse treats people who sign up twice. If the address is already on the list, GetResponse keeps the existing contact as it is. Knowing this up front saves confusion later, when someone fills in two of your forms.

Find your GetResponse API key

  1. Log in to GetResponse, click the Tools icon in the top menu and open Integrations and API.
  2. Select the API tab and click Generate API key.
  3. Name it (for example “ChimpMatic”) and copy it. A new key appears only once, so copy it before you close the window.

GetResponse’s own help covers this step too, in how GetResponse adds contacts. Treat the key like a password, because anyone who has it can manage your contacts. For that reason, ChimpMatic encrypts it before saving and never shows it again.

If the key stops working later, for example after someone regenerates it, the form keeps sending its emails but no new contacts reach GetResponse. So whenever you replace the key in GetResponse, paste the new one into the form’s tab as well.

Field mapping for GetResponse for WordPress

Field mapping tells ChimpMatic which answer goes into which GetResponse field. Contact Form 7 names each answer with a mail-tag such as [your-email] or [your-name]. GetResponse keeps the name on the contact and every other detail in custom fields. However, its API calls a list a campaign, so you may see both words. So mapping is simply matching one to the other.

Form field Typical mail-tag Where it goes in GetResponse
Email [your-email] The email address (required)
Name [your-name] The name custom field
Company or phone [your-company] A custom field you create in GetResponse first
Consent checkbox [acceptance your-consent] Decides whether the contact is sent at all

The email address is required, and ChimpMatic Lite also sends any three fields you choose. Pro has no field limit of its own, so a long form arrives complete and only your GetResponse list sets the limit. Either way, an unmapped field is not sent, which is why a list sometimes fills with bare email addresses. Therefore, map the name at least.

Keep the types matched as well. A date field in GetResponse needs a date in the form, and a number field needs a number, or GetResponse may reject the value. Also, if you rename a mail-tag in the form, update the mapping, because the old mapping points at a tag that no longer exists. The field mapping guide covers every case.

Confirmation is set on the list

In GetResponse, each list decides whether contacts confirm by email. In addition, new contacts are queued by GetResponse, so on a double opt-in list they appear only once they confirm. For the details, see GetResponse’s help on finding the API key, and the double opt-in guide explains when confirmation is worth it.

A message is not permission

A contact message is not permission to send marketing. Therefore, if the form is not a signup form, add a checkbox or acceptance field, and ChimpMatic sends people to GetResponse only when it is ticked. This matters most for visitors in the EU, where you need proof that someone agreed. It works the same way for every form and every list, in the free plugin too.

Keep your GetResponse list clean

A clean list costs less and reaches more inboxes, because most platforms charge by the number of contacts and judge senders by how many emails bounce. So three habits pay off. First, collect consent, so everyone on the list expects your emails. Second, map at least the name, so emails can greet people properly. Third, keep bots out, as the next paragraph explains.

Spam protection is that third habit. A public form will happily sync bot entries into your list, which inflates your contact count. So add a CAPTCHA or honeypot to the form before you connect it.

Start GetResponse autoresponders and automations from WordPress forms

Once contacts arrive in GetResponse, the next step is to email them automatically. GetResponse calls these autoresponders and automations. The simplest trigger is the list itself. Build one that starts when someone joins the list your form feeds, and every new contact from that form enters it.

  1. In GetResponse, create a new automation and choose “joins a list”, or the closest trigger GetResponse offers, as its starting point.
  2. Next, pick the same list your form feeds.
  3. Then add the first email, for example a welcome or the download the form promised.
  4. After that, add any delays and further emails.
  5. Finally, switch it on and send the form once from an inbox you control.

Because each form can feed its own list, you can give each form its own sequence. For example, a newsletter form joins one list and gets a welcome series, while a quote form joins another and gets a sales follow-up. With Pro, one form can also send people to several lists at once, so a single signup can start more than one sequence.

Good first sequences are short and specific.

  • Welcome. One or two emails that say what people will get from you, sent right after they join.
  • Delivery. The download, coupon or checklist the form promised, sent at once.
  • Follow-up. For quote and demo forms, a short note within a day, then a reminder a few days later.
  • Reminders. For events, a reminder before the start and the recording afterwards.

If confirmation is on, the sequence starts only after the contact confirms. So when you test, click the confirmation link first, then wait for the first email.

ChimpMatic Lite and Pro for GetResponse for WordPress

Feature Lite (free) Pro
Lists per form One Several at once
Fields sent Email plus any three Unlimited
Consent checkbox Yes Yes
Confirmation Follows the list’s setting Follows the list’s setting
Connect any number of forms Yes Yes
Priority support No Yes

For most sites, Lite covers the job, with one list per form, the email plus three fields, and consent. Pro is for sites that segment, with several lists per form and every field mapped. See everything the integration does on the Contact Form 7 GetResponse integration page, or compare plans and pricing.

Troubleshooting GetResponse for WordPress

Almost every problem is a setting. So start by turning on the Debug Logger in the plugin’s advanced settings, send a test, and read GetResponse’s exact answer in the log.

Problem Likely cause Fix
The contact does not appear right away GetResponse queues new contacts Wait a minute, then check whether the list uses double opt-in
ChimpMatic reports “already subscribed” The address is already on that list Nothing to fix. The existing contact stays
Custom fields arrive empty The form fields are not mapped to custom fields Map them and send a new test
The lists do not load The API key was copied incompletely or revoked Generate a new key and paste it again

Two causes are behind most of the remaining questions. The first is an unmapped field, which the field mapping guide fixes. The second is confirmation, since a contact who has not confirmed yet looks missing until they click the link. Finally, if the form marks an entry as spam, that entry never reaches GetResponse, so check your spam filter when real entries go missing.

Moving from Mailchimp to GetResponse for WordPress

Many sites that use GetResponse started on Mailchimp. With ChimpMatic, the move does not have to happen all at once, because each form picks its own platform. For example, you can switch the newsletter form to GetResponse today and leave the quote form on Mailchimp until its follow-up sequence is rebuilt.

  1. First, export your Mailchimp audience and import it into a GetResponse list, so existing subscribers come along.
  2. Next, rebuild your welcome email and any sequences as GetResponse autoresponders and automations.
  3. Then open one form’s Contact Form 7 Extension tab, choose GetResponse, paste your API key and pick the new list.
  4. After that, send a test and check the new contact on both sides.
  5. Finally, repeat for the next form when you are ready.

Because the plugin stays the same, your forms, field mappings and consent checkboxes keep working through the move. Only the destination changes, one form at a time.

GetResponse for WordPress: FAQ

How do I connect GetResponse to WordPress forms?

Install ChimpMatic Lite, open a Contact Form 7 form’s Contact Form 7 Extension tab, choose GetResponse, paste your API key and pick a list. From then on, every submission of that form reaches GetResponse.

Is GetResponse for WordPress free with ChimpMatic?

Yes. ChimpMatic Lite is free on WordPress.org and connects as many forms as you have. Pro adds several lists per form and unlimited mapped fields.

Do I need GetResponse’s own WordPress plugin as well?

No, not for your forms. ChimpMatic talks to GetResponse’s API directly, so your Contact Form 7 forms need nothing else.

Where do I find my GetResponse API key?

In short, Log in to GetResponse, click the Tools icon in the top menu and open Integrations and API. Select the API tab and click Generate API key. Name it (for example “ChimpMatic”) and copy it. A new key appears only once, so copy it before you close the window.

Can different WordPress forms feed different GetResponse lists?

Yes, because each form has its own tab with its own list, fields and consent rule. As a result, one site can feed several lists.

What happens if someone is already on the list?

If the address is already on the list, GetResponse keeps the existing contact as it is.

How does confirmation work with GetResponse?

In GetResponse, each list decides whether contacts confirm by email. In addition, new contacts are queued by GetResponse, so on a double opt-in list they appear only once they confirm.

How many fields can I send?

ChimpMatic Lite sends the email plus any three fields you choose. Pro has no limit of its own, so every custom field your GetResponse list has can be filled.

Can I start GetResponse autoresponders and automations from a WordPress form?

Yes. Build one that starts when someone joins the list your form feeds, and every new contact from the form enters it.

What if I rename the list in GetResponse?

Nothing breaks. ChimpMatic remembers the list itself, not its name, so the form keeps sending people to the same list under its new name.

Does it work with an acceptance field?

Yes. Map Contact Form 7’s acceptance field as the consent field, and ChimpMatic sends people to GetResponse only when it is ticked.

Will my form still send its notification emails?

Yes. ChimpMatic adds the signup and changes nothing else, so your form’s emails go out as before.

Can I use GetResponse and Mailchimp on the same site?

Yes. Each form picks its own platform, so one form can feed GetResponse while another still feeds Mailchimp. That makes a gradual move between platforms simple.

Where does my data go?

The email address, the fields you mapped and the consent choice go to GetResponse. In addition, the external services page lists every service the plugin connects to and what is shared.

Next steps with GetResponse for WordPress