> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/integrations/getresponse.md).
# GetResponse
Send quote requesters to a GetResponse list for email marketing follow-up.
Connecting GetResponse means every quote request also becomes a contact you can follow up with, without anyone copying details by hand.
{% hint style="info" %}
GetResponse is listed under the **PRO** plan. Klaviyo, Mailchimp and Shopify are the integrations listed under **FREE**. See [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md).
If the controls here are greyed out and a padlock line reads "🔐 This feature is available on …", that is your plan and not a fault. Follow the link in that line, or open **Pricing plans** in the app.
{% endhint %}
## Step 1 — Get your API key
In your GetResponse account, generate an API key. GetResponse's own guide walks through it: [Where do I find the API key?](https://www.getresponse.com/help/where-do-i-find-the-api-key.html).
Keep the key somewhere safe while you finish the setup.
{% hint style="info" %}
GetResponse calls its lists campaigns. Make sure you pick the one you actively send from.
{% endhint %}
## Step 2 — Connect it in the app
{% stepper %}
{% step %}
### Open the Integrations tab
In your Shopify admin, open **SA Request a Quote**, select **Advanced settings**, then open the **Integrations** tab.
{% endstep %}
{% step %}
### Select GetResponse
Under **Third-party integration**, select **GetResponse** — described in the app as "Grow your GetResponse audience".
The GetResponse page opens, with a **Third-party** breadcrumb to take you back to the list.
Pick the service, then open its settings.
{% endstep %}
{% step %}
### Turn on Enable
Switch on **Enable**. Nothing is sent to GetResponse until you do.
{% endstep %}
{% step %}
### Paste your API key
Paste the key from Step 1 into the **API key** field.
{% endstep %}
{% step %}
### Choose the list and match your fields
Pick the GetResponse list new contacts should join, and the mapping rows appear beneath it on their own. Line up your quote form fields — the **Contact information** fields such as Email address, First name and Last name — with the matching fields in GetResponse.
Create the list in GetResponse first — the app can only offer lists that already exist. Email address is the one mapping you cannot skip: without it there is no contact to create. The rest are optional.
Choose the list first — the mapping appears once it is set.
{% endstep %}
{% step %}
### Save
Select **Save**. Nothing is stored until you do, and an unsaved page sends nothing.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
[Mailchimp](/sa-request-a-quote/integrations/mailchimp.md) walks through the same sequence with every control named, if you want to see what each step looks like before you start.
{% endhint %}
## Step 3 — Test it
Submit a real quote request from your storefront, then check GetResponse for the new contact. Confirm the fields you matched actually arrived — not just the email address.
{% hint style="warning" %}
Do not skip the test. A connection can look active and still deliver nothing useful if the fields are matched wrongly, and you will not notice until you try to use the data.
{% endhint %}
## Is this the right tool?
A fit if you already run your email marketing and landing pages in GetResponse.
If you do not already use GetResponse, do not adopt it just for this — [Zapier](/sa-request-a-quote/integrations/zapier.md) connects quote data to almost anything, and [Create a Shopify customer after submit](/sa-request-a-quote/integrations/create-shopify-customer.md) keeps everything inside Shopify on the **FREE** plan.
## If contacts are not arriving
* **Check Enable is still on.** Nothing is sent while it is off.
* **Check the key is still valid.** Regenerating a key in GetResponse breaks the connection until you paste the new one in. Saved keys are shown masked, so paste a fresh one if in doubt.
* **Check you picked the right list.** Contacts may be arriving somewhere you are not looking.
* **Check the email field is matched.** Without it there is no contact to create.
Still stuck? Email .
## Next steps
* [Integrations overview](/sa-request-a-quote/integrations/overview.md) — the other tools you can connect
* [Build a standard form](/sa-request-a-quote/quote-form/build-standard-form.md) — make sure your form collects what you are matching
* [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md) — what the PRO plan includes
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.samita.io/sa-request-a-quote/integrations/getresponse.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
