Skip to content
Default help center home
Default help center home

Forms FAQ

General

Q: Can I use Typeform?

A: No, Default does not support Typeform at this time. If you are looking to migrate form systems, we recommend using our own Default Forms.Default Forms are no-code, making them easy to style.


Q: What are Default lead attributes?

A: Default lead attributes are completely optional and allow you to push certain fields automatically over to your CRM, as defined in your Field manager page. All form input fields can otherwise be referenced within a workflow and pushed to any CRM field as needed.


Q: How come I can't see data for certain fields in pipeline?

A: If you’re missing columns in your pipeline from the Lead attribute list below, then please double-check if you’ve mapped it as a lead attribute field.

  • First name

  • Last name

  • Company name

  • Headcount

  • Role

  • Job title

  • City

  • Location

  • Industry

HubSpot Forms

Q: How does Default pick up on my primary form if there are multiple on the page?

A: During the form connection process your submission sends us a form identifier. This is expected to be unique for each form.

We store this form identifier under a <meta> tag on our end, and when submissions are sent, match it to the stored identifier.

By default, our snippet only tracks a single form on the page based on the criteria in the first two bullets.

With that being said, if you want to send all form submissions on page to a single workflow in Default, you can pass in strict mode = true in your snippet from Step 1.


Q: I just added new fields to my web form. How does Default check for new fields?

A: On any webform (including a HubSpot form) you have the option to update fields within Default. When you do so, you will be asked to follow the steps and submit a new response from your public-facing form to Default. Default will automatically listen for new form fields, and omit any fields that were removed.

Forms observability

Q: Where do errors come from? Are errors surfaced from client-side or server side?

A: Both types of errors are tracked.

Client-side errors are marked with the prefix [Webform script error] to distinguish them from backend errors.


Q: What happens if Default fails to load on page? Will client-side errors be captured if the script fails to load?

A: No, since the error reporting code is contained within the script itself.

Your developers can add a onerror() handler for the script as below:

<script> (function (w, d) { w.__default__ = { team_id: xxx, form_id: xxxxxx }; var s = d.createElement("script"); s.async = true; s.src = 'https://import-cdn.default.com/v2/index.js'; s.onerror = function () { // log error to analytics or error tracker } d.head.appendChild(s); })(window, document); </script>

Q: Can errors be sent from through Default, via the onerror() handler?

A: Yes, you can forward any errors to Default to receive notifications for them:

<script> (function (w, d) { w.__default__ = { team_id: xxx, form_id: xxxxx }; var s = d.createElement("script"); s.async = true; s.src = 'https://import-cdn.default.com/v2/index.js'; s.onerror = function () { fetch("https://nucleus.default.com", { method: "POST", headers: { "Content-Type": "application/json", }, body: JSON.stringify({ form_id: "xxx", // put your form_id here errorMessage: "script failed to load", }), }); } d.head.appendChild(s); })(window, document); </script>

Q: Does this work for all Default form systems?

A: Yes, form observability is available for all form systems - including 3rd party (non-Default form) forms


Q: How does Default alert me? Where can I find these notifications?

A: For Slack: Located in your Default Slack app DMs. You can find it from:

  • Slack App > Scroll down to Slack App (usually at the bottom) > Default

For Others:

  • In app notifications > notification sidebar in app

  • Email > email

Note: Only users in Default with the admin role are eligible to receive these notifications.