# contact.creation filter for forms

**URL:** <https://community.hubspot.com/t/contact-creation-filter-for-forms/115241>\
**Category:** APIs & Integrations\
**Tags:** webhooks\
**Created:** [August 26, 2024, 10:25pm UTC](https://community.hubspot.com/t/contact-creation-filter-for-forms/115241 "2024-08-26T22:25:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JWilner](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@JWilner](https://community.hubspot.com/u/JWilner)\
**Post date:** [August 26, 2024, 10:25pm UTC](https://community.hubspot.com/t/contact-creation-filter-for-forms/115241/1 "2024-08-26T22:25:59Z")

</div>

I’m trying to create a process listening for `contact.creation` events from a trial request form. What is the best way to filter those events for a specific form?

As it is now, when I get a `contact.creation` event I check the `e_submitted_form` APIs to see if the contact submitted the given event, but there seems to be at least some eventual consistency -- I’ve got to check for `e_submitted_form` a few times before it routinely shows up.

Is there a better way for me to be filtering the `contact.creation` event by a given form? Maybe a hidden field?

---

<div class="post-metadata">

**Author:** ![GRajput](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/grajput/32/102020_2.png) [@GRajput](https://community.hubspot.com/u/GRajput)\
**Post date:** [August 27, 2024, 8:38am UTC](https://community.hubspot.com/t/contact-creation-filter-for-forms/115241/2 "2024-08-27T08:38:24Z")

</div>

Hi @JWilner

To enable a unique identification of form submissions, we recommend adding a hidden field, `form_source`, to your HubSpot form. We suggest setting its value to `‘creation_request_form’`.

This field will be invisible to users but included in the contact properties when the form is submitted.

Additionally, we recommend setting up a workflow or custom code in HubSpot that triggers on the `contact.creation` event.

In this process, please verify the value of the `form_source` property. If it equals `‘creation_request_form’`, proceed with your specific workflow; otherwise, ignore the trigger.

This approach allows for immediate identification of events originating from your specific form without the need for repeated API queries using the `e_submitted_form` API.

I hope this will help you out. Please mark it as **Solution Accepted and upvote** to help another Community member.  
Thanks!