TouchBasePro

Add form sign-ups to a TouchBasePro list and fill its custom fields from their answers.

TouchBasePro is an add-on for Forms. Each form gets a TouchBasePro panel where you add actions, and each action adds the person who submitted to one of your lists. The form works as before, and if TouchBasePro turns someone away, the submission is still saved.

Connect TouchBasePro

Get an API key from your TouchBasePro account. It must be able to read lists and add subscribers. If you can't find one, ask TouchBasePro support for a key for their email API.

In WordPress, open XPAC → Integrations → TouchBasePro, paste the key into API key and save.

Click Test connection. It reads your lists with the saved key and reports how many it found. It sends nothing.

The key stays visible to admins on this screen. XPAC uses TouchBasePro's original email API. A key made for the newer API on touchbasepro.io may be refused, and Test connection tells you so. A refused key is explained, with TouchBasePro's own reason when it gives one.

Add it to a form

Edit the form, open the TouchBasePro panel in the sidebar and click Add TouchBasePro action. The dialog is titled Add subscriber.

  • List: the list to add people to. Choosing another list resets the rows mapped to custom fields.
  • Re-add people who left the list: off by default. Includes unsubscribed, bounced and suppressed people. Turn it on only if the form asks for fresh consent.
  • Restart automated emails: shown when the option above is on. Applies to people it re-adds.
  • Consent to track opens and clicks: No (the default), Yes, or Use a form field. It's sent on every sign-up.
  • Consent field: with Use a form field. A blank, "no", "false", "off" or "0" answer counts as No. Any other answer counts as Yes.
  • Field mapping: pair each Form field with a TouchBasePro field: Email, Name, or one of the list's custom fields.

Save the action, then save the form. Save stays off until you pick a list and a row maps to Email, and while a row points at a field that is no longer on the list. Make the email field required.

Map each form field once: if it's in two rows, only the last one is sent. To send a full name, map a first name and a last name field to Name; they're joined with a space. Several ticked answers go to a multi-select custom field as separate values, and anywhere else as one value separated by commas. File uploads are never sent. Lists and fields are read when you open the form, so reload the editor to see ones you just made in TouchBasePro.

Each row in the panel shows the action and its list. Use the switch to turn an action off without deleting it. With Forms' conditional logic, an action can run only when the answers match. The add-on sends no confirmation email of its own, so ask for consent on the form. The XPAC Agent can also connect a form to a list for you.

When a send fails

Sends run in the background a moment after the submission is saved, so the visitor never waits. Each one shows on XPAC → Forms → Deliveries:

StatusWhat it means
WaitingQueued, or waiting for its next automatic try.
DeliveredTouchBasePro accepted it. The Notes column lists anything left out.
SkippedThere was nothing to send. The Error column says why.
FailedIt didn't go through. The Error column has the reason.
DismissedYou dismissed it, or the submission is in spam or the trash.

What TouchBasePro outcomes look like:

  • An empty email answer is Skipped. If another action in the same submission went through, the delivery is Delivered with a note instead.
  • When TouchBasePro refuses the person (an invalid address, or someone who unsubscribed, bounced, was suppressed or never confirmed, with Re-add people who left the list off), the delivery is Failed and isn't retried.
  • A refused API key or a missing key is Failed with a message saying where to fix it.

A timeout, a rate limit or a server error is retried on its own after about 1, 5, 30 and 120 minutes, up to five tries. Other failures stay Failed until you act. Fix the cause, then click Retry now on the delivery, or Retry all failed. A retry sends with the form's current settings and the API key saved now. Actions that already went through aren't sent again unless you've changed them since. If the site timed out after TouchBasePro had already added someone, the retry sends that person again.

If 5 deliveries in a row fail on one form, XPAC pauses TouchBasePro on that form and emails the site admin. A refused person, an empty email answer and a rate limit don't count toward this. While it's paused, submissions are still saved but show as Failed, and XPAC tries one submission an hour. If that one goes through, sending starts again on its own. To start sooner, fix the cause and click Resume and retry on the Deliveries screen.

For developers

The add-on has one filter of its own: xpac_touch_base_pro_request_timeout sets how many seconds to wait for TouchBasePro. The default is 10.

On this page