How to Integrate Retool with GetResponse

In GetResponse, click your account avatar in the top-right corner and select My Profile from the dropdown. In the profile menu, navigate to the Integrations & API tab. Scroll down to find the GetResponse API section. Click Generate API Key (or copy your existing key if one was previously generated). GetResponse API keys are account-level credentials — they have full read and write access to all data in your GetResponse account including contacts, lists, campaigns, autoresponders, and landing pages. Treat this key like a password: store it in Retool Configuration Variables, never share it, and regenerate it if you suspect it has been compromised. For GetResponse MAX (enterprise) accounts, the API base URL is different: instead of https://api.getresponse.com/v3, you'll use https://api3.getresponse360.pl/v3 or https://api3.getresponse360.com/v3 depending on your regional instance. You'll also need to add an X-Domain header with your enterprise domain value. Contact GetResponse support to confirm your exact enterprise API endpoint. For standard GetResponse accounts, the base URL is simply https://api.getresponse.com/v3 — no additional configuration needed beyond the API key.

In Retool, navigate to the Resources tab and click Add Resource. Select REST API from the connector list. Name: GetResponse API Base URL: https://api.getresponse.com/v3 For GetResponse MAX enterprise accounts, use your specific enterprise API URL instead. Authentication: Do NOT use the Bearer Token option. GetResponse requires a custom header format. Select No Authentication and instead add a Custom Header: - Header Key: X-Auth-Token - Header Value: api-key YOUR_API_KEY (include the literal text 'api-key ' followed by your actual key) For better security, store the API key in Retool Configuration Variables first: Settings → Configuration Variables → create GETRESPONSE_API_KEY → mark as secret. Then use the header value: api-key {{ retoolContext.configVars.GETRESPONSE_API_KEY }}. Add another header: Content-Type: application/json. For GetResponse MAX, also add: X-Domain: YOUR_ENTERPRISE_DOMAIN. Click Create Resource. Test with a GET query to /accounts — this returns your GetResponse account information. A 200 OK with account details confirms authentication. If you get 401, verify the X-Auth-Token header format includes the 'api-key ' prefix before your API key.

GetResponse uses the term 'campaigns' internally for what users see as 'contact lists' in the UI. Create a getCampaigns query: GET /campaigns to fetch all contact lists. The response is an array of campaign objects with: campaignId, name, createdOn, dayOfCycle (autoresponder cycle day for new contacts), subscribersCount, and languageCode. Create a getContacts query: GET /contacts with the following URL parameters: - campaignId: {{ select_list.value || '' }} (filter by selected list) - sort[createdOn]: desc (newest first) - page: {{ Math.floor(table_contacts.pagination.offset / 100) + 1 }} - perPage: 100 - fields: contactId,name,email,createdOn,campaign,tags,scoring,engagementScore The fields parameter reduces response size by fetching only the columns you need. GetResponse contacts include: contactId, name, email, campaign (object with campaignId and name), tags (array of tag strings), scoring (lead score), and engagementScore (0-100 engagement rating). Create a searchContacts query for lookup by email: GET /contacts?email={{ input_email.value }} — this returns contacts exactly matching the email address, useful for the detail view when a user searches for a specific contact.

1// Transformer for GetResponse contacts
2const contacts = data || [];
3return contacts.map(contact => ({
4  id: contact.contactId,
5  name: contact.name || 'No Name',
6  email: contact.email,
7  list: contact.campaign?.name || 'Unknown',
8  list_id: contact.campaign?.campaignId || '',
9  tags: (contact.tags || []).join(', '),
10  score: contact.scoring || 0,
11  engagement: contact.engagementScore || 0,
12  subscribed_at: contact.createdOn ? new Date(contact.createdOn).toLocaleDateString() : '',
13  engagement_label: contact.engagementScore >= 70 ? 'Highly Engaged'
14    : contact.engagementScore >= 40 ? 'Engaged'
15    : contact.engagementScore >= 10 ? 'Low Engagement'
16    : 'Inactive'
17}));

GetResponse uses the term 'newsletters' for one-time email campaigns (as opposed to autoresponders which are sequence-based). Create a getNewsletters query: GET /newsletters with parameters: - sort[createdOn]: desc - page: 1 - perPage: 25 - fields: newsletterId,name,status,createdOn,sendOn,statistics The statistics field embeds delivery metrics in the response: statistics.sent, statistics.opened (with unique and total sub-fields), statistics.clicked, statistics.bounced, and statistics.unsubscribed. Create a transformer to compute percentage metrics from the raw statistics counts. GetResponse provides unique opens and total opens separately — use unique opens for the open rate calculation. For campaign-level detail, create getNewsletterDetail: GET /newsletters/{{ table_campaigns.selectedRow.data.id }} to fetch the full campaign with subscriber-level activity data. For autoresponders (drip sequences), create a getAutoresponders query: GET /autoresponders?campaignId={{ select_list.value }} — this returns the autoresponder steps for the selected list with: subject, sendDelay (days after subscription), clicksCount, opensCount, and subscribersCount.

1// Transformer for email campaign performance
2const newsletters = data || [];
3return newsletters.map(nl => {
4  const stats = nl.statistics || {};
5  const sent = stats.sent || 0;
6  const opened = stats.opened?.unique || 0;
7  const clicked = stats.clicked?.unique || 0;
8  const bounced = (stats.bounced?.soft || 0) + (stats.bounced?.hard || 0);
9  const unsubscribed = stats.unsubscribed || 0;
10
11  const openRate = sent > 0 ? ((opened / sent) * 100).toFixed(1) : '0.0';
12  const clickRate = sent > 0 ? ((clicked / sent) * 100).toFixed(1) : '0.0';
13  const bounceRate = sent > 0 ? ((bounced / sent) * 100).toFixed(1) : '0.0';
14  const ctr = opened > 0 ? ((clicked / opened) * 100).toFixed(1) : '0.0';
15
16  return {
17    id: nl.newsletterId,
18    name: nl.name,
19    status: nl.status,
20    sent_at: nl.sendOn ? new Date(nl.sendOn).toLocaleDateString() : '',
21    total_sent: sent.toLocaleString(),
22    open_rate: `${openRate}%`,
23    click_rate: `${clickRate}%`,
24    bounce_rate: `${bounceRate}%`,
25    click_to_open: `${ctr}%`,
26    unsubscribed
27  };
28});

Build contact management actions using GetResponse's write endpoints. Create an updateContact query: PATCH /contacts/{{ table_contacts.selectedRow.data.id }} with body: { "campaign": { "campaignId": "{{ select_newList.value }}" }, "tags": {{ JSON.stringify(input_tags.value.split(',').map(t => t.trim())) }} }. This moves the selected contact to a different list and updates their tags. For bulk tagging, create a JavaScript query that loops over selected Table rows and patches each contact. Use Promise.all() for parallel execution with a concurrency limit of 5 contacts at a time. For the full-funnel landing page report, create a getLandingPages query: GET /landing-pages?page=1&perPage=25. Landing pages return: landingPageId, name, url, visits, uniqueVisits, campaignId (the list they feed), and conversionRate. Join landing page data with campaign subscriber growth: for each landing page's campaignId, compute the subscriber count growth over the landing page's active period from the getCampaigns data. This shows funnel conversion from visitor → subscriber → email engagement in a single Retool view. For marketing operations teams building GetResponse dashboards combined with internal CRM data, webinar registration tracking, and automated list segmentation workflows, RapidDev's team can help architect the complete Retool solution.

1// Transformer: join landing pages with campaign subscription data
2const pages = getLandingPages.data || [];
3const campaigns = getCampaigns.data || [];
4
5const campaignMap = {};
6campaigns.forEach(c => { campaignMap[c.campaignId] = c; });
7
8return pages.map(page => {
9  const campaign = campaignMap[page.campaignId] || {};
10  const conversionRate = page.visits > 0
11    ? ((page.uniqueConversions || 0) / page.uniqueVisits * 100).toFixed(1)
12    : '0.0';
13  return {
14    id: page.landingPageId,
15    name: page.name,
16    url: page.url || '',
17    total_visits: (page.visits || 0).toLocaleString(),
18    unique_visits: (page.uniqueVisits || 0).toLocaleString(),
19    conversion_rate: `${conversionRate}%`,
20    list_name: campaign.name || 'None',
21    list_subscribers: campaign.subscribersCount || 0
22  };
23});