Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

🔗Connect & Integrations

Send every Dapta Forms 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 Conn

Dapta Forms 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.

The Connections page opened from the Integrations entry in the rail, with HubSpot and Calendly connected
Connect once here, then map fields per form.

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

The Connect tab of a form showing the Integrations section with a Webhook card and a HubSpot card
The Connect tab. Integrations first, then Tracking & pixels and Emails.
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) and the Respondent confirmation (to the respondent): follow the account template or customize them for this form.

The Tracking and pixels section followed by the Emails section in the Connect tab
Further down the same tab: tracking IDs and the two submission emails.

💡 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 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 Dapta Forms queue one delivery per enabled integration (webhook, HubSpot, email). 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.

In this section

  • Connections (account level): connect HubSpot and Calendly with a token, see who is connected, disconnect, and review the webhooks inventory.

  • HubSpot: sync respondents as contacts, map questions to properties, translate values, stamp UTMs, score and outcome.

  • Scheduler step & Calendly: let respondents book a meeting inside the form.

  • Webhooks: POST each submission as JSON to a URL you control, signed and retried.

  • Tracking & pixels: GTM, Meta Pixel, PostHog and HubSpot tracking on the public page.

  • Submission emails: the notice you receive and the confirmation the respondent receives.

  • Delivery, retries & history: what happens after a submission, retry schedule, statuses.

What's next

PreviousBrand kit (workspace-wide)
NextConnections (account level)

Last updated