> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/connect.md).

# Connect & Integrations

Send every dForms submission where your team works: HubSpot, your own webhook endpoint, analytics pixels and email notices. Learn the two surfaces (account-level Connections and the per-form Connect t

dForms can push each submission out the moment it arrives: to a HubSpot contact, to a webhook on your own server, to your analytics tools through pixels, and to inboxes through email notices. Everything is configured from two places, and nothing an integration does can ever block or lose a submission.

***

## The two surfaces

**1. Connections (account level).** Open **Integrations** in the left rail. This is where you connect your account to **HubSpot** and **Calendly** once with a token, and where you see an inventory of every webhook across your forms. Connecting is done by an admin or owner; after that, every form in the workspace can use the connection.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-2ee97be0bae202d019e9725cec381f74e14275c0%2Fforms-connect-02-connections-page.png?alt=media" alt="The Connections page opened from the Integrations entry in the rail, with HubSpot and Calendly connected"><figcaption><p>Connect once here, then map fields per form.</p></figcaption></figure>

**2. The Connect tab (per form).** Open any form in the editor and click **Connect** in the top bar. The tab has four sections:

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d5847bac02bc6c7a2c084c92ed2cc67b7ee141ed%2Fforms-connect-01-connect-tab.png?alt=media" alt="The Connect tab of a form showing the Integrations section with a Webhook card and a HubSpot card"><figcaption><p>The Connect tab. <strong>Integrations</strong> first, then <strong>Tracking &#x26; pixels</strong>, <strong>Emails</strong> and <strong>Spam protection (captcha)</strong>.</p></figcaption></figure>

| Section                       | What you set there                                                                                                                                                                         |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Integrations**              | The **Webhook** card and the **HubSpot** card, each with an **Enabled** / **Disabled** switch and its own delivery history. **Google Sheets** shows as **Coming soon**.                    |
| **Tracking & pixels**         | **Google Tag Manager ID**, **Meta Pixel ID**, **PostHog project key**, **PostHog host (optional)** and **HubSpot tracking ID** for the form's public page.                                 |
| **Emails**                    | The **New submission notice** (to you, or to the addresses you list) and the **Respondent confirmation** (to the respondent): follow the account template or customize them for this form. |
| **Spam protection (captcha)** | An optional human check before the final submit, in **Automatic** or **Strict** mode.                                                                                                      |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-ce7c19e2ea49d750e3eaffe4b5d2fbe56e6dccca%2Fforms-connect-03-tracking-and-emails.png?alt=media" alt="The Tracking and pixels section followed by the Emails section in the Connect tab"><figcaption><p>Further down the same tab: tracking IDs and the two submission emails.</p></figcaption></figure>

> **💡 Tip:** There is no Save button on the Connect tab. Changes are saved automatically and the footer reads **Changes saved automatically**. Integrations save to the live form immediately, while tracking IDs and the spam protection setting are staged with your draft and go live when you click **Publish**.

***

## Durable delivery, in one paragraph

When someone submits, the answers are stored first. Only then does dForms queue the deliveries: one per enabled webhook and HubSpot destination, and one email per recipient. A slow or broken endpoint never slows the respondent down, and a failed attempt is retried automatically with increasing delays. Every integration card has a **View history** button that shows what was sent and what came back, so you never have to guess. Details are on [Delivery, retries & history](/dforms/connect/delivery-and-retries.md).

With [spam protection](/dforms/connect/spam-protection.md) on, a partial submission is stored but not sent to webhooks or HubSpot. Only the verified complete submission is delivered.

***

## In this section

* [Connections (account level)](/dforms/connect/connections.md): connect HubSpot and Calendly with a token, see who is connected, disconnect, and review the webhooks inventory.
* [HubSpot](/dforms/connect/hubspot.md): sync respondents as contacts, map questions to properties, translate values, stamp UTMs, score and outcome, and link contacts to the page they converted on.
* [Scheduler step & Calendly](/dforms/connect/scheduler-and-calendly.md): let respondents book a meeting inside the form.
* [Webhooks](/dforms/connect/webhooks.md): POST each submission as JSON to a URL you control, signed and retried.
* [Tracking & pixels](/dforms/connect/tracking-and-pixels.md): GTM, Meta Pixel, PostHog and HubSpot tracking on the public page.
* [Submission emails](/dforms/connect/emails.md): the notice you and your team receive, and the confirmation the respondent receives.
* [Spam protection (captcha)](/dforms/connect/spam-protection.md): a human check before the final submit, and what it changes for partial answers.
* [Delivery, retries & history](/dforms/connect/delivery-and-retries.md): what happens after a submission, retry schedule, statuses.

## What's next

* [Submissions](/dforms/results/submissions.md): the answers behind every delivery.
* [Autosave, drafts & publishing](/dforms/builder/autosave-and-publishing.md): why tracking IDs wait for **Publish** and integrations do not.
* [Members & roles](/dforms/account/members-and-roles.md): who can connect a provider and who can only map fields.
* [Troubleshooting](/dforms/troubleshooting.md): a contact that never arrived, a webhook that keeps failing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dforms/connect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.