Overview
Connect GetResponse with Flows360
Email marketing and automation platform for contacts, campaigns, and newsletters.
Use the GetResponse connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.
Available actions
- Create Contact
- Create or Update Contact
- Find Contact
- Create Newsletter
- Find Campaign List
- Custom API Call
Available triggers
- No triggers are declared in this pinned package.
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: GetResponse
- Package:
@activepieces/piece-getresponse@0.1.0 - Exact artifact digest:
sha256:3858e77a00f37146bc2e52d3b1433fcc165ad660454bfb17496524ed4c321351 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2, CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Create Contact (
create-contact), Creates a new contact in a GetResponse campaign. Classification: read. - Create or Update Contact (
create-or-update-contact), Creates a contact or updates the existing contact with the same email in the selected campaign. Classification: read. - Find Contact (
find-contact), Finds a contact by email address. Classification: read. - Create Newsletter (
create-newsletter), Creates a newsletter and queues it to send to the selected campaign. Classification: read. - Find Campaign List (
find-campaign-list), Finds campaign lists by name. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: OAuth 2.0, custom
Authentication profiles
connection · oauth2
connection_2 · custom
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Contact | Yes | No | Creates a new contact in a GetResponse campaign. |
| Create or Update Contact | Yes | No | Creates a contact or updates the existing contact with the same email in the selected campaign. |
| Find Contact | Yes | No | Finds a contact by email address. |
| Create Newsletter | Yes | No | Creates a newsletter and queues it to send to the selected campaign. |
| Find Campaign List | Yes | No | Finds campaign lists by name. |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Create Contact · Read
Creates a new contact in a GetResponse campaign.
create_contact · Risk: low · Retry: safe
Inputs
campaignId· string · Required, Select the campaign list to use.email· string · Required, The email address of the contact to create.name· string · Optional, The contact name as it should appear in GetResponse.
Create or Update Contact · Read
Creates a contact or updates the existing contact with the same email in the selected campaign.
create_or_update_contact · Risk: low · Retry: safe
Inputs
campaignId· string · Required, Select the campaign list to use.email· string · Required, The email address used to find or create the contact.name· string · Optional, The contact name as it should appear in GetResponse.
Find Contact · Read
Finds a contact by email address.
find_contact · Risk: low · Retry: safe
Inputs
email· string · Required, The email address of the contact to find.campaignId· string · Optional, Select the campaign list to use.
Create Newsletter · Read
Creates a newsletter and queues it to send to the selected campaign.
create_newsletter · Risk: low · Retry: safe
Inputs
campaignId· string · Required, Select the campaign list to use.fromFieldId· string · Required, Select the verified sender address to use.replyToFieldId· string · Optional, Select the verified sender address to use.subject· string · Required, The subject line for the newsletter.name· string · Optional, An internal name for the newsletter inside GetResponse. Leave empty to use the subject.htmlContent· string · Optional, The newsletter content in HTML format.plainContent· string · Optional, The plain text version of the newsletter content.
Find Campaign List · Read
Finds campaign lists by name.
find_campaign_list · Risk: low · Retry: safe
Inputs
name· string · Optional, Enter part or all of the campaign list name. Leave empty to return the first lists in the account.limit· number · Optional, The maximum number of campaign lists to return.
Custom API Call · Read
Make a custom API call to a specific endpoint
custom_api_call · Risk: low · Retry: safe
Inputs
url· object · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_is_binary· boolean · Optional, Enable for files like PDFs, images, etc.failsafe· boolean · Optional, On a failed request, output the error instead of failing the step.timeout· number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).followRedirects· boolean · Optional, Follow 3xx redirects instead of returning them as the response.
Setup
Setup
- Add the GetResponse connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- API Key (
apiKey), required; stored as a sensitive connection value.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-getresponse@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 6 actions and 0 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Runtime execution evidence is managed separately from package metadata.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required GetResponse connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-getresponse@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.