GetResponse in Hummerce is an integration with the GetResponse mailing system - the store automatically sends customer data with newsletter status, abandoned carts, orders and the product catalog, so email campaigns and marketing automation run on the store's current data, with no manual export.
Last updated: 2026-09-29.
¶ Benefits and use cases
- Email campaigns on the store's current data - customers with newsletter consent land in the selected GetResponse campaign automatically, with no manual list export.
- Abandoned cart recovery - the store sends GetResponse data for carts not updated for a set number of hours, ready for automation reminding customers to complete their purchase.
- Order tracking in campaign statistics - status, payment and order value update in GetResponse on every change, so mailing reports show real sales from campaigns.
- Product catalog for recommendations and product newsletters - name, price, category, photo and product address sync with GetResponse for use in automations and message product blocks.
- Personalized links with automatic customer recognition - a campaign link can carry a unique subscriber identifier, so the store recognizes the customer after clicking the message, with no login needed.
- Language versions of campaigns - customers land on a separate GetResponse list for each store language.
¶ What and when the store sends to GetResponse
- Customers - a customer who consented to the newsletter lands in the GetResponse campaign configured for their language (separate lists per language, e.g. PL/DE/FR). A change to customer data (first name, last name, address, phone, newsletter consent and other selected fields) updates their card in GetResponse.
- Abandoned carts - a cart not updated for longer than the configured number of hours goes to GetResponse with its value, currency, chosen variants and a link to the saved cart - ready for a reminder automation.
- Orders - an order and its status changes (payment, delivery, order status) sync to GetResponse together with the value, delivery and billing address, and the delivery and payment methods used.
- Product catalog - the name, address, manufacturer, category, price (gross and net) and photo of the product and variant sync to GetResponse, for use in message product blocks and recommendations.
- Separate scheduled tasks handle sending customers, carts and orders - each can be turned on or off independently in the module configuration.
An order has two parameters showing the sending status:
- GetResponse send status (
_getResponseSendStatus) - values include "sent" and "error"; the parameter's change history shows the sending attempts.
- GetResponse order ID (
_getResponseOrderId) - filled in once GetResponse assigns the order its own identifier, meaning it accepted it correctly.
A link in a message's content (e.g. a button in a newsletter) can carry an extra parameter with a unique subscriber identifier stored in GetResponse. The store uses it to recognize the customer after they click - including when saving cart contents - with no login required. Such a link is set up in GetResponse as a custom protocol link, with the store's parameter and a value taken from a subscriber's custom field.
- The integration is part of the Hummerce platform - it works in all current store versions.
- A GetResponse account and an API integration key generated in the GetResponse account settings.
- The customer's newsletter consent decides whether they land in a GetResponse campaign - see Newsletter - signups and consent.
- The product and category address in the data sent to GetResponse uses the store's friendly URLs, when defined.
- Requires implementation - the integration doesn't switch on by itself. Scope: creating a GetResponse account, getting the integration key, configuring the module in the store panel (key, default campaign, per-language lists, customer/cart/order sending tasks), mapping customer and product fields, testing the sending.
- Minimum estimated time: basic configuration (key, campaign, sending customers) - from 4 h; adding cart and order sync - from 3 h; product catalog sync - from 3 h.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on: the number of languages and GetResponse lists, the scope of synced customer and product fields, the need for additional automations on the GetResponse side (beyond configuring the store itself).
- Copying a product in the panel also copies its GetResponse identifiers (product and variant) - a new product created from the copy needs those identifiers cleared, otherwise sending it to GetResponse returns an error (a product with that identifier already exists there).
- Changing a product's type (a regular item to a variant or the other way around) after it already reached GetResponse under the previous type can block further syncing of that product - it's best to settle on the product type before its first order or cart addition.
- An article or product without a name won't send correctly to GetResponse - the product name is required.
- We do not verify the configuration for legal compliance (e.g. newsletter consent wording, GDPR) - the legal basis and consent wording are up to the store.
- Automatic clearing of GetResponse identifiers when copying a product, to avoid a manual fix after changing the product type.
Does Hummerce only send customers subscribed to the newsletter to GetResponse?
Yes. Only customers who consented to the newsletter land in a GetResponse campaign.
Can you check in the store panel whether a given order reached GetResponse?
Yes. Order parameters show the sending status and the identifier assigned by GetResponse.
Does the integration send abandoned carts to GetResponse?
Yes, carts not updated for longer than a set number of hours, together with a link to complete them.
Does the product catalog sync automatically with GetResponse?
Yes, the product and variant's name, price, category, photo and address update in the background.
How long does a GetResponse integration take?
Basic configuration (key, campaign, sending customers) - from 4 h. Carts and orders - from 3 h each, product catalog - from 3 h.
What happens if I copy a product that was already sent to GetResponse?
The copy inherits the original's GetResponse identifiers, which blocks sending the new product - they need to be manually removed from the copy before the first sending.
Want to see how a GetResponse integration could work in your store? Contact the Hummerce team (in Polish).
- Module configuration (group GetResponse): API integration key, API address and domain, default campaign, export of customers created after a date, callback function, customer/cart/order sending tasks and their start dates, cart inactivity hours before sending, cart item price source, default phone prefix, log settings (show, save, delete older than X days).
- Customer tagging from a GetResponse link: the request parameter and subscriber custom field used to recognize a customer after clicking a campaign link, optionally through a cookie.
- Order parameters: the sending status and GetResponse identifier visible in the order details and its change history.
¶ REST API and MCP
- No dedicated REST API operations or MCP tools for GetResponse - syncing runs as background scheduled tasks.
- MCP (AI assistant - MCP server): general configuration and maintenance tools (
ec2_config_search, ec2_config_get, ec2_config_set, ec2_modules_list, ec2_task_run, ec2_task_log) also work on the GetResponse module; the integration key, as a secret, isn't read or written by the assistant - it's changed in the panel.
The module doesn't add its own customer-facing messages in the store - data is exchanged in the background.
| Symbol |
Object |
Label |
_getResponseSendStatus |
order |
GetResponse send status |
_getResponseOrderId |
order |
GetResponse order ID |
_getResponseProductId |
item |
GetResponse product ID |
_getResponseVariantId |
item |
GetResponse variant ID |
_getResponseContactId |
customer cart |
GetResponse contact ID |