Slack, HubSpot & webhooks

When a viewer fills in the lead form on one of your clickable demos, TurtleScene can pass their answers on straight away: as a Slack message, as a HubSpot form submission, or as JSON sent to your own web address. Use this so sales hears about a lead while the viewer is still interested, rather than when someone next downloads a CSV.

#Before you start

Integrations send lead form answers, so the demo needs a lead form first. See Lead capture & passwords. The demo must also be public, because only public demos accept form submissions.

Integrations are set for each demo. If you want every demo's leads in the same Slack channel, add the same address to each one.

#Open the Integrations tab

1. In the sidebar, click Library and open the clickable demo.
2. In the editor toolbar, click Personalize. The Settings window opens.
3. Click the Integrations tab.

Changes save automatically. Click Done when you've finished.

#Send leads to Slack

1. In Slack, create an incoming webhook for the channel that should receive leads, and copy its address. It starts with https://hooks.slack.com/services/.
2. In the Integrations tab, paste it into Slack incoming webhook.

Each new lead posts a message to that channel. It starts with "New lead from" and the demo's title, followed by one line per form field with the field's label and the viewer's answer.

#Send leads to a HubSpot form

TurtleScene submits each lead to a form in your HubSpot account, so it lands in HubSpot as a normal form submission.

1. In HubSpot, find your portal ID and the ID of the form that should receive leads.
2. In the Integrations tab, under HubSpot Forms, enter the Portal ID and the Form ID. Both are needed; nothing is sent until both are filled in.

TurtleScene matches your lead form fields to HubSpot's fields like this:

#Send leads to your own webhook

1. In the Integrations tab, paste your endpoint's address into Generic webhook, for example https://example.com/webhook.

For every new lead, TurtleScene sends a POST request with a JSON body like this:

{
  "demoId": "…",
  "demoTitle": "Onboarding tour",
  "data": {
    "Work email": "sam@example.com",
    "Company": "Example Ltd"
  }
}

data holds the viewer's answers, keyed by each field's label as it appears in your lead form. If your demo has translated versions, the keys stay in the original language whichever language the viewer chose.

#When deliveries happen

• A delivery is sent once, when the viewer submits the form. Slack, HubSpot and your webhook each get their own copy.
• Nothing else triggers a delivery: views, clicks and finishing the demo aren't sent.
• If Slack, HubSpot or your endpoint is unavailable, that delivery isn't retried. The lead is still saved in TurtleScene, and you can download it any time with Download CSV under Lead submissions in the same tab.
• If your workspace moves below Studio, deliveries stop. Leads are only collected on Studio and up.

#Download leads as a CSV file

Under Lead submissions, click Download CSV to get every answer this demo has collected, newest first, with the date and a column for each form field. Only members of the workspace can download it.

#Related

• Analytics shows views, completion and CTA clicks for every clickable demo.
• Custom domains are set up in the same Integrations tab.