ActionGetResponseUpdated May 2026

What GetResponse campaigns (lists) exist?

Short answer: Drop the "GetResponse → List GetResponse Campaigns" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 GetResponse actions

Sample request

{}

Returns

[
  {
    "name": "Newsletter",
    "createdOn": "2026-01-01T00:00:00Z",
    "isDefault": "true",
    "campaignId": "camp123",
    "description": "Weekly newsletter"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List GetResponse Campaigns.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GetResponse

2 Google Sheets triggers

HubSpot → GetResponse

18 HubSpot triggers

FAQ

Questions about List GetResponse Campaigns.

What does the List GetResponse Campaigns action do in GetResponse?

Returns every campaign (GetResponse's term for list) with name and subscriber count. Useful for resolving campaign IDs at workflow setup.

What inputs does List GetResponse Campaigns require?

List GetResponse Campaigns has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GetResponse returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List GetResponse Campaigns support batch operations?

Yes. Run List GetResponse Campaigns inside a Loop node to process arrays. Tiny Command handles GetResponse's rate limits automatically so you don't have to throttle manually.

More actions