How to Integrate Retool with Infusionsoft (by Keap)

The modern Keap REST API v2 uses OAuth 2.0 for authentication. To obtain credentials, navigate to the Keap Developer Portal at https://keys.developer.keap.com and sign in with your Keap account. Click 'Create a new application' if you have not done so already. Fill in the application name (e.g., 'Retool Integration'), description, and website URL. For the Redirect URI, you must enter the OAuth callback URL that Retool uses — for Retool Cloud this is typically https://oauth.retool.com/oauthcallback. Check your Retool resource configuration for the exact callback URL before entering it here. Select the OAuth scopes your integration requires. For a CRM management dashboard, the key scopes are: 'full' (provides access to all Keap REST API endpoints) or more granular scopes like 'contacts.read', 'contacts.write', 'opportunities.read', 'opportunities.write'. After creating the application, the Keap developer portal displays your Client Key (Client ID) and Client Secret. Copy both values — you will need them in the next step. Note that if you are maintaining a legacy Infusionsoft XML-RPC integration, you can find the XML-RPC API key in your Keap account under Admin → Settings → Application Settings. Look for the 'API Key' section. This is a static key used as a parameter in XML-RPC calls.

In Retool, click the Resources tab in the left sidebar and click Add Resource. Select REST API from the resource type list. Name the resource 'Keap CRM API'. In the Base URL field, enter: https://api.infusionsoft.com/crm/rest/v2 — note that despite the Infusionsoft domain, this is the current Keap REST API v2 endpoint. Scroll to the Authentication section and select OAuth 2.0 from the dropdown. In the Authorization URL field, enter: https://accounts.infusionsoft.com/app/oauth/authorize. In the Access Token URL field, enter: https://api.infusionsoft.com/token. Enter your Client Key as the Client ID and your Client Secret in the corresponding fields. In the Scopes field, enter 'full' (or your specific scope list, space-separated). Set OAuth flow to Authorization Code. Click the Connect button to initiate the OAuth authorization flow — a browser window opens for you to sign in to your Keap account and grant access. After authorization, Retool stores the access and refresh tokens. Click Save Changes. For teams using the legacy Infusionsoft XML-RPC API, create a separate resource with Base URL https://api.infusionsoft.com/crm/xmlrpc/v1 and no authentication configured in Retool (the API key is passed as a parameter inside the XML body of each request instead).

Create the foundational queries for the CRM dashboard. In a Retool app, open the Code panel and click + to add a new query. Select your Keap CRM API resource. Name the first query 'getContacts'. Set Method to GET and Path to /contacts. Add URL parameters to control the query: 'limit' set to {{ pagination.pageSize || 50 }}, 'offset' set to {{ pagination.offset || 0 }}, 'given_name' bound to a search text input component, and 'order' set to 'id' with 'order_direction' set to 'descending'. Add a URL parameter 'optional_properties' set to 'custom_fields,opt_in_reason' to retrieve additional contact properties. This endpoint returns a paginated list of contacts with their core fields. Create a second query named 'getTags' with Method GET and Path /tags. This returns all available tags in your Keap account — use this to populate a filter dropdown in the UI. Create a third query named 'getOpportunities' with Method GET and Path /opportunities. Add parameters for 'limit', 'offset', and 'stage_name' filter. Add JavaScript transformers to both the getContacts and getOpportunities queries to normalize the nested response data into flat arrays for display in Retool Tables.

1// Transformer: normalize Keap contacts for Table display
2const contacts = data.contacts || [];
3return contacts.map(contact => ({
4  id: contact.id,
5  name: [contact.given_name, contact.family_name].filter(Boolean).join(' ') || '(No name)',
6  email: (contact.email_addresses || []).find(e => e.field === 'EMAIL1')?.email || '',
7  phone: (contact.phone_numbers || []).find(p => p.field === 'PHONE1')?.number || '',
8  company: contact.company?.company_name || '',
9  tags: (contact.tag_ids || []).join(', '),
10  owner: contact.owner_name || 'Unassigned',
11  date_created: contact.date_created
12    ? new Date(contact.date_created).toLocaleDateString()
13    : ''
14}));

Assemble the dashboard interface. Drag a Text Input component to the top of the canvas for contact name search — name it 'nameSearch'. Drag a Select component for tag filtering — populate it with {{ getTags.data.tags }} using name as the label and id as the value. Drag a Table component below the search controls. Set its Data to {{ getContacts.data }}. Configure visible columns: name, email, phone, company, tags, owner, date_created. Add a row selection event handler: when a row is selected in the contacts table, trigger the getContactDetail query (Method GET, Path /contacts/{{ contactsTable.selectedRow.id }}, with optional_properties parameter for full fields). Display the contact detail in a right-side Container with panels for basic info, tags, associated opportunities, and recent email history. Add a Tags section to the detail panel: create a query named 'applyTag' with Method POST, Path /contacts/{{ contactsTable.selectedRow.id }}/tags, Body Type JSON, Body { tagIds: [{{ parseInt(tagSelect.value) }}] }. Add a 'Remove Tag' query with Method DELETE, Path /contacts/{{ contactsTable.selectedRow.id }}/tags/{{ selectedTag.value }}. Create an update opportunity stage query using PATCH method to /opportunities/{{ opportunitiesTable.selectedRow.id }} with a body containing the updated stage_name. Configure all write queries with On Success handlers that trigger a refresh of the relevant list query.

1// Query: Apply a tag to the selected contact
2// Method: POST
3// Path: /contacts/{{ contactsTable.selectedRow.id }}/tags
4// Body Type: JSON
5{
6  "tagIds": [{{ parseInt(tagSelect.value) }}]
7}

For teams maintaining integrations built against the legacy Infusionsoft XML-RPC API, Retool can call XML-RPC endpoints via POST requests with XML bodies. The legacy API is at https://api.infusionsoft.com/crm/xmlrpc/v1. XML-RPC requests are POST requests with Content-Type text/xml, and the body is an XML payload specifying the method name and parameters including your static API key. Create a REST API Resource in Retool with this base URL and no Retool-level authentication (authentication happens via the API key in the XML body). For each query, set Method to POST, Path to empty or /, Body Type to 'raw', and Content-Type header to text/xml. The XML body follows the XML-RPC protocol: include the methodName (e.g., 'ContactService.findByEmail'), a params element with a struct containing the key (your API key) and query parameters. The response is also XML — use a JavaScript transformer to parse the XML string using the DOMParser API: const parser = new DOMParser(); const xml = parser.parseFromString(data, 'text/xml'). Extract values from the XML DOM. Key XML-RPC methods available include ContactService.findByEmail, ContactService.load, InvoiceService.calculateAmountOwed, and DataService.query for generic table queries. For complex integrations involving both legacy XML-RPC data and modern REST API data during a migration period, RapidDev's team can help architect a unified Retool dashboard that bridges both API versions.

1<!-- Example Infusionsoft XML-RPC request body -->
2<!-- Method: POST to https://api.infusionsoft.com/crm/xmlrpc/v1 -->
3<!-- Content-Type: text/xml -->
4<?xml version='1.0' encoding='UTF-8'?>
5<methodCall>
6  <methodName>ContactService.findByEmail</methodName>
7  <params>
8    <param><value><string>{{ retoolContext.configVars.INFUSIONSOFT_API_KEY }}</string></value></param>
9    <param><value><string>{{ emailSearch.value }}</string></value></param>
10    <param><value><array><data>
11      <value><string>Id</string></value>
12      <value><string>FirstName</string></value>
13      <value><string>LastName</string></value>
14      <value><string>Email</string></value>
15    </data></array></value></param>
16  </params>
17</methodCall>