GetResponse
Manage GetResponse email marketing, contacts, campaigns, automation, ecommerce, and account resources.
Verdict
Common use cases
- Add tags to contacts during campaign planning
- Cancel newsletter sends when copy needs revision
- Import contact lists from spreadsheets
- Create custom fields for segmentation
- Schedule A/B test cancellations
Integration
- Vendor
- GetResponse
- Category
- other
- Auth
- API_KEY
- Tools
- 50
- Composio slug
getresponse
Tools
- Add a new tag
Add a new tag.
- Cancel A/B test
Schedule cancellation of an A/B test.
- Cancel sending the newsletter
Cancel newsletter sending and turn the newsletter into a draft.
- Create a contact import
Start an asynchronous contact import into a campaign.
- Create a custom event
Create a custom event definition with typed attributes.
- Create a custom field
Create a custom field definition.
- Create address
Create an address in the connected GetResponse account.
- Create a file
Create a File Library file from base64-encoded content.
- Create a folder
Create a File Library folder.
- Create and send newsletter
Create a newsletter and immediately queue delivery, or schedule it when send_settings.sendOn is supplied. GetResponse limits this endpoint to 256 calls per day.
- Create a new contact
Submit a contact for asynchronous creation in a campaign. GetResponse returns no contact ID; use LIST_CONTACTS with the email filter to find the contact after processing.
- Create a predefined field
Create a campaign-specific predefined field in GetResponse.
- Create a subject A/B test
Create a subject-line A/B test with two to five variants and start or schedule delivery to its selected recipients.
- Create a suppression list
Create a new suppression list.
- Create autoresponder
Create an autoresponder that automatically delivers its message when the configured trigger and timing conditions are met.
- Create campaign
Create a campaign (contact list); configured double opt-in can automatically send confirmation emails, and subscription notifications can alert configured recipients.
- Create cart
Create a cart with its selected product variants.
- Create category
Create a shop category; setting is_default makes it the shop's default category and changes the previous default.
- Create 'From' address
Create a GetResponse sender name and email address.
- Create meta field
Create a meta field in a shop.
- Create multiple contacts at once
Submit multiple contacts for asynchronous creation in one campaign. GetResponse returns no contact IDs; use LIST_CONTACTS after processing to find accepted contacts.
- Create newsletter draft
Create a newsletter draft without sending or scheduling delivery. GetResponse requires send_settings but stores the message as a draft.
- Create order
Create an ecommerce order and trigger matching Make a purchase workflows unless additional_flags is skipAutomation.
- Create product
Create a product and its nested ecommerce data in a shop.
- Create product variant
Create a product variant with images, meta fields, and taxes.
- Create RSS newsletter
Create and configure an RSS-to-email newsletter, which can deliver new feed content when enabled. Requires the RSS email-marketing entitlement.
- Create search contacts
Create a saved contact search from condition sections.
- Create shop
Create an ecommerce shop.
- Create tax
Create a tax for a shop.
- Create the custom report
Schedule a one-time custom report. Requires a paid custom-reports entitlement, and available report types depend on the pricing plan.
- Create transactional email template
Create a reusable transactional email template.
- Delete A/B testdestructive
Delete an A/B test.
- Delete a contact by contact IDdestructive
Permanently remove a contact; when message_id is supplied, record the removal as an unsubscribe from that message, optionally with the source IP address.
- Delete a custom eventdestructive
Delete a custom event definition by ID.
- Delete a custom fielddestructive
Delete a custom field definition by ID.
- Delete addressdestructive
Delete an existing GetResponse account address.
- Delete a predefined fielddestructive
Delete an existing GetResponse predefined field.
- Delete autoresponderdestructive
Permanently delete an autoresponder.
- Delete cartdestructive
Delete a cart from a shop.
- Delete categorydestructive
Delete a category from a shop.
- Delete file by file IDdestructive
Permanently delete a File Library file by ID.
- Delete folder by folder IDdestructive
Permanently delete a File Library folder by ID.
- Delete 'From' addressdestructive
Delete a GetResponse 'From' address, optionally replacing its references with another address.
- Delete meta fielddestructive
Delete a meta field from a shop.
- Delete newsletterdestructive
Delete a newsletter by ID.
- Delete orderdestructive
Delete an order from a shop.
- Delete productdestructive
Delete a product from a shop.
- Delete product variantdestructive
Delete a product variant.
- Delete RSS newsletterdestructive
Permanently delete an RSS newsletter.
- Delete search contactsdestructive
Delete a saved contact search.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration', search for GetResponse, and select it. 3. In a new browser tab, log into your GetResponse account and go to Menu > Integrations & API > API. 4. Click 'Generate API Key', copy the key, and paste it into Switchy's API Key field. 5. Click 'Connect' — Switchy will validate the key and confirm the connection. 6. Open any Project in your workspace and type '@GetResponse list my campaigns' to test. 7. If the MCP returns campaign data, the setup is complete. 8. To invoke a tool, @mention GetResponse in a message and describe what you need — for example, '@GetResponse add a tag called Q1-Leads to my main campaign'. 9. The AI will call the appropriate tool and return the result inline.
What teammates see: by default, memories from GetResponse are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add Campaign Tag
@GetResponse add a tag called 'Webinar-Jan2024' to my account. Confirm when it's created.
Cancel Newsletter Send
@GetResponse cancel the newsletter scheduled for tomorrow at 9am and turn it back into a draft. Let me know when it's done.
Import Contact List
@GetResponse start a contact import into my 'Q1 Leads' campaign. I'll provide the CSV data in the next message.
Create Custom Field
@GetResponse create a custom field called 'Industry' with type 'text'. I want to use it for audience segmentation.
List Active Campaigns
@GetResponse show me all active campaigns in my account, including subscriber counts and creation dates.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@GetResponse show me all contacts tagged 'webinar-2024' who opened our last three newsletters
Found 247 contacts matching your criteria. The most engaged segment includes contacts from the US (89), UK (43), and Canada (31). Average open rate across these contacts is 68%, significantly above your account average of 42%. Top three contacts by engagement: sarah.chen@example.com (opened all 3, clicked 5 links), mike.torres@example.com (opened all 3, clicked 3 links), and anna.kowalski@example.com (opened 2, clicked 4 links). All contacts are currently subscribed to your 'Product Updates' campaign.
This example demonstrates GetResponse's contact segmentation and engagement tracking capabilities. Requires read access to contacts, tags, and newsletter statistics via API key. Note that contact data refreshes may lag by up to 15 minutes, and large contact lists (10K+) may require pagination that affects response time.
@GetResponse create a custom field called 'preferred_demo_time' for storing appointment slots, then add it to all contacts in the 'sales-qualified' campaign
Custom field 'preferred_demo_time' created successfully with type 'text' and added to your account schema. Applied the field to 412 contacts in the 'sales-qualified' campaign. The field is now available in your contact forms, import mappings, and segmentation rules. Existing contacts will show this field as empty until populated. You can bulk-update values via CSV import or set them individually through the contact management interface.
This showcases GetResponse's schema customization and bulk contact operations. Creating custom fields is permanent (deletion requires support contact), and the field will appear across all campaigns once created. Be mindful that custom field limits vary by plan tier—most accounts support 10-20 custom fields total.
@GetResponse draft a newsletter announcing our Q1 product releases, pull content from the last 5 blog posts tagged 'feature-launch', and schedule it for next Tuesday at 10am EST to the 'active-users' segment
Newsletter draft created: 'Q1 Product Release Highlights'. Pulled content from 5 blog posts (Jan 15 - Mar 8) covering the new dashboard redesign, API v3 launch, mobile app updates, integration marketplace, and advanced analytics suite. Generated subject line: 'Your Q1 Update: 5 New Features to Explore' with preview text highlighting the dashboard redesign. Newsletter is scheduled for Tuesday, April 2 at 10:00 AM EST to 3,847 contacts in 'active-users' segment. A/B test option available if you want to test subject lines before full send.
This example combines GetResponse's content integration, AI-assisted drafting, and scheduling capabilities. The MCP can pull blog content but cannot verify link validity or image availability—review the draft in GetResponse's editor before confirming send. Scheduling requires timezone conversion accuracy; always verify the final send time in your GetResponse dashboard.
Use-case deep-dives
When GetResponse MCP fits a product drop workflow
A 6-person DTC brand is launching a new product line and needs to coordinate email campaigns, import customer segments, and tag buyers in real time as orders come in. The GetResponse MCP is the right call here because it exposes the full campaign lifecycle—create custom fields for product preferences, import segmented contact lists, schedule A/B tests on subject lines, and trigger tag additions when Shopify webhooks fire. The 50-tool scope means you can script the entire launch sequence in one Switchy thread instead of clicking through the GetResponse UI 40 times. The threshold: if your team sends fewer than 2 campaigns a month, the MCP is overkill—just use the web app. But for brands running weekly drops or multi-variant tests, this MCP turns launch day into a repeatable playbook.
Using GetResponse MCP to keep help docs current
A 3-person SaaS support team maintains a knowledge base in Notion and sends onboarding sequences through GetResponse. Every time they update a help article, they need to refresh the corresponding email template and re-import contact segments who haven't opened recent messages. The GetResponse MCP handles the sync: create a file in the library from the updated Notion export, update custom fields to flag contacts who need the new content, and cancel any in-flight newsletters that reference the old version. The API key auth means the support lead can delegate this to a junior without sharing login credentials. The boundary: if your knowledge base changes less than once a week, manual updates are faster. But for teams shipping docs daily, the MCP keeps email and help content in lockstep without a Zapier tax.
When GetResponse MCP scales webinar workflows
A 4-person B2B marketing team runs monthly webinars and needs to import registrants from Eventbrite, tag attendees versus no-shows, and trigger follow-up sequences based on poll responses. The GetResponse MCP is the move: create a contact import for each event, add tags as attendance data comes in, define custom events for poll answers, and schedule A/B tests on the replay email subject lines. The 50 tools mean you can handle registration spikes without rate-limit drama—import 2,000 contacts in one call, then batch-tag them as the webinar runs. The trade-off: if you run fewer than 3 events a quarter, the setup overhead isn't worth it. But for teams doing weekly or bi-weekly webinars, the MCP turns event ops into a one-thread script you run every time.
Frequently asked
What does the GetResponse MCP let me do in Switchy?
The GetResponse MCP gives your AI agents direct access to your email marketing operations. They can manage contacts, create and cancel newsletters, define custom fields and events, import subscriber lists, add tags, and upload files to your library. Think of it as letting your AI handle routine campaign setup and list management without switching to the GetResponse dashboard.
Do I need admin access to connect GetResponse?
You need an API key from your GetResponse account, which typically requires account owner or admin permissions to generate. The key grants full access to the 50 tools exposed by this MCP, so whoever connects it should understand they're giving Switchy write access to campaigns, contacts, and custom fields. Check your GetResponse account settings under Integrations to create the key.
Can the MCP send emails or just manage drafts?
The MCP can cancel scheduled newsletters and turn them back into drafts, but it doesn't directly trigger sends. You'll still approve final campaign sends in GetResponse itself. This is intentional — it prevents accidental mass emails while letting your AI prep campaigns, import contacts, and handle A/B test logistics. For actual sending, use GetResponse's native approval flow.
Why use this instead of GetResponse's API directly?
The MCP wraps GetResponse's API in a format your AI agents understand natively. Instead of writing custom code to parse JSON responses and handle auth, your agents just ask for what they need in plain English. You trade some flexibility for speed — the 50 exposed tools cover common workflows, but niche API endpoints aren't included. For one-off tasks, the MCP wins. For complex automation, consider the API.
Who on the team should connect this integration?
Whoever owns your email marketing strategy and has API key access in GetResponse. This person should understand which campaigns and lists the AI will touch, since the MCP grants write access to contacts, tags, and custom fields. If multiple people manage GetResponse, decide upfront who's responsible for auditing what the AI changes. The connection doesn't consume extra Switchy seats.