GetResponse MCP integration for AI agents.
Connect AI agents to GetResponse through 14 structured actions, including get campaign, create campaign, and delete contact. Review authentication, inputs, w…
- ACTION CONTRACTS
- 14
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the GetResponse integration exposes
The GetResponse Agent App exposes 14 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent retrieve one getresponse campaign by id, create a getresponse campaign for organizing contacts, and permanently delete a getresponse contact by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected GetResponse account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real GetResponse capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADRetrieve one GetResponse campaign by ID.
INPUTS: campaignId
create_campaignWRITECreate a GetResponse campaign for organizing contacts.
INPUTS: name / languageCode / apiOptIn
delete_contactHIGH IMPACTPermanently delete a GetResponse contact by ID.
INPUTS: contactId
create_contactWRITEQueue a contact for creation in a GetResponse campaign.
INPUTS: email / name / campaignId / dayOfCycle / scoring
get_contactREADRetrieve one GetResponse contact by ID.
INPUTS: contactId
get_newsletterREADRetrieve one GetResponse newsletter by ID.
INPUTS: newsletterId
get_newsletter_statisticsREADRetrieve delivery and engagement statistics for one GetResponse newsletter.
INPUTS: newsletterId / groupBy / createdFrom / createdTo / page
list_campaignsREADList GetResponse campaigns, which represent contact lists.
INPUTS: name / isDefault / sortBy / sortOrder / page
list_contactsREADList and search GetResponse contacts with page-based pagination.
INPUTS: email / name / campaignId / exactMatch / createdFrom
list_custom_fieldsREADList GetResponse custom fields that can be assigned to contacts.
INPUTS: name / sortOrder / page / perPage
list_newslettersREADList GetResponse newsletters with filters and pagination.
INPUTS: name / subject / status / type / campaignId
list_tagsREADList GetResponse tags that can be assigned to contacts.
INPUTS: name / createdFrom / createdTo / sortBy / sortOrder
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
campaignIdOPTIONAL- A GetResponse resource identifier.
create_campaign
nameREQUIRED- A unique campaign name between 3 and 64 characters.
languageCodeOPTIONAL- The campaign language code, such as EN.
apiOptInOPTIONAL- The opt-in mode for contacts added through the API.
delete_contact
contactIdOPTIONAL- A GetResponse resource identifier.
create_contact
emailREQUIRED- The contact email address.
nameOPTIONAL- The contact name.
campaignIdREQUIRED- A GetResponse resource identifier.
dayOfCycleOPTIONALscoringOPTIONAL
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Retrieve one GetResponse campaign by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaignControl Create Campaign
Create a GetResponse campaign for organizing contacts. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_campaignVerify with Get Contact
Retrieve one GetResponse contact by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate GetResponse with explicit limits
- Authorize GetResponse with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in GetResponse rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the GetResponse task completed successfully.
CONNECTION MODEL
API key
GetResponse uses API key. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by GetResponse.