NocoDB On Record Update Webhook is not Triggered.

[flachdaniel]

Hi!

We have 3 bases:

• Products
• Warehouse1
• Warehouse2

The Products may have one-to-one links to warehouses if that warehouse contains the product.

In the warehouses we are tracking the product inventory in that warehouse.

We also have 2 Lookup fields in the Products table for the Warehouse1_Inventory and for the Warehouse2_Inventory.

We have a "Biggest_Inventory" formula field in the Products table:

MAX({Warehouse1_Inventory}, {Warehouse2_Inventory})

which is tracking our biggest Inventory for that product in a given Warehouse.

However:

If we are updating the Warehouse Inventory via API call, then the Biggest_Inventory is updated on the Products table, BUT the On Record Update Webhook for the Products table is not triggered.

Is this a bug?
Is there a workaround?

[dosubot[bot]]

The "On Record Update Webhook" in NocoDB is not triggered when the "Biggest_Inventory" field in the "Products" table is updated via an API call because the webhook will only be triggered if the configured condition was not met before the record was updated and is met after the update.

From the documentation:

The webhook will be triggered only when Condition(old-record) = false and Condition(new-record) = true.

If the condition for triggering the webhook is not met by the changes made via the API call, the webhook will not be triggered.

Workaround:
Ensure that the condition for the webhook is correctly configured to detect the changes made by the API call. If no specific condition is required, you can configure the webhook without any conditions to ensure it triggers on any update.

Configuring webhook

1. Name of the webhook
2. Select the event for which webhook needs to be triggered

Trigger	Details
After Record Insert	After a single record is inserted
After Record Update	After a single record is updated
After Record Delete	After a single record is deleted
After Multiple Record Insert	After bulk records are inserted
After Multiple Record Update	After bulk records are updated
After Multiple Record Delete	After bulk records are deleted
Manual Trigger	Manually trigger webhook using button field

3. Method & URL: Configure the endpoint to which webhook needs to be triggered. Supported methods are GET, POST, DELETE, PUT, HEAD, PATCH
4. Headers & Parameters: Configure Request headers & parameters (optional)
5. Condition: Only records meeting the configured criteria will trigger webhook (optional)
6. Test webhook (with sample payload) to verify if parameters are configured appropriately (optional)
7. Save the webhook

Webhook with conditions

In case of webhook with conditions, only records meeting the configured criteria will trigger webhook. For example, trigger webhook only when Status is Complete. You can also configure multiple conditions using AND or OR operators. For example, trigger webhook only when Status is Complete and Priority is High.

The webhook will be triggered only when the configured condition wasn't met before the record was updated. For example, if you have configured webhook with condition Status is Complete and Priority is High and you update the record with Status Complete and Priority Low to High, webhook will be triggered. However, if you update any other fields of the record with Status Complete and Priority High, webhook won't be triggered.

In summary, the webhook will be triggered only when Condition(old-record) = false and Condition(new-record) = true.

Ensure that the webhook is configured correctly to detect the changes you are making via the API ^[1][2].

To continue talking to Dosu, mention @dosu.

[flachdaniel]

The "Trigger On Condition" is turned off for the webhook and IS working if I update a field on the table itself manually.

However, seems like the fields which have a Lookup to other tables and even the fields which are derived from those Lookup fields does not trigger the "On Update" condition, even when you can clearly see the value changing in the table.