GetResponse
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent GetResponse integration that needs a Maton API key and can change email marketing data, but the sensitive access is disclosed and write actions are instructed to require user approval.
Before installing, make sure you trust Maton with managed OAuth access to your GetResponse account. Keep MATON_API_KEY private, use the Maton-Connection header when multiple accounts are connected, and manually approve any action that creates, updates, deletes, or sends marketing content.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could help change campaigns, contacts, or newsletters in a connected GetResponse account if the user approves those actions.
The skill exposes API operations that can modify marketing assets and contact data, but it clearly instructs confirmation before writes.
Manage email marketing campaigns, contacts, newsletters, autoresponders, and segments... **All write operations require explicit user approval.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
Review the exact target account, resource, and effect before approving any create, update, delete, or send operation.
Anyone or any agent with access to the MATON_API_KEY may be able to make authorized GetResponse requests through Maton.
The skill requires a Maton API key and uses managed OAuth to act on the user's connected GetResponse account.
All requests require the Maton API key in the Authorization header... Authorization: Bearer $MATON_API_KEY ... Maton proxies requests to `api.getresponse.com` and automatically injects your OAuth token.
Store MATON_API_KEY securely, revoke it if exposed, and connect only the GetResponse accounts you intend the agent to manage.
Customer/contact information may transit through Maton's service as part of normal GetResponse API use.
Requests, including contact details and custom fields, are sent through Maton's API gateway to GetResponse; this is disclosed and aligned with the integration purpose.
Base URL: https://api.maton.ai/getresponse/{native-api-path} ... POST /getresponse/v3/contacts ... "email": "john@example.com", "name": "John Doe", ... "customFieldValues"Use the skill only if you trust Maton and GetResponse with the relevant marketing/contact data, and avoid sending unnecessary personal data.