Documentation Industry-specific Realpad

Industry integration

Realpad

Realpad integration overview
  • CategoryIndustry
  • AuthLogin credentials

Overview

Realpad connects on /integrations in the dashboard. Click the Realpad card and the 'Connect Realpad' modal opens with five fields: Login (the API login Realpad issued for the project, not the Realpad UI login), Password (the API password issued alongside the login), Developer ID, Screen ID, and Project ID. On save MessageMind validates the Login and Password by issuing the cheapest authenticated read (list consent types) against each candidate Realpad host until one answers successfully; the winning host is remembered on the integration. Once validated, new MessageMind contacts are pushed to Realpad as leads on the configured Project ID, custom-field edits and tags on linked contacts are synced out, and your Realpad customers are imported and polled back in (Realpad has no webhooks).

What MessageMind can do with it

  • Push new MessageMind contacts into Realpad as leads on the configured Project ID, with a configurable default referral source.
  • Sync custom-field edits on linked contacts out to Realpad, keyed by the per-integration attribute map, with a snake_case retry when Realpad rejects the raw attribute name.
  • Update core customer fields (name, identity) on an existing Realpad customer when the linked MessageMind contact is edited.
  • Import your Realpad customers into MessageMind as contacts through a background job you can trigger from the integration card.
  • Poll Realpad on a schedule for customer and lead changes, since Realpad does not emit webhooks.
  • Pull project information for the configured Project ID so the AI can reference the right development when talking to a buyer.
  • Export customer contacts and inquiry history through Realpad's Data Takeout endpoints, with retry handling for rate limits.

Requirements

  • A Realpad CRM account with API access and the Login, Password, Developer ID, Screen ID, and Project ID that identify your tenant.
  • An API-only Login and Password issued by Realpad (not your Realpad UI login).
  • Any custom attributes the AI will write to must already exist in your Realpad CRM. There is no API to discover attributes, so each tenant's slugs are configured on the integration.

How to connect

  1. In the MessageMind dashboard, open /integrations and click the Realpad card. The 'Connect Realpad' modal opens.
  2. Fill in the five fields: Login (e.g. 'project-name-api.3'), Password (the Realpad API password), Developer ID (e.g. '44423545', from /get-projects-info), Screen ID (e.g. '350613', the Realpad screen to use), and Project ID (e.g. '44423921', the project new leads should be attached to).
  3. Click to save. MessageMind probes each candidate Realpad host with the Login and Password; the host that answers the authenticated read is remembered on the integration. If none accept the credentials, nothing is stored.
  4. Once validated, the connection is enabled and the AI can read and write to your Realpad CRM. New contacts pushed into MessageMind are sent to Realpad as leads, and edits to linked contacts are synced out live.
  5. To pull your existing Realpad customers into MessageMind, trigger the import from the Realpad card. MessageMind enqueues a background job (POST /realpad/confirm-import) and you can watch its progress via the import-status endpoint.
  6. If a Realpad password is rotated, repaste the new value in the same card; the stored credential is replaced and sync resumes.

Authentication and permissions

Mechanism
Login and Password posted as form-encoded parameters on every call. There is no OAuth, no API key exchange, and no session token; each request re-authenticates with the stored credentials.
Credentials
Login, Password, Developer ID, Screen ID, and Project ID. All five are stored on the integration document; the Password remains inside your MessageMind tenant.

Available data and actions

Reads

  • The customer and lead lists for the connected tenant, polled on a schedule.
  • The tenant's consent types (also used as the cheapest authenticated read at connect time to probe each candidate host).
  • Project information for the configured Project ID.
  • Data Takeout Excel exports of customer contacts and inquiries, with a longer timeout than normal reads.

Writes

  • New leads on your Realpad tenant, attached to the configured Project ID, with the configured default referral source when no better value is available.
  • Customer attribute values on linked customers, keyed by the per-integration attribute map, with a snake_case retry on rejection.
  • Core customer field updates on existing Realpad customers when the linked MessageMind contact is edited.

AI agent use cases

  • A website or WhatsApp lead is written straight into Realpad as a new lead on the right Project ID, tagged with the configured referral source.
  • A sales conversation updates the customer's attributes in Realpad as they share preferences (for example budget range or preferred development).
  • Project information for the current development is pulled into the conversation so the AI can answer buyer questions accurately.
  • Your existing Realpad customer base is imported into MessageMind so the AI greets returning buyers by name and keeps writing back to the right customer record.

Configuration

  • The Realpad API host is auto-probed from a built-in candidate list, or pinned explicitly by setting a single base URL on the deployment. The winning host is remembered on the integration document.
  • A per-integration attribute map maps MessageMind custom-field keys to the Realpad attribute slugs that exist in your tenant.
  • A configurable default referral source is applied to new leads when no better value is available on the contact.
  • Normal calls time out after 30 seconds; Data Takeout exports have a longer 120 second budget.
  • Data Takeout rate limits (HTTP 429 with Retry-After) are honoured, with a bounded number of retries up to a sane cap.
  • Imports run as a background job per user (source 'realpad'). Starting a second import while one is in progress re-enqueues the existing job rather than creating a duplicate.

Example workflows

Push a new chat lead into Realpad

  1. A customer starts a conversation on one of your MessageMind channels.
  2. MessageMind collects the lead details.
  3. A create-lead call is sent to Realpad on the configured Project ID, with the configured default referral source when no better value is available.
  4. The lead appears in your Realpad CRM where the sales team can pick it up.

Import existing Realpad customers

  1. On the Realpad card, trigger the import. The dashboard calls POST /realpad/confirm-import.
  2. MessageMind creates (or reuses) a background import job for the current user, source 'realpad', and enqueues it.
  3. The job walks the customer list and writes each one into MessageMind as a linked contact.
  4. You can poll GET /realpad/import-status/:jobId for progress. A second confirm while a job is in progress re-enqueues the existing job rather than starting a duplicate.

Limitations

  • Realpad emits no webhooks. State changes on the Realpad side are only picked up when MessageMind polls the list endpoints.
  • Realpad attributes are pre-created per tenant and there is no API to list them, so an attribute that does not exist in your Realpad CRM will fail.
  • Credentials are posted on every call rather than exchanged for a session token; a rotated password must be re-entered in MessageMind to resume.
  • Data Takeout endpoints are rate-limited; a large tenant can see short delays while retries unwind.
  • The Login is an API-only account issued by Realpad, not your Realpad UI login.

Troubleshooting

The connect form reports that the credentials could not be validated.

MessageMind probes each candidate Realpad host with the Login and Password; if none accept them, nothing is stored. Verify the Login and Password against your Realpad account, confirm you are using the API-only Login (not your Realpad UI login), and try again.

A customer attribute write is refused with an unknown attribute error.

The attribute does not exist in your Realpad tenant. Create it in Realpad under the matching slug, or map the MessageMind key to the correct slug on the integration. MessageMind already retries once with a snake_case variant before giving up.

A Data Takeout export times out.

Exports have a longer timeout than normal calls (around two minutes). On a very large tenant, retry during a quieter period; MessageMind honours HTTP 429 Retry-After with a bounded number of retries.

The customer import card says an import is already in progress.

MessageMind keeps one import job per user with source 'realpad'. The dashboard call re-enqueues that job rather than creating a duplicate. Poll GET /realpad/import-status/:jobId to see progress.

The toast says 'No enabled Realpad integration found for this user.'

The import can only run against an enabled Realpad integration. Open the Realpad card, reconnect with a valid Login and Password, and try the import again.

Disconnect and reconnect

  • On /integrations in the dashboard, open the Realpad card and click Disconnect. The Login, Password, Developer ID, Screen ID, Project ID, and the resolved API host are removed from your tenant and polling stops.
  • The Realpad CRM itself keeps its leads, customers, attributes, and project data. Disconnecting does not undo any lead or customer update already written.
  • To reconnect, re-enter the five fields in the connect form. The candidate hosts are re-probed on first use and the winning host is remembered again.