Inquiry about the “Form Submitted” trigger behavior in HubSpot

[mka9]

Hello, thank you as always for your support.

We are currently using the “Form Submitted” trigger in HubSpot for form submissions.
Is it possible to specify a start date/time for data retrieval with this trigger?

Also, when this trigger is enabled for the first time,
will it send notifications for all previously submitted form data,
or does it only apply to new submissions?

Thank you in advance for your clarification.

[Christensen · Accepted solution]

Hey @mka9, unfortunately, you can't filter form submissions by date range directly in workflow triggers.
A possible workaround is:

1. Create a custom date property for the form submission
2. Build a workflow that will save the date to the custom property when the form is submitted
3. Create your main workflow triggered by updates to that custom property then add a condition for the accepted sumission date range

It's a two-workflow setup, but it'll achieve what you need.

[RubenBurdin · Accepted solution]

Hi @mka9 , the native Form Submitted trigger is very simple, so it doesn’t let you set a start timestamp or fetch historical submissions. It only listens for new submissions from the moment the workflow is turned on, and it never “replays” old form activity. That’s why you won’t see notifications for past submissions, even if the contact has a long submission history (https://knowledge.hubspot.com/workflows/set-your-workflow-enrollment-triggers )

If you need control over a time window, the usual pattern is to store the submission moment yourself. A small companion workflow can grab the event timestamp and write it into a custom date property, then your main workflow uses that property as the enrollment trigger or as a filter for the period you care about.

This gives you predictable behavior when you need to isolate a specific campaign or form window without relying on HubSpot’s default trigger logic (https://knowledge.hubspot.com/forms/create-and-edit-forms )

If consistency between your forms and another system shapes these workflows, Stacksync carries those fields across both directions automatically.

[mka9]

Hi @Christensen , Thanks for sharing such detailed and immediately useful information so quickly.

It's a really interesting approach. I appreciate the greate idea. I'll try it out right away.

Have a wondlerful day. thank you.

[Christensen · Accepted solution]

Hey @mka9, unfortunately, you can't filter form submissions by date range directly in workflow triggers.
A possible workaround is:

1. Create a custom date property for the form submission
2. Build a workflow that will save the date to the custom property when the form is submitted
3. Create your main workflow triggered by updates to that custom property then add a condition for the accepted sumission date range

It's a two-workflow setup, but it'll achieve what you need.