Connect Keap

Connecting Keap lets you save website answers to contact records, so your follow-up can reflect what people tell you. You can also use their existing tags and custom fields to choose what they see on your website.

Connect Keap

You'll need permission to manage your RightMessage project's integration and authorize the intended Keap account. Each project connects to one email platform or CRM. Before replacing one, check which questions, forms, or conditions use it.

1. In RightMessage, open your project settings and choose Integration.
2. Under Email platforms & CRMs, select Keap (Infusionsoft).
3. In Overview, click Connect to Keap (Infusionsoft).
4. Sign in to Keap if prompted and approve access to the intended account.
5. Return to RightMessage and check the connected state and connection health.

Enlarge

Keap connection controls in RightMessage, with no credentials enteredOriginalOriginal

Keap connects through OAuth, so you don't enter an API key, refresh token, or token-expiry value. If access is revoked or you're asked to authorize it again, choose Reconnect to Keap (Infusionsoft).

Choose what to sync

You can save choice answers and segment groups to custom fields or a tag for each answer. Typed answers can go to custom fields or the native First name and Last name fields.

1. Open Questions, choose your question, and open Sync with Keap (Infusionsoft).
2. For a choice question, choose custom fields or tags under Sync mode.
3. For a field, choose Destination and fill in Answer → value. For tags, select the existing Keap tag for each answer. Typed questions map directly to a field.
4. If your flow creates contacts, open the Email question's Setup and keep Identify the visitor enabled.
5. Set Contact action to Create/Update contact, or choose Add to tag and select at least one tag.
6. Review the flow and mappings, then click Publish.

Single-answer questions default to field sync. Multiple-answer questions prefer tags when available. Keep answer tags separate from unrelated workflow tags. See the shared answer-mapping guide for multiple-answer values, tag removal, and switching modes.

For an Other answer, choose a separate field in Save write-ins to Keap (Infusionsoft).

Pick compatible fields

Create custom fields in Keap first. You can't create them from RightMessage. Choose an existing field and use values that fit its type. For dropdown or multi-select fields, check the allowed options as well as their visible labels. A free-text answer may not be a valid option.

A Name question can use One field per part to save first and last names separately. Those are the only native answer destinations. Email is read for identification. Phone, address, and other collected details need compatible custom fields.

Create contacts without a Keap form

Create/Update contact and Add to tag write directly to the contact. You don't need a matching Keap form for each RightMessage offer, and this connection doesn't submit Keap hosted forms or add contacts to lists.

Collect the appropriate consent before using a contact action. If a displayed Email question consent checkbox is left unchecked, RightMessage keeps the response without identifying the visitor or sending their data to Keap.

You can have Keap automations respond to the tags or fields you save. RightMessage doesn't offer direct automation enrollment, outgoing event actions, incoming event history, or purchase history through this connection.

Keap's internal provider identifier is still infusionsoft. Keep that name in existing configurations, custom code, and saved templates rather than renaming it to keap.

Recognize subscribers from email links

Choose a test contact you control and install the RightMessage snippet on the page you'll test.

RightMessage reads rm_isoft as a Keap contact ID. In Keap's email editor, add the contact-ID merge field to a link to one of your own pages. Here's an example for WorkForge (opens in a new tab):

https://workforge.rightmessage.com/pricing.html?rm_isoft=~Contact.Id~

Keap's contact-ID merge-field example (opens in a new tab) uses ~Contact.Id~. Keap replaces it with the recipient's ID when it sends the email. If your URL already has a query string, use &rm_isoft=~Contact.Id~ instead.

The value must be the numeric contact ID, not Keap's separate inf_contact_key tracking value. An unresolved merge field won't identify anyone.

If you use an external Keap form, its redirect can use rm_isoft only when the form replaces the merge field with the new contact's ID. Check the final redirect URL, and put the RightMessage snippet on that destination page. Keap forms don't all support the same merge behavior.

A configured RightMessage form or identifying Email question can also identify contacts. The generic ?email= parameter can look up an existing contact by URL-encoded email. Opening an identifying link doesn't create or subscribe a contact by itself.

Check the connection

1. Give your test contact a distinctive Keap tag or custom-field value.
2. Send them a Keap email with the identifying link and open it in a fresh browser session.
3. Check the on-site debugger for the intended contact and their Keap data, including tags, custom fields, email, and native name data.
4. Navigate to another page without the parameter to check that the browser remembers the contact. A new browser or device needs to identify them again.
5. Submit a mapped answer on the live website, then open that contact in Keap and check the exact field value or tag.
6. Submit a signup with a new email address you control. Check that your selected contact action creates the intended record.

Matching mapped Keap values can place identified visitors in RightMessage segments. Passive sync keeps an existing nonempty Keap field instead of replacing it with old browser data. A new answer submission can update it. This doesn't import your whole contact database or backfill every historical answer.

If recognition fails, check the delivered contact ID and connected account. If field or tag choices are stale, click Clear Cache in Overview and reopen the picker. For a failed tag update, check the selected tag and the update itself, even if connection health is healthy. Reconnect if the account's authorization is no longer valid.

When you can recognize the intended contact and see their answer on the Keap record, the connection is working. Follow Verify an integration change when you change credentials or destinations.