# DemoPage docs: connect your crm

> Turn on Demo before the first call, and your CRM or a Zap can send each new lead to DemoPage. DemoPage records a walkthrough made for that lead, and your team gets the demo and the lead's card before the first call. Leads from your demo reach your team by email and Slack.

Your portal is at https://app.demopage.io/portal.

## Turn on Demo before the first call

1. In your portal, under Where leads go, find Demo before the first call and press Turn on.
2. Copy your intake key right away. It's shown only once. If you lose it, press New key; the old key stops working.
3. Copy the Send leads to address.

![Demo before the first call, turned on: the Send leads to address, the start of the key, and How to send a lead with an example request.](https://storage.googleapis.com/demopage-media/docs/crm-prepare.3d1cbed193ef.webp)

## What to send

- email: the lead's work email. Required.
- goal: what they want to solve, such as the message from your demo form. Required.
- tools, company, and firstname, if you have them.

```
curl -X POST https://app.demopage.io/api/d/your-link/prepare \
  -H "Authorization: Bearer YOUR_INTAKE_KEY" \
  -H "content-type: application/json" \
  -d '{"email":"ada@example.com","goal":"Our reps log calls by hand.","tools":"HubSpot"}'
```

## From a HubSpot workflow

1. In a contact workflow, add the action Send a webhook, with the method POST.
2. Paste your Send leads to address as the webhook URL.
3. For authentication, add your key as an API key named x-demopage-key, sent in the request header.
4. HubSpot's contact fields are read as they are, so there's nothing to map.

## From Zapier

1. Add the action Webhooks by Zapier, and choose POST.
2. Paste your Send leads to address as the URL, and send the data as JSON.
3. Map the lead's email and goal, and any of tools, company, and firstname.
4. Add a header named Authorization with the value Bearer, a space, and your key.

## What happens next

- DemoPage records a walkthrough of your product made for that lead. Website visitors come first: it waits for a spare demo browser and uses at most half of the day's live demos.
- Your team gets the demo and the lead's card by email and Slack.
- With Email the lead their demo ticked, the lead gets it when every page loads as expected. Otherwise your team gets it to watch and send.
- When the lead opens their demo, your team gets an alert.
- Up to 25 demos a day. The same email within a week gets the same demo.

## Getting demo leads into your CRM

Leads from your demo go to your alert emails and Slack channel. DemoPage can also post each lead and finished demo to a webhook, for Zapier, Make, or your own endpoint. For now the DemoPage team turns that on for you, so talk to us.

## More guides

- [Set up DemoPage](https://demopage.io/docs.md): From sign-up to a live demo on your site: pages, embed, leads, and signed-in screens.
- [Add the demo button to your site](https://demopage.io/docs/add-to-your-site.md): Paste one script tag on any site builder, or use your own button.
- [Choose pages, and who gets a live demo](https://demopage.io/docs/pages-and-access.md): Keep the pages the demo may show, and decide whose live demo waits for you.
- [Show your product, signed in](https://demopage.io/docs/demo-login.md): Give the guide a sandbox login so it can learn the product, then pick the pages a customer may see.
- [Get lead alerts in Slack](https://demopage.io/docs/slack-alerts.md): Post who watched your demo, what they asked, and a recap link into a Slack channel.
- [Read your demo results](https://demopage.io/docs/results.md): What each number means, the questions buyers asked, and your latest leads.
- [Build your demo from your code](https://demopage.io/docs/ai-tools.md): Connect Cursor, Claude Code, Codex, or ChatGPT to map your screens from code.