# Coming in cron-plus v3: a "Cron Filter" node with natural language conditions

**URL:** <https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707>\
**Category:** General\
**Created:** [31 August 2026 14:52 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707 "2026-08-31T14:52:45Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [1 September 2026 13:36 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/21 "2026-09-01T13:36:50Z")

</div>

> [@mudwalker](#):
>
> My week starts on a Sunday, as I was taught in school more than 'just a few years ago'. But then I am probably in the minority and Heaven Forbid if I go against ISO Standards. (said Tongue in Cheek!) (Tickbox for Start of Week?)

TBF, "last day of the week" is the same as saying "on sunday" (or "on saturday" if you are from a crazy part of the world 😉 ) so a tick box is probably just adding complication.

I think it makes sense to leave "of the week" ISO standard.

But I have noted you comment and not 100% ruled it out just yet.

And thank you for the feedback.

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [1 September 2026 14:17 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/22 "2026-09-01T14:17:32Z")

</div>

I would prefer 'Time Gate' to 'Cron Filter' as it is not necessarily tied to cron-plus

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [2 September 2026 10:20 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/23 "2026-09-02T10:20:37Z")

</div>

Though it would forever remind me of the superb Stargate Si-Fi series. 😃 No bad thing though.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [2 September 2026 11:13 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/24 "2026-09-02T11:13:06Z")

</div>

Changing my preference re node name from `Time Gate` to `Cron Plus Gate` 😀

"Cron Plus" because it's part of the `Cron Plus` group and also to reflect that it's not limited to cron related triggers.

"Gate" because of `Simple Gate` and `Queue Gate`

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 September 2026 12:50 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/25 "2026-09-02T12:50:23Z")

</div>

I'm thinking of naming the node simply `"when"` 🤔

_(note the underlying distinction between packages will still be "cron-filter", "when" would be a display name!)_

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [2 September 2026 13:34 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/26 "2026-09-02T13:34:50Z")

</div>

> [@Steve-Mcl](#):
>
> I'm thinking of naming the node simply `"when`

Just about sums up 'it all', like it!

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [2 September 2026 14:30 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/27 "2026-09-02T14:30:31Z")

</div>

> [@Steve-Mcl](#):
>
> I'm thinking of naming the node simply `"when"`

The only downside of that is that it is such a short name and might easily end up with a name clash? Shouldn't such short, generic names be reserved for core features rather than contributed nodes?

And actually, I am not convinced that it gives enough meaning to be able to pick it out from the crowd. Having the "gate" postfix accurately describes its effect.

So maybe `when-gate`?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 September 2026 15:07 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/28 "2026-09-02T15:07:25Z")

</div>

> [@TotallyInformation](#):
>
> when-gate

I like - top of the list!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 September 2026 15:20 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/29 "2026-09-02T15:20:02Z")

</div>

Sounds good to me.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 September 2026 19:16 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/30 "2026-09-04T19:16:19Z")

</div>

Forgot to mention, v3.0.0 is now live.

Hopefully I didn't break anything (or too much)

I have zero doubt that some of the most obvious `when gate` phrase support has been overlooked and you will all hopefully be kind in pointing that out.

Anyhoo, happy Friday.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [5 September 2026 00:01 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/31 "2026-09-05T00:01:42Z")

</div>

Altitude and Azimuth are important solar (and lunar) properties. eg the sun shines into Newgrange when it's azimuth is between 134 and 138 degrees and it's altitude is greater than 0.5 degrees.

The node seems not to understand an input including the words altitude or azimuth, though "sun above 30" is accepted and explained as "Allow when: sun altitude is above 30 degrees"

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/a/daa211aa0218546880e464e2240bfd177bd1e325.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [5 September 2026 08:40 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/32 "2026-09-05T08:40:37Z")

</div>

> [@jbudd](#):
>
> azimuth is between 134 and 138 degrees and it's altitude is greater than 0.5 degrees.

Coming soon

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/9/29c4b3acb1ff89e7d7d084603d9b9db53b45841d.png)

---

<div class="post-metadata">

**Author:** ![RandomSporadicProjs](https://avatars.discourse-cdn.com/v4/letter/r/e19adc/32.png) [@RandomSporadicProjs](https://discourse.nodered.org/u/RandomSporadicProjs)\
**Post date:** [6 September 2026 09:03 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/33 "2026-09-06T09:03:23Z")

</div>

Looks interesting.

4  
Chrono-logic  
or  
Crono-logic

---

<div class="post-metadata">

**Author:** ![smanjunath211](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/smanjunath211/32/95742_2.png) [@smanjunath211](https://discourse.nodered.org/u/smanjunath211)\
**Post date:** [8 September 2026 05:51 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/34 "2026-09-08T05:51:36Z")

</div>

Awesome concept, especially text based instructions feature

here are few suggestions for names

`cron-guard`, `cron-sieve`, `chronogate`, `cron-if`

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [15 September 2026 12:54 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/35 "2026-09-15T12:54:02Z")

</div>

I tried this as the input to the Node. Any use to you?

`daily between civilDawn to 2130h`

 ![Screenshot from 2026-09-15 13-43-16](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/c/ec9c6e9022717276f380d0615d4e27e5b45763f6.png)

DOesn't seem to like a mix of named times and HHMMSS

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [15 September 2026 14:18 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/36 "2026-09-15T14:18:52Z")

</div>

Thanks for the feedback. "daily" is a synonym i missed (will add) (you could already enter "every day" or "always" or just leave it out tbh!)

civilDawn is effectively "dawn" but I will add explicit support for "civil dawn/dusk" so it avoids ambiguity.

As for `2130h`, `21:30` works but i think I will add support for the military `nnnnh` version too.

---

<div class="post-metadata">

**Author:** ![FireWizard52](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/firewizard52/32/34508_2.png) [@FireWizard52](https://discourse.nodered.org/u/FireWizard52)\
**Post date:** [22 September 2026 17:29 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/37 "2026-09-22T17:29:59Z")

</div>

I wanted to use something similar as @mudwalker.  
I wanted to control the output every hour on the hour, but only between sunrise and sunset.  
So e.g. 08:00, 09:00, 10:00, but not 02:00.

I don't think it is very unusual or complicated, but maybe I'm missing the proper English phrase.

![Cronplus-When-Gate1](https://us1.discourse-cdn.com/flex026/uploads/nodered/optimized/3X/3/2/326488653283ac4fa2249d7b7ec1010c78a2b20b_2_690x59.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 September 2026 18:43 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/38 "2026-09-22T18:43:39Z")

</div>

"on the hour" is something i could add, but for now:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/d/8d15cfe18a8f5544d1b5f243a12e0694235d2ff1.png)

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [22 September 2026 19:57 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/39 "2026-09-22T19:57:29Z")

</div>

> [@Steve-Mcl](#):
>
> "on the hour" is something i could add, but for now:

This looks like another example where the node's stated understanding "every hour" is not accepted as an input to the node. This does not make sense to me!

Of course "On the hour" quickly gets more complicated: "At 2, 6, 10, ...58 minutes, between morning nautical twilight and sunrise".

Once you go down the rabbit hole ...  
🐇 🌑

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [23 September 2026 07:22 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/40 "2026-09-23T07:22:10Z")

</div>

> [@jbudd](#):
>
> Once you go down the rabbit hole ...

It’s always 6 o’clock at the mad hatters tea party…

[Previous page](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707.md?page=1)

[Next page](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707.md?page=3)