# HubSpot recipe, AI Source Standard v1.0

CC BY 4.0, Broadcastwell. Documentation checked 7 October 2026.

1. Use the invited account in the client's portal. Confirm the company and portal ID. Open Settings, Properties. Select Contact properties and search both internal names. If either already exists, compare the type, group and all values before changing anything. A conflict needs the client's admin; do not create a duplicate with a suffix.
2. Choose Create property, Create manually, then enter Property label and open Edit more options. In Details, set Object type Contact, Group Contact information, label AI source and internal name ai_source. In Documentation, Property description, paste the exact description from the property JSON. In Field type, choose Dropdown select. Load options, Paste your own accepts label|value with the delimiter set to |. Enter the exact ten labels and values from STANDARD.md in its order. Preserve Custom sort and the blank default, then Create.
3. Create AI question asked, internal name ai_question_asked, Multi-line text, Contact information, exact supplied description. These are the only two standard properties.
4. Open Marketing, Forms and the existing lead form. Add the two existing contact properties. Use the visible labels How did you hear about us? and What did you ask it? Disable Required on both. Keep the source blank by default. Add the supplied helper where dependent fields are unavailable. Preview and publish only the owned form change. For an external form, verify its existing integration maps the two values. Do not assume non-HubSpot forms capture works without the required tracker and compatible HTML.
5. If the existing subscription supports it, open Automation, Workflows, Create workflow, From scratch, Contact-based. Name it AI Source Standard v1: record AI source. Choose a form submission trigger for the intended form with ai_source known. Add only Create note, associated with the enrolled contact. Body: AI Source Standard v1: ai_source = followed by the enrolled contact's AI source token, then , recorded followed by the supported current date or enrolment date token. Do not type token placeholders as plain text. Re-enrolment off. Review the action and exclude existing contacts before turning on. A plan without this action keeps the two fields and mapping, with the workflow omitted. Never upgrade or substitute an email.
6. Submit one identified test through the form with ChatGPT and test, using a test identity controlled by the client. Verify the contact property values, the dated submission and optional note. Verify no marketing action or notification was added by the workflow. Remove only that test contact after the client confirms its identifier. Retain a redacted evidence note, not personal details. Do not delete a contact that existed before the test.

The workflow writes a note, not the properties. Re-enrolment off means one qualifying note per contact; count period leads from dated submission records. Raw questions stay in the client's CRM and are reviewed before reporting.

Before testing, ask the portal administrator to check existing automatic company association and enrollment settings. HubSpot can create a company from a new contact's email domain even when the form contains no company property. Agree the test identity and cleanup scope first. Do not change portal-wide settings or remove a pre-existing company as part of installing these two fields. Source, read 7 October 2026: [HubSpot automatic company association](https://knowledge.hubspot.com/object-settings/automatically-create-and-associate-companies-with-contacts).

## Reference screenshots

These screenshots show Broadcastwell's own configuration on 7 October 2026, without contact records. Screens before Create document the reviewed settings; the publication confirmation documents the saved form. The optional note workflow was not available on this portal's free plan, so there is no execution screenshot and no live workflow test claim.

1. [AI source label, internal name and group](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-ai-source-details-before-create.png).
2. [Dropdown configuration with ten options and a blank default](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-ai-source-options-before-create.png). The viewport shows the first options; use the property JSON for the complete ordered list.
3. [AI question asked label, internal name and group](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-ai-question-details-before-create.png).
4. [Multi-line text configuration with a blank default](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-ai-question-type-before-create.png).
5. [Form automation screen before publication](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-intake-no-automation.png). The suggested email automation was not created.
6. [Approved form publication confirmation](https://github.com/Broadcastwell/ai-source-standard/blob/v1.0/templates/screenshots/hubspot-intake-form-published.png).

Sources: https://knowledge.hubspot.com/properties/create-and-edit-properties ; https://knowledge.hubspot.com/forms/create-forms ; https://knowledge.hubspot.com/workflows/create-workflows ; https://knowledge.hubspot.com/workflows/choose-your-workflow-actions ; https://knowledge.hubspot.com/forms/use-non-hubspot-forms ; https://developers.hubspot.com/docs/api-reference/legacy/crm/properties/guide . Screen availability depends on the portal plan. Reference verification, 7 October 2026: both exact properties and their ten ordered values were created and read back in Broadcastwell's own portal. One separately approved intake form was published with only Email and the two optional properties. Its live labels, optional state and blank defaults were checked. No workflow was created because the current free plan does not provide the required workflow action. Submission notifications and pre-population are off. The served contact form and existing handler delivered the exact ChatGPT and test answers to the notification and the same single synthetic contact on 7 October 2026. A Workers redirect-mode issue was corrected before the successful production verification. The same single verification contact was removed using HubSpot restorable deletion at 23:29 UTC on 7 October 2026. The filtered UI and an independent CRM search both returned zero active matches. This verifies form delivery, not analytics classification or the three human referral clicks.