1. Integrations
  2. GetResponse

GetResponse integration: visitors from the chat are added to your GetResponse list as contacts

Agenola's GetResponse integration connects your agent to your GetResponse account: the agent adds a visitor who asks for your newsletter to your list, tags them based on the conversation and sends events that start your GetResponse automations. Connect in one click with your GetResponse account.

How it works

GetResponse steps are added to the flow or turned on in the Integrations tab of the AI Assistant step. In every step the contact is found by email address; the email the visitor gives is enough.

Each step chooses the list it writes the contact to: one agent can write to your newsletter list, another to your customer list. If your account has one list, you don't need to choose.

  • If your list asks for confirmation, GetResponse sends a new contact a confirmation email; they join the list once they confirm. Automatic emails on the list, such as a welcome email, reach a new contact from the first day.
  • In an agent open to visitors, use “Get subscription status”: it only tells whether the email is subscribed, not the contact's name or phone.
  • “Send event” triggers an event you defined in GetResponse; you can build an automation that starts with it.
  • The steps that send a draft newsletter, delete a newsletter or remove a contact from a list don't run until the confirmation box in the step is ticked.
  • Steps work with the connecting person's access in GetResponse.

What it does

This list is generated from the same source as the GetResponse page in the dashboard: if it isn't listed here, we don't do it with GetResponse. Flow steps live in the flow editor under Add step → Integrations → GetResponse.

ContactAction · Flow step7
  • Add or update contact

    Adds the contact if they aren't in the list, otherwise updates their name, phone, note and tags. If your list asks for confirmation, GetResponse sends a new contact a confirmation email; they join the list once they confirm. If your list has automatic emails such as a welcome email, a new contact gets them from the first day.

  • Add contact

    Adds the contact to the list. If your list asks for confirmation, GetResponse sends a confirmation email. If the contact is already in the list, the step fails.

  • Update contact

    Changes the name, phone or note of the contact in the list.

  • Get subscription status

    Reads whether the email is subscribed in the list; doesn't return the contact's name or any other detail. Use this in agents open to visitors.

  • Get contact

    Reads the contact's name, phone, note and tags. For agents your team uses; a visitor could type someone else's email.

  • Get contacts

    Returns the 100 contacts most recently added to the list. For agents your team uses.

  • Remove contact from list

    Removes the contact from the list; they no longer get the list's emails. The contact can be added again later.

Contact tagAction · Flow step2
  • Add tags

    Adds tags to the contact. A tag that doesn't exist in GetResponse is created.

  • Remove tags

    Removes the tags from the contact; their other tags stay.

Contact eventAction · Flow step1
  • Send event

    Triggers an event you defined in GetResponse for the contact; you can start an automation from it. The contact must be in the list.

ListAction · Flow step1
  • Get lists

    Returns the lists in your account.

NewsletterAction · Flow step4
  • Get newsletter

    Reads the newsletter's name, subject and status.

  • Get newsletters

    Returns the latest 100 newsletters as a list.

  • Send draft

    Sends the chosen draft newsletter to the list now.

  • Delete newsletter

    Permanently deletes the newsletter.

Example conversations

A visitor who asks for the newsletter is added to the list

Visitor: I'd like to hear about your offers. Can I sign up for the newsletter? My email is deniz@example.com.

Agent: Of course. We've sent a confirmation email to deniz@example.com; click the link in it to join our newsletter.

Behind the scenes: “Add or update contact” adds Deniz to the newsletter list; since the list asks for confirmation, GetResponse sends the confirmation email. Once Deniz confirms, the list's welcome email goes out.

Tags and events based on the conversation

Visitor: I'm on your newsletter. Do you have a business package? I'm asking for a team of 30. My email is can@example.com.

Agent: Our team will prepare a business package offer just for you; I've passed on your details.

Behind the scenes: “Add tags” gives Can the “business” tag. “Send event” triggers the “business_request” event you defined in GetResponse; your automation that starts with this event sends Can the offer emails.

The subscription is checked

Visitor: Am I signed up for the newsletter? My email is ece@example.com.

Agent: Yes, ece@example.com is signed up for our newsletter.

Behind the scenes: “Get subscription status” reads whether the email is subscribed in the list; the contact's name and other details don't reach the agent.

Setup

  1. 1In Agenola, on Integrations → GetResponse, press “Connect to GetResponse” and give access with your GetResponse account.
  2. 2In the agent editor, add GetResponse steps, choose the list and write the variable holding the visitor's email in the email field.

Detailed setup: How do I connect GetResponse?

Permissions and where your data goes

  • Sent to GetResponse: the fields you fill in the step (the visitor's email, name, phone and note), tags and event properties.
  • Read from GetResponse: the account's name and email, lists, newsletters, defined events and the contact details a step asks for.
  • GetResponse has no permission list: the connection reaches what the connecting person's access in the account reaches. Steps only do the work you add.
  • Connection details are stored encrypted on the server. Only the workspace owner and admins connect or remove it. When it's removed, your contacts stay in GetResponse. You can also remove Agenola's access from your GetResponse account.

Related integrations

See all integrations

Frequently asked questions

Does a visitor join a GetResponse list without confirming?

It depends on your list's setting. If the list asks for confirmation, GetResponse sends a new contact a confirmation email and they join the list once they confirm. On a list without confirmation the contact is added directly; use such a list only when the visitor has given explicit consent.

Can a visitor see someone else's details through GetResponse steps?

The visitor's identity isn't verified; they can type someone else's email. In an agent open to visitors, use “Get subscription status”, which only tells the subscription. “Get contact” and “Get contacts” return names and phones; turn them on in agents your team uses.

I have several GetResponse lists. Which one is used?

The list you choose in the step. Each step can choose its own list, so one agent writes to your newsletter list and another to your customer list. If your account has one list, you don't need to choose.

Can the agent start my GetResponse automations?

Yes. Define an event in GetResponse and build an automation that starts with it; the “Send event” step triggers the event for a contact in the list. You write the event's properties in the step as “name: value”.

Try the GetResponse connection on your own account

Agenola and our partners use cookies to improve the site and show you relevant ads. We count which of our ads bring visitors without using your name or email; anything more only happens if you allow it. Privacy Policy(opens in a new tab)