GetResponse
GetResponse contact and engagement events
GetResponse is the all-in-one email + landing-page + webinar platform, and Tiny Command surfaces four behaviour triggers (Contact Subscribed, Contact Unsubscribed, Email Opened, Link Clicked) plus two actions (Create Contact and List Campaigns — GetResponse calls lists "campaigns", which trips up newcomers). Contact Subscribed fires after double-opt-in confirms when the campaign requires it. Link Clicked is the high-resolution engagement signal — it carries which message, which link URL, and the contact, which is the right hook for behavioural lead scoring or cart-abandonment-style follow-ups. The connection uses the GetResponse API key from the user's account settings; tokens are account-wide (not OAuth), so connecting a workspace means the workflow can read every campaign on the account. Create Contact accepts campaigns as an array of campaign IDs (use List Campaigns to populate the picker), plus custom fields keyed by their tag, plus an ipAddress field that GetResponse uses for GDPR consent logging when you have it.
Workflows start when GetResponse does.
4 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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".
Fires when a contact unsubscribes from a campaign. Useful for "they opted out → suppress in CRM, log to churn dashboard" workflows.
Fires once per contact per message on first open. For engagement-based scoring or for "warm lead detection → fire follow-up" cross-app patterns.
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.
Do anything GetResponse can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create GetResponse Contact | Adds a contact to a GetResponse campaign with email, name, custom fields. The base hook for "form submission → push to GR campaign" sync workflows. |
| List GetResponse Campaigns | Returns every campaign (GetResponse's term for list) with name and subscriber count. Useful for resolving campaign IDs at workflow setup. |
Pre-built GetResponse workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect GetResponse once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every GetResponse field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the GetResponse integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect GetResponse to Tiny Command?
What GetResponse triggers does Tiny Command support?
What GetResponse actions can I run from a workflow?
Is the GetResponse integration real-time?
Do I need to write code to use GetResponse with Tiny Command?
How much does the GetResponse integration cost?
More email apps people connect.
Same category as GetResponse, ordered by how often teams pair them. Hover the carousel to pause.
Do more with GetResponse.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
