We have recently released two new options for the webhook body that we are sending out.

1. you can now pick the API version number defining the format of the payload that we are sending out

2. you can also decide if you want to have directly expanded in the record value the nested blocks that might be part of it

Have a look at the interface:

Some of the most useful and used triggers for our webhooks are those revolving around records creation/update/deletion, and when it comes to a "record update" event, it is very common the need to know exactly what has changed. So far, it was not that easy to get that information.

Well, now it is! For "record update" events, the webhook payload now presents the record data both before the update operation (previous_entity) and after (entity), making diffs extremely easy on your end.

Integrations/automations like "only do X if the title has changed" are like 1000% faster to develop:

1
{
2
  "environment": "foo-bar",
3
  "entity_type": "item",
4
  "event_type": "update",
5
  "entity": {
6
    "id": "39830648",
7
    "type": "item",
8
    "attributes": {
9
      "name": "Mark Smith",
10
    },
11
    "relationships": { ... },
12
    "meta": { ... }
13
  },
14
  "previous_entity": {
15
    "id": "39830648",
16
    "type": "item",
17
    "attributes": {
18
      "name": "John Smith",
19
    },
20
    "relationships": { ... },
21
    "meta": { ... }
22
  }
23
}

For security reasons, we have decided to remove any previously saved Netlify/Vercel token information from all existing build triggers. This change no longer allows you to view build logs directly from within the DatoCMS interface.

The reason for this change is that a project's read-only token API has read access to build triggers, but these were exposing third-party tokens that potentially allowed destructive operations to be performed. If you have publicly shared any DatoCMS key and you have build triggers pointing to Netlify/Vercel, we recommend rotating the keys of these these services.

Another day, another improvement to DatoCMS!

Building up from our recent addition of MD5 metadata to assets, we can now warn the user when there's an asset in the Media Area with the same signature as the file they're trying to upload:

Today we're really happy to announce a small, nifty addition that we're sure a lot of people will find useful! We called it Quick Search, and it allows to find all records matching a specific criteria around your whole project.

You can launch Quick Search using the little "magnifying glass" icon that's always present at the top-right or, even faster, using the ⌘+P (or Ctrl+P) keyboard shortcut:

Small, great addition today. You can now see which records point to the current record via Link fields! Some plugins were already available to perform the same job, but the need is so common that we decided to add it everywhere 😉

This is a nice addition to the Media Area: you can now see the MD5 hash of any asset you upload to DatoCMS. You can also search for MD5 in your Media Area, to see if the same asset is already present!

This is especially useful in automated scripts: the same information/query is also available both on our Content Management API and Content Delivery API:

This was long overdue, but we finally found some time to update our Yeoman Plugin generator to make use of the latest React version, and improved the default React skeleton with hooks!

npm update -g generator-datocms-plugin

We made some improvements to webhooks! You can now "pause" webhooks by temporarly disabling them, and use Mustache templates not only to compose a custom HTTP payload, but also to personalize the URL:

You can now change the sort order of the records by the field of your choice: