How to Filter HubSpot “Last CV” Updates Within the Past Hour?

Beginner Questions
,
1

:bullseye: What is your goal?

I want to send a Slack notification every hour when a HubSpot contact’s last CV is updated. To do this, the scenario should trigger only when the last CV timestamp is within the past hour since the previous run.

:thinking: What is the problem?

I need to filter contacts based on their last CV time within the past hour, but my filter condition isn’t working. Using addHours(now; -1) results in an error, and I’m not sure how to correctly specify the filter.

:test_tube: What have you tried so far?

I attempted to add a filter in the Make scenario using the expression addHours(now; -1) to capture contacts whose last CV value is within the past hour. However, Make returned an error when processing this expression. I haven’t found an alternative filter setup that works yet.

2

HubSpot sends timestamps in ms, so you must convert them first. Use a filter like: parse Date(last_cv) > add Hours(now; -1). This is the correct way in Make to check updates within the past hour.

1 Like
3

Thanks for the guidance! I tried building a filter using parseDate(…​) and addHours(now; -1) as you suggested. In my case, I replaced last_cv with the “Recent Conversion Date” property (see attached screenshot). Unfortunately, the filter still throws an error when I try to save it.

It seems the filter UI isn’t accepting the expression, or I might be missing something in the syntax. The Last CV/Recent Conversion Date is a date/time property in HubSpot, so I assumed parsing and comparing it should work. Are there any additional steps I need to take to convert the timestamp or apply the function correctly?

Any further advice would be greatly appreciated!

image
image430×232 11.5 KB

4

Hey! Try to use datetime operators instead of Time operators. Used to work for me, also without the parse theoretically.

image

1 Like
5

You don’t just put it inside a parseDate(), you have to actually tell it what the format is.

1 Like
6

Thanks a lot, that was exactly it!

Switching the filter from Time operators to Datetime operators did the trick.

Now the filter with Recent Conversion Date > addHours(now; -1) works without any more 400 errors and my “last 1 hour conversions only” scenario is running perfectly again.

Really appreciate you sharing this tip :folded_hands:

1 Like
7

Happy to hear it! Keep on automating!