Integrations

Connect your CRM, calendar, and Slack, with no write-back.

DemoPage connects to HubSpot, Salesforce, Zapier, Chili Piper, Slack, and MCP clients through plain HTTPS calls, not marketplace apps. A workflow sends a lead, DemoPage records a demo for that lead, and your team is alerted. It never writes back to your CRM or your calendar, and each page says what isn't supported.

Last reviewed 2026-10-26. Written from what the product does today.

What connects, and how

Integrations, what each sends, and the state of the documentation
ToolHow it connectsEventDocumentation
HubSpot (/integrations/hubspot)A HubSpot workflow sends the lead to DemoPagecontact.readyStep-by-step guide published
Salesforce (/integrations/salesforce)A Salesforce flow sends the lead to DemoPagecontact.readySame endpoint as HubSpot; no step-by-step guide yet
Zapier (/integrations/zapier)A Zap sends any of the three events, or reads your demo linkscontact.ready, meeting.booked, demo.requestedStep-by-step guide published
Chili Piper (/integrations/chili-piper)Your booking tool tells DemoPage a meeting was bookedmeeting.bookedEvent supported; no step-by-step guide yet
Slack (/integrations/slack)DemoPage posts lead alerts into one channelalerts outStep-by-step guide published
MCP clients (/integrations/mcp)An AI assistant reads your account, or builds your demo from your codetoolsTwo servers, documented

The two doors in

Everything that reaches DemoPage uses one of two documented endpoints, both over HTTPS with a bearer key.

Endpoints and the key each uses
EndpointKeyUse it for
POST /api/d/{link}/prepareThe link's intake key, dp_in_Send one lead and have a demo recorded for them
POST /api/v1/eventsThe account key, dp_live_Store a contact.ready, meeting.booked, or demo.requested event

The account API is described at https://app.demopage.io/api/v1/openapi.json.

What none of them do

  • DemoPage doesn't update HubSpot or Salesforce records, create or move calendar events, or change a Chili Piper queue.
  • There are no marketplace listings. Connecting a tool means pointing its webhook or flow at DemoPage's address.
  • Demo leads reach your team by email and Slack. To also post each lead and finished demo to a webhook, add its address yourself in your portal, under Demo settings, then Guide and call to action.

When not to use DemoPage for this

  • Two-way CRM sync. DemoPage stores events and doesn't write to the tool that sent them.
  • A one-click install from a marketplace. Setup is a webhook or flow that you configure.

Questions

What teams ask.

Which tools does DemoPage connect to?

HubSpot, Salesforce, Zapier, a calendar, and Chili Piper send events in. Slack and email carry alerts out. MCP clients can read your account or build your demo from your code.

Does DemoPage write to my CRM?

No. Events are stored in DemoPage, and nothing is written back to HubSpot, Salesforce, a calendar, or Chili Piper.

Do I need a developer?

For HubSpot, Zapier, and Slack the guides use each tool's own screens. Salesforce and Chili Piper need someone who can configure an outbound call in that tool.