Warmly Integration Documentation: LeanData

Last updated: April 14, 2026

Note: This is only available to customers on paid Warmly plans with an active LeanData BookIt subscription.

Warmly’s LeanData BookIt integration brings your LeanData routing directly into your inbound experience.

When a prospect visits your site and submits their information, Warmly:

  • Sends their data to LeanData in real time

  • Routes them to the right sales rep based on your existing rules

  • Instantly displays the correct booking calendar

No manual handoffs. No delays. Just a seamless path from interest to booked meeting.

Before you start

Before configuring the integration in Warmly, make sure you have:

  • An active LeanData BookIt subscription with routing graphs already set up

  • Your LeanData API Key (from LeanData support or admin portal)

  • Your BookIt Organization ID
    (LeanData → BookIt → Settings → General)

  • Your Trigger Node Name
    (your routing graph entry point, e.g., Lead_Routing)

  • The form fields used in your routing logic
    (e.g., email, firstName, companyName)

Important: Sales rep email addresses must match in both LeanData and Warmly. This is how Warmly maps routing results to the correct calendar.


Step-by-Step Instructions

Follow these steps to use the feature:

Step 1: Connect LeanData in Warmly

  1. Go to Settings → LeanData in Warmly

  2. Enter your API Key (securely stored)

  3. Enter your BookIt Organization ID

  4. Enter your Trigger Node Name

  5. Configure your Field Mappings

    Field mappings define what data gets sent to LeanData. Each mapping includes:

    1. Form Field API Name
      (must match LeanData exactly — no spaces)

    2. Variable
      (the Warmly session data source)

    Note: Note: Form Field API Names must not contain spaces. Variables reference session data ( prospect.* , company.* , etc.)

    Form Field

    API Name

    Variable Description

    email

    prospect.email

    Visitor email

    firstName

    prospect.firstName

    First name

    lastName

    prospect.lastName

    Last name

    companyName

    company.name

    Company name

  6. (Optional) If using Salesforce, set the BookIt Log ID Field

  7. Click Integrate

Step 2: Review Your Auto-Generated Workflow

After connecting, Warmly automatically creates a “LeanData BookIt” workflow and opens it in the builder.

Default structure:

Collect Email → Collect Name → Assign via LeanData → Branch:
├─ Rep Assigned → Show message + “Book a Meeting” → Calendar
└─ No Rep Assigned → Fallback message → End

The logic is fully set up — you just need to:

  • Review messaging

  • Adjust tone/branding

  • Make any small tweaks

Step 3: Test the Integration

Before going live, run a full test:

Validate the flow

  • Questions capture the correct data

  • LeanData returns a routing result

  • Assigned rep exists in Warmly

  • Calendar loads with real availability

Validate booking

  • Booking completes successfully

  • Calendar closes after scheduling

  • Confirmation is received

  • (If using Salesforce) booking ID is written to the Lead

If you hit an authentication error, re-check your API key in Settings → LeanData.

Step 4: Customize the Experience

Once everything is working, you can tailor the workflow:

  • Add/remove questions

  • Map additional fields to LeanData

  • Customize branch messaging

  • Handle edge cases (e.g., no routing match)

  • Layer in other Warmly features:

    • AI chat

    • Slack notifications

    • CRM updates


Troubleshooting

  1. API key invalid

    Cause: Incorrect or expired key

    Fix: Re-enter a valid API key

  1. Rep assigned in LeanData, but not in Warmly

    Cause: Email mismatch

    Fix: Ensure rep emails match exactly in both systems

  2. Calendar not opening

    Cause: No routing match (responseType: "none")

    Fix: Verify Trigger Node Name and field mappings

  3. Field mapping errors

    Cause: Invalid field names or missing variables

    Fix:

    1. Remove spaces from API names

    2. Confirm variables exist (e.g., prospect.email)

  4. “Affected workflows” warning

    Cause: Field mapping changes impact existing workflows

    Fix: Review and update affected workflows manually

Have questions or feedback? Reach out to your CSM or email us at [email protected]