# Webhook with conditions (date based)

**URL:** <https://community.nocodb.com/t/webhook-with-conditions-date-based/1292>\
**Category:** Webhooks\
**Created:** [July 26, 2024, 5:43am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292 "2024-07-26T05:43:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![elad](https://avatars.discourse-cdn.com/v4/letter/e/6bbea6/32.png) [@elad](https://community.nocodb.com/u/elad)\
**Post date:** [July 26, 2024, 5:43am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/1 "2024-07-26T05:43:23Z")

</div>

Is there a way to generate a webhook based on the date and time it arrived?

---

<div class="post-metadata">

**Author:** ![Navi](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@Navi](https://community.nocodb.com/u/Navi)\
**Post date:** [July 26, 2024, 5:48am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/2 "2024-07-26T05:48:20Z")

</div>

Create a [webhook with conditions](https://docs.nocodb.com/automation/webhook/create-webhook/#webhook-with-conditions) as detailed here.

You can choose the field in question and use a filter value accordingly.

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/3378dee394fbe7ee2e0321853241e132b6f815fb.png)

---

<div class="post-metadata">

**Author:** ![elad](https://avatars.discourse-cdn.com/v4/letter/e/6bbea6/32.png) [@elad](https://community.nocodb.com/u/elad)\
**Post date:** [July 26, 2024, 7:09am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/3 "2024-07-26T07:09:18Z")

</div>

Thanks, but you didn’t answer my question. I am asking about the activation of the webhook at a certain date, at a certain time. For example, when a certain date arrives at 8:00 p.m.

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [July 26, 2024, 7:13am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/4 "2024-07-26T07:13:21Z")

</div>

Webhook triggers currently are only based on change in record state (insert | update | delete). Time based webhook triggers are not supported. What is your use case?

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [July 26, 2024, 7:14am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/5 "2024-07-26T07:14:57Z")

</div>

The point @Navi made above here is – if you wish to trigger a webhook based on arrival time of a particular record, then you can do so by making use of conditional trigger support in webhook & records “Created-at” time field.

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [July 26, 2024, 7:26am UTC](https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/6 "2024-07-26T07:26:23Z")

</div>

A Github issue to track this requirement is created. You can vote-up &/ add more relevant details to help us further

> <https://github.com/nocodb/nocodb/issues/9080>
>
> \### Please confirm that the feature request does \*\*\*not\*\*\* already exist
> 
> \- \[X\] …I confirm there is no existing issue for this feature request.
> 
> \### Use case
> 
> Add support for CRON job based Webhook trigger -- 
> This would allow one to automate tasks on a scheduled basis by invoking a webhook. Useful for scenarios where you need to perform periodic operations or data synchronization tasks at regular intervals. 
> 
> Source : https://community.nocodb.com/t/webhook-with-conditions-date-based/1292/2
> 
> \### Suggested solution
> 
> Add a new trigger for webhook : allow webhook to be triggered at a pre configured time instead of just record based trigger.
> 
> \### Additional context
> 
> Information that needs to be sent in the payload - if configuration is allowed needs to be decided, as we do not have a direct reference for a view record in this case.