Integrations · Productivity

Connect Chili Piper to Well

Index Chili Piper company record and person record so questions about customer and contact answer themselves in conversation.

Connect Chili PiperSee what Well does

What Well pulls from Chili Piper

Chili Piper feeds company record, person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Chili Piper’s access.

From Chili Piper		In Well	Relation
Company record		Customer	Enriches
Person record		Contact	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Chili Piper → Well

What Well does with your Chili Piper connection

Connect

Connect Chili Piper over OAuth (MCP DCR): Well registers a client through Chili Piper's OAuth Dynamic Client Registration and you approve on Chili Piper's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings company record and person record in from Chili Piper through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Chili Piper entity into customer and contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Chili Piper lands in the workspace as customer and contact you can search, chart, and automate.

Questions Chili Piper unlocks

Ask in plain language. Well answers from your connected Chili Piper connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Chili Piper connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Chili Piper connection…

1 agent skill runs on Chili Piper.

Well lists Chili Piper in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Chili Piper

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Chili Piper in three steps

01
Authorise Chili Piper via MCP
From Well's Connections panel, search for Chili Piper and click Connect. Well discovers Chili Piper's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Chili Piper's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Well's MCP client discovers company record and person record from Chili Piper that Chili Piper's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Chili Piper records. Because Chili Piper ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Chili Piper records happens in the background.

How Chili Piper stays secure with Well

Well connects to Chili Piper's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Chili Piper secret. Tokens are scoped to the company record and person record Chili Piper exposes and refreshed server-side. Reads only, Well cannot modify or delete Chili Piper records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Chili Piper records
Resources the Chili Piper MCP server exposes, scoped by your OAuth approval.
granted
Resolve company record and person record across your stack
Match identifiers in Chili Piper against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Chili Piper records
Not granted; Chili Piper is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Chili Piper passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Chili Piper’s admin panel.

Frequently asked questions about Chili Piper and Well

How do I connect Chili Piper to Well, and how long does it take?

From Well, open Connections, find Chili Piper, and click Connect. Well discovers the OAuth metadata from Chili Piper's MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Chili Piper's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Chili Piper?

Well brings in company record, and person record from Chili Piper and reshapes each entity into your workspace: company record becomes customer; person record becomes contact. Every record arrives with the source identifier preserved, so Chili Piper stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well track Chili Piper status changes that signal customer-facing risk?

Status transitions on Chili Piper items linked to customer or deal entities surface as workspace events. A task slipping past its due date on a top-tier customer's project, a ticket reopening, a milestone marked at risk; each shows up on the relevant customer page so account owners see the signal before the customer raises it.

How does Well preserve the link from a workspace customer back to the original company record in Chili Piper?

Every workspace customer built from Chili Piper carries the source company record identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Chili Piper record; from Chili Piper, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

How often does Chili Piper sync with Well, and what triggers a refresh?

Well combines live Chili Piper events with periodic reconciliation reads of company record and person record. New rows appear within seconds when Chili Piper pushes them; periodic reads catch anything a push missed. The first connect backfills history from Chili Piper in the background.

Can I disconnect Chili Piper and what happens to the data Well already pulled?

Open Connections > Chili Piper in Well and click Disconnect. Well calls Chili Piper's token revocation endpoint and stops calling Chili Piper immediately on its side; provider-side propagation to Chili Piper's admin panel varies by provider. The company record and person record Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Chili Piper?

The Chili Piper records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.

Ready to connect Chili Piper?

Connect once. Every company record, person record from Chili Piper becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect Chili PiperTalk to us