The piece begins with 'Hi everyone' rather than a headline naming the feature or benefit.
The lead mentions 'two quality-of-life improvements' but doesn't specify what they are until several sentences later.
It explains what 'Insert as JSON' does mechanically ('pull in individual values' vs 'grab the whole thing') but doesn't quantify the time or effort saved.
The content is a single dense paragraph block with only inline bold text ('Insert as JSON string', 'Insert as JSON data') substituting for headers or bullets.
The webhook trigger and 'Generate structured data' examples gesture at concreteness but no actual before/after workflow is shown.
No user quotes, usage stats, or team validation appear anywhere in the update.
The update ends mid-explanation of field types with no link, button, or instruction to try the feature.
The update opens with 'Hi everyone' instead of a headline, burying the actual feature ('Insert as JSON') in a filing-label greeting. The body is a dense paragraph block with only bolded fragments ('Insert as JSON string', 'Insert as JSON data') standing in for real structure, and it ends without any social proof or call-to-action, leaving the reader with mechanics but no next step.
Hi everyone,Two quality-of-life improvements just landed in Automations, both aimed at making it easier to pass data from one step of your automation to the next. Insert as JSONWhen you're inserting dynamic data into a later action, you've always been able to pull in individual values one at a time. Now there's a faster option: you can insert a whole group of related data at once with the new "Insert as JSON" token. This works for both a single group of details (an object) and a list of items (an array).This is especially handy when you're working with data that has a lot of nested detail, like the response from an incoming webhook trigger or the output of a "Generate structured data" action. Instead of drilling in and picking each property by hand, you can grab the whole thing in one step.You'll see one of two versions, depending on where you're inserting it:**Insert as JSON string** — appears when you're inserting into a text field. **Insert as JSON data** — appears for inputs on the← Back to the Decision Friction Index