# 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:** 8\
**Page:** 3

<div class="post-metadata">

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

</div>

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

You could also install a 6GB LLM along with the node package to interpret all possible forms of time definition ... I mean Apple does it with MacOS 27 happily installing 30GB of LLMs for Apple Intelligence.

---

<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:** [23 September 2026 12:40 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/42 "2026-09-23T12:40:44Z")

</div>

Just to chuck another spanner in the works - will there be scope for a (user maintained?) translation dictionary so eg

`Entre 11:30 e 21:00 às terças-feiras` can work as well as `Between 11:30 and 21:00 on tuesdays`

---

<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:** [23 September 2026 14:45 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/43 "2026-09-23T14:45:31Z")

</div>

i did think (momentarily) about supporting translations when I started this but didnt actually put any of it in place (falling back on "no one will ask for that" 😃 )

If an issue is raised, I would not shut it down.

---

<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:** [24 September 2026 17:17 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/44 "2026-09-24T17:17:32Z")

</div>

If that is the proper phrase, I can deal with that as a solution.  
No need to put too much effort in it.

Thanks for the response.

---

<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:** [25 September 2026 07:30 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/45 "2026-09-25T07:30:35Z")

</div>

> [@FireWizard52](#):
>
> No need to put too much effort in it.

Too late 😉

Next version (soon):

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

---

<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:** [25 September 2026 08:23 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/46 "2026-09-25T08:23:14Z")

</div>

You are so fast 😃

---

<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:** [25 September 2026 08:31 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/47 "2026-09-25T08:31:26Z")

</div>

Looking good Steve.

More possibly desirable features, sort of rate limiting:

Only the first message after 0, 15, 30, 45 minutes past the hour.

Pass every nth message (per msg.topic) regardless of filter settings.

Allow msg.force to bypass the filter checks.

---

<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:** [25 September 2026 08:42 UTC](https://discourse.nodered.org/t/coming-in-cron-plus-v3-a-cron-filter-node-with-natural-language-conditions/101707/48 "2026-09-25T08:42:00Z")

</div>

it has crossed my mind (a "first or once directive") but for now, I am keeping things atomic (e.g. an RBE/filter node can quite easily achieve this) - perhaps worth a demo flow until I decide what to do!?

in the meantime, an issue is here: [when gate: "first only" support · Issue #155 · Steve-Mcl/node-red-contrib-cron-plus · GitHub](https://github.com/Steve-Mcl/node-red-contrib-cron-plus/issues/155)

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