Overview

Aimdoc uses Chili Piper in two places:

1. Integrations tab: store your Chili Piper router details (Domain Name and Inbound Router Name).
2. Actions tab: map Aimdoc form fields to Chili Piper field IDs (field keys).

When a qualified visitor reaches a calendar action, Aimdoc builds a Chili Piper payload and requests a routed booking URL from your router.

Before you start

• A Chili Piper Concierge router is created and configured.
• Router field mapping in Chili Piper is configured for the data you want to pass.
• In Aimdoc, your agent form includes the fields you plan to map.

Step 1: Get router details from Chili Piper

In Chili Piper, open your router and go to Embed / Javascript for your Inbound Concierge.

Copy:

• cpTenantDomain -> use this as Domain Name in Aimdoc
• cpRouterName -> use this as Inbound Router Name in Aimdoc

Use only the raw values (for example fire and your router slug), not a full URL.

Step 2: Add router details in Aimdoc

In Aimdoc:

1. Go to Integrations.
2. Open Chili Piper.
3. Enter:
   • Domain Name = cpTenantDomain
   • Inbound Router Name = cpRouterName
4. Save.

Step 3: Map field IDs in Actions

In Aimdoc:

1. Go to your agent's Actions tab.
2. Select Chili Piper under Scheduling.
3. For each Aimdoc field, enter the corresponding Chili Piper field ID (field key).
4. Save the action.

Which Chili Piper value should I paste as the "field ID"?

Use the exact field keys expected in Chili Piper's REST form payload.

• If your router trigger is InAppButton, use Chili Piper Data Field Names.
• If your router trigger is ThirdPartyForm/Webform submitted, use the configured Form Field Names.

These must match Chili Piper exactly (case-sensitive).

Email behavior

Aimdoc automatically sends visitor email as PersonEmail when requesting the routed calendar URL. You can still map additional fields (for example FirstName, LastName, Company, and custom keys) as needed by your router setup.

Workflow requirement in Aimdoc

If you map a field in Chili Piper Actions, that field must be collected in your workflow track path (current track or parent tracks).
If it is not collected, Aimdoc blocks publishing until the missing fields are added.

Verify your setup

1. Start a test conversation.
2. Reach a workflow path that triggers a calendar action.
3. Confirm the Chili Piper calendar loads in chat.
4. Complete a booking and verify it routes correctly in Chili Piper.

Troubleshooting

• Calendar does not load: Double-check Domain Name and Inbound Router Name.
• Wrong routing result: Check field mappings and router rules in Chili Piper.
• Missing data in Chili Piper: Ensure each mapped field is actually collected by Aimdoc before scheduling.
• Validation errors in Aimdoc tracks: Add missing mapped fields to the track's collected fields or parent track fields.

Chili Piper documentation

• Configuring Concierge REST API
• Setting up Concierge with HubSpot Pop-Up Forms
• Configuring Your Concierge Inbound Router

Need help?

If you run into issues, contact support@aimdoc.ai and include:

• Your router slug
• A screenshot of your Aimdoc Chili Piper field mappings
• A sample test lead payload (without sensitive data)