Faster time to market
Ship GetResponse automations faster with pre-built actions and templates.
GetResponse Connector
Build in-app email marketing workflows that create and update contacts, send campaign and transactional messages, manage campaigns and trigger automations. Ship multi-tenant customer integrations and expose governed actions for subscribers, campaigns and messages.
Reusable orchestration
Create reusable workflows for contacts, campaigns and message routing.
Multi-tenant governance
Expose approved methods as governed MCP tools per customer.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate and automate contacts, campaigns, messages, webhooks and automations in GetResponse. Use Cyclr to map SaaS customer accounts, add or update contacts, subscribe contacts to campaigns, send messages and route webhook events into downstream systems. For API details and available endpoints see the GetResponse API documentation.
PRODUCT USE CASES
Top Use Cases for GetResponse Integrations
Quickly build customer-facing automations that keep subscriber data moving between your app and GetResponse. Automate list syncs, campaign triggers, webhook-driven events and message sends across many tenant accounts.
Create or update a contact and add to campaign
On new SaaS sign-up, create/update a GetResponse contact and add them to a campaign (contacts and campaigns endpoints).
Trigger campaign or autoresponder from product events
When users hit product milestones, trigger campaign sends or autoresponders using Messages and Campaigns endpoints.
Respond to GetResponse webhooks in real time
Receive subscribe/unsubscribe and click webhooks to update tenant records, enable or disable features and sync CRM data.
ORCHESTRATION
How GetResponse works with Cyclr
Cyclr sits between your SaaS product and GetResponse to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
GetResponse
GetResponse processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore GetResponse methods you can orchestrate through Cyclr.
Contacts2
Get Contacts
ActionGets all of the contacts
Get Contacts By ID
ActionGets a single contact by ID
Lists3
Get Lists
ActionGets all of the lists
Get List Contacts
ActionGet all the contacts in the list
Add Contact To List
ActionAdds a contact to a list
TECHNICAL DETAILS
GetResponse integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing GetResponse integrations in Cyclr.
API and authentication
- API host
https://api.getresponse.com/v3- Authentication
- API key; OAuth 2.0
- Credentials
API key; OAuth client ID and secret; OAuth redirect URI; X-Domain for GetResponse MAX accounts.
- Method categories
Contacts; Campaigns; Messages; Webhooks; Automations; Forms; Landing pages; Files; Statistics
Pagination and rate limits
Pagination
Paged collections use page and perPage parameters; default 100, max 1000; headers include TotalCount.
Rate limits
30,000 calls per 10 minutes, 80 calls per second, up to 10 parallel requests. Headers X-RateLimit-Limit and X-RateLimit-Remaining returned.
IMPLEMENTATION
Authentication at a glance
GetResponse supports API key via X-Auth-Token (prefix ‘api-key’) and OAuth 2.0. MAX accounts require an X-Domain header. Confirm which methods Cyclr enables in Console.
- Authentication method
- API key; OAuth 2.0
- Credential required
API key; OAuth client ID and secret; OAuth redirect URI; X-Domain for GetResponse MAX accounts.
Before you begin:
View setup guideGetResponse MAX accounts use different API host and require X-Domain. APIv3 doesn’t support CORS; use server-side proxy.
COMMON QUESTIONS
Frequently asked questions
It synchronizes contacts, manages campaigns, sends messages, triggers automations and handles webhook events. Use these flows to keep subscriber data and campaign activity synchronized between your app and GetResponse.
Use an API key in the X-Auth-Token header (prefix ‘api-key’) or OAuth 2.0. GetResponse MAX accounts also require an X-Domain header; confirm enabled auth methods in Cyclr Console.
Yes. Build multi-tenant flows that store per-customer credentials and map tenant accounts to distinct GetResponse campaigns and contacts using Cyclr orchestration.
Yes. You can expose approved actions (for example send message, create contact, add to campaign) as governed MCP tools so product teams control what customers can run.
KEEP EXPLORING
Related resources and connectors
Documentation
Email Marketing Integrations to make your daily tasks easier
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorBluecore
Related Marketing connector for customer-facing integration workflows.
Related connectorLead Squared
Related Marketing connector for customer-facing integration workflows.
Related connectorLeadfox
Related Marketing connector for customer-facing integration workflows.