TriggerGetResponseReal-timeUpdated May 2026
When does GetResponse fire on unsubscribes?
Short answer: Drop the "GetResponse → GetResponse Unsubscribe" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in GetResponse, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
GetResponse Unsubscribe
When the matching event happens
watch for contact unsubscribednew contact unsubscribedwhen a contact unsubscribeson contact unsubscribedwhen contact unsubscribed
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"name": "John Doe","email": "user@example.com","event": "unsubscribe"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| name | string | "John Doe" |
| string | "user@example.com" | |
| event | string | "unsubscribe" |
Pairs with
Drop these actions after GetResponse Unsubscribe.
FAQ
Questions about GetResponse Unsubscribe.
How does the GetResponse Unsubscribe trigger work in GetResponse?
Fires when a contact unsubscribes from a campaign. Useful for "they opted out → suppress in CRM, log to churn dashboard" workflows.
Is the GetResponse Unsubscribe trigger real-time?
Yes. GetResponse Unsubscribe uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in GetResponse.
What data does GetResponse Unsubscribe return?
The full event payload from GetResponse. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter GetResponse Unsubscribe so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need GetResponse admin permissions to use GetResponse Unsubscribe?
For most GetResponse accounts a standard user can authorize the trigger. Some GetResponse plans require an admin to enable third-party webhooks. Check GetResponse's docs if the trigger fails to register.
More triggers
Other GetResponse triggers.
Trigger
GetResponse Contact Subscribed
Fires when a new contact is added to a GetResponse campaign (after double-opt-in if enabled). The base hook for "new GR subscriber → push to CRM + welcome workflows".
TriggerGetResponse Email Opened
Fires once per contact per message on first open. For engagement-based scoring or for "warm lead detection → fire follow-up" cross-app patterns.
TriggerGetResponse Link Clicked
Fires when a contact clicks a tracked link. Payload includes the resolved URL — high-resolution engagement signal for "clicked the pricing link → fire sales-handoff workflow" automation.
Build a workflow on this trigger.
One trigger. 2+ downstream actions. Zero glue.
