GetResponse

GetResponse sends each form submission to your GetResponse account. An action adds the contact to a list, with mapped fields, tags and an autoresponder day, or deletes the contact from a list. It needs XPAC Forms.

Connect GetResponse

Add it to a form

Edit the form, open the GetResponse panel in the sidebar and click Add GetResponse action.

• Action: Add contact adds the contact to the list. Delete contact deletes them from the list and leaves addresses that are not on it alone.
• List: the GetResponse list. A list deleted in GetResponse is flagged, and the action can't be saved until you choose another.
• Update existing contacts: on by default. Writes the mapped fields and adds the tags to a contact already on the list. Nothing else on the contact changes.
• Autoresponder cycle day: for new contacts. 0 starts the autoresponder today. Leave it empty to skip it. Updates never change a contact's day.
• Tags: 2 to 64 letters, numbers or underscores. Spaces become underscores, and missing tags are created. Tags already on the contact stay.
• Field mapping: pair each Form field with a GetResponse field: Name, Email or one of your custom fields. One row must map to Email. Only the top row for each GetResponse field is sent. Delete contact uses only the email.

Answers GetResponse won't accept are left out, and the delivery gets a note naming them: a phone number without a country code, a date or number it can't read, or a choice that is not one of the field's options. A US-format Phone field gets +1, and a number starting with 00 is sent with +. A Smart international Phone field already sends +CC numbers, and a phone format from an add-on that declares a country code gets that code. File uploads are sent as links. Private uploads are left out with a note, because their links open only for people logged in to your site.

Click Save, then update the form. Each action has a switch to turn it off, and Edit GetResponse action and Remove GetResponse action buttons. With Forms' conditional logic, an action can run only when the answers match. The XPAC Agent can add these actions for you too.

When a send fails

XPAC saves every submission first and sends it to GetResponse in the background, so a GetResponse problem never loses a submission. Each send is listed under XPAC → Forms → Deliveries:

• Delivered: GetResponse took it. A note says when something was left out, such as an answer it won't accept, a tag it refused, or an action skipped for a blank email.
• Waiting: queued, or waiting to try again. When GetResponse is busy or can't be reached, XPAC tries again after about 1, 5, 30 and 120 minutes.
• Failed: every try failed, or GetResponse refused this contact, for example an address that is not valid. The row says why.
• Skipped: there was nothing to send, such as a submission with no email address.
• Dismissed: you dismissed it, or the submission is in spam or the trash.

Retry now sends a failed or dismissed delivery again with the form's current settings and the API key saved now. Actions that already went through are not sent again unless you edited them since, and a retry never adds the same contact twice.

If five deliveries in a row fail because of the account or the connection, such as an expired key or GetResponse being down, XPAC pauses GetResponse on that form. A problem with one person's answers never counts. While it is paused, submissions are still saved but show as Failed, and the site's admin email address gets one email about it. XPAC still tries one submission an hour, and GetResponse starts sending again on its own if that one goes through. To resume now, fix the cause and click Resume and retry on the Deliveries screen. It sends the failed submissions again with the form's current settings.

For developers