We run bi-weekly webinars as part of our business and they take place during the day, using one universal form to pull in registrants for all events regardless of which week they are for.
Currently we are using Zapier to determine the allocation of which date they are being stamped with depending on when they are submitting the form registration because HubSpot doesn’t have the same functionality (and using custom json code doesn’t work - I’ve already tried it), so what would be useful is being able to branch HubSpot workflows using submission date windows from the forms.
E.g. if a contact submits a form between 1 July and 6 July at 12pm, the relevant date property on their contact record is stamped with 6 July 2026, but if they submit the for between 6 July at 12:01pm and 15 July at 12pm, then they are stamped with 15 July 2026. Having these date stamps in place drives the entire registration workflow that sends the contact the right comms at the right time.
Having the process spread across multiple platforms is clunky and confusing for anyone who didn’t build the process out (namely me), so the question is:
When will this functionality be available?
Hi @StephShute,
What you’re describing sounds solvable through a custom code action.
using custom json code doesn’t work - I’ve already tried it
What exactly did you try? Can you share the custom code action? Such an action could grab the current date or enrollment timestamp, loop forward day by day checking for Monday or Wednesday, stop at the first match, return it.
When exactly are the webinar dates, Mondays and Wednesdays?
Best regards
I would not wait for a native branch type if this is driving registration comms today.
A clean HubSpot-only model is to treat the webinar windows as data, then stamp the contact once at registration time:
- Store each webinar date plus its cutoff timestamp somewhere controlled, for example HubDB, a custom object, or a small config list in custom code.
- On form submission, run one workflow step that compares the submission/enrollment timestamp to those cutoffs.
- Write one contact property, e.g. next_webinar_date.
- Let all reminder and attendance workflows key off that stamped date.
The important detail is timezone. Pick one business timezone for the cutoff, because 6 July 12:00 vs 12:01 can drift if the code uses UTC but the team thinks in local time.
If custom code “didn’t work”, I’d check whether it returned a real date value into a workflow output field, not just JSON text. The output field should be mapped directly into the contact date property.