Naming the fields your webhook saves is easier to get right

Released 21 August 2026

Picking the fields a webhook should save is a naming job, and naming was the awkward part. Both halves of that are fixed: the name box keeps your cursor, and a name that will not work says so where you write it.

What's new

• The cursor stays in the box. Typing a name under Save fields to use later used to push the cursor out after every letter, so a name had to be typed straight through and could never be corrected in the middle — one slip and the row had to be deleted and done again. It now behaves like any other box: type, click back into the middle, fix a letter.
• A name that will not work is marked in red, on its own row. A name used twice, a name with a space or a dash in it, or a row with only half of it filled in — each is flagged where it happens, as you type. Before, the only sign was the whole trigger refusing to save, without saying which row was the problem.
• Quieter warnings for the things that are allowed but rarely meant. Naming a field the same as one of the automatic hook_ fields will replace it, and saving the same piece of data twice under two names works but is not needed. Both are pointed out without stopping you — sometimes they are exactly what you intended.

Worth knowing

• Nothing in red means it will save. The checks in the form are the same rules the trigger is judged by when you save it, so a clean form is a form that goes through.
• The rules themselves have not changed. Letters, numbers and underscores, starting with a letter, and each name used only once. Names are case-sensitive, so total and Total are two different fields — the form now says so when you have both.