# Allow Forms to Associate Multiple Object Types (e.g. Ticket ↔ Custom Object)

**URL:** <https://community.hubspot.com/t/allow-forms-to-associate-multiple-object-types-e-g-ticket-custom-object/141343>\
**Category:** HubSpot Ideas\
**Tags:** forms, object\
**Created:** [October 21, 2025, 6:29am UTC](https://community.hubspot.com/t/allow-forms-to-associate-multiple-object-types-e-g-ticket-custom-object/141343 "2025-10-21T06:29:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![samaramoliveira](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samaramoliveira/32/14569_2.png) [@samaramoliveira](https://community.hubspot.com/u/samaramoliveira)\
**Post date:** [October 21, 2025, 6:29am UTC](https://community.hubspot.com/t/allow-forms-to-associate-multiple-object-types-e-g-ticket-custom-object/141343/1 "2025-10-21T06:29:33Z")

</div>

**Current Limitation**  
When a HubSpot form includes properties from multiple objects — for example, _Contact_, _Ticket_, and a _Custom Object_— the form can only:

- Create or update the **contact** , and
- Optionally create **one additional object** (e.g., a ticket).

The result: if both a ticket and a custom object are created through a form, they are **not automatically associated** with each other. Both end up associated only to the contact.

**Why This Is a Problem**  
Many service and operations use cases rely on linking multiple records together from one submission.  
Example:

- A customer submits a “Repair Request” form.
- The submission creates a Ticket (the request) and an Item (the product being repaired).
- The team needs those two records linked to track service status by product, without manual association or complex workarounds.

Currently, the only workaround is to use **workflows** that recreate the custom object and associate it afterward, which requires duplicating all related properties as temporary contact fields. This increases maintenance overhead, risk of errors, and makes large-scale setups unwieldy.

**Suggested Enhancement**  
Enable **form-based multi-object association** , where:

- A form can associate two or more objects upon submission (Ticket ↔ Custom Object ↔ Contact).
- Or, allow a form to pass a unique identifier (e.g., Serial Number or Custom Object ID) to associate an existing record instead of creating a new one.
- Additional option: expose association logic as an advanced form action, similar to the “create record” option available today.

**Business Impact**  
This improvement would streamline multi-object processes like:

- Product registrations
- Warranty claims
- Equipment repairs
- Service requests tied to assets or accounts

It would significantly reduce reliance on redundant properties and workflows, improving data integrity and user experience for both teams and customers.