Learn how to launch Cotonity automation workflows whenever a visitor submits a HubSpot form, enabling instant personalized follow-up.
Setting up the form trigger
In Cotonity, navigate to Triggers → HubSpot Form Submission and click Add Trigger. Select the HubSpot portal and then choose one or more specific forms from the dropdown — or select All Forms to catch every submission. Cotonity registers a HubSpot webhook internally; no manual configuration in HubSpot is required. The trigger activates within seconds of a form being submitted and passes the full submission payload — all field values, submission timestamp, page URL, and HubSpot contact ID — to the Cotonity workflow as trigger variables.
Accessing form field values
Every form field value is available in your workflow using the expression syntax {{trigger.form.fieldName}}. Field names correspond to the HubSpot internal property name (e.g., firstname, email, hs_persona). For multi-select fields, the value is an array you can iterate over using Cotonity's loop action. If you are using a progressive profiling form, only the fields visible on the specific submission are included in the payload; use conditional branches to handle partial submissions gracefully without failing the workflow.
Routing by form type
A single Cotonity workflow can handle submissions from multiple forms by using conditional routing based on {{trigger.form.formId}} or a custom form identifier property. For example, route Contact Us submissions to a human handoff queue, demo request submissions to a qualification agent, and newsletter sign-up submissions to a simple acknowledgment sequence. This consolidates your automation logic in one place while still delivering tailored responses for each form type.
Preventing duplicate triggers
HubSpot can occasionally send duplicate webhook events in rare edge cases. Cotonity's trigger deduplication layer checks the HubSpot submission GUID included in the payload and ignores any duplicate event received within a 60-second window. You can adjust this deduplication window in Trigger Settings. For workflows where idempotency is critical — such as booking confirmations — also add an explicit deduplication check on the contact's email address at the start of the workflow to guard against any gaps in the deduplication layer.