Attio
Changelog7-point breakdown
'What's new in Workflows' names the feature category rather than the outcome, functioning as an internal filing label.
'More of the work, off your plate' opens with a concrete benefit before any feature name is introduced.
Lines like 'the loop block now iterates over arrays of objects' are followed by outcome tags ('so batch work... runs end to end') but the pattern is mechanical and repeats for every bullet.
Structured-output, loop, integration, and error-messaging updates are all run together in one continuous paragraph with no headers or bullet breaks.
Named tools like Notion, Lemlist, and Webflow add specificity, but there's no before/after comparison showing what the workflow looked like without these changes.
No customer name, quote, or adoption metric appears anywhere in the update despite claims of increased power.
Closing actions are direct and specific: 'Watch workshop,' 'find out more in our Help Center,' and 'Get started with the SDK docs.'
The headline 'What's new in Workflows' is a filing label that tells readers nothing about the benefit inside, despite a genuinely strong lead ('More of the work, off your plate'). The body reads as an undifferentiated feature dump—structured outputs, loop blocks, app connections, error messages—stitched into one paragraph with no visual separation, and no customer example or usage metric ever validates that any of this works in practice.
What's new in Workflows Copy link to this entry More of the work, off your plate. Workflows put your customer context to work, turning repeatable tasks into agents that run themselves. Earlier this month, we launched blocks with custom agents, code execution, and apps like Notion, Linear, and Fin. Now, it's getting even more powerful: Define agent outputs. Custom Agents now support structured outputs: define the schema you want and the agent returns only those fields, so its result perfectly fits your next blocks. Loop over anything. The loop block now iterates over arrays of objects, not just simple lists, so batch work across nested data runs end to end. Connect more of your stack. New app blocks and native field support across your tools: find leads by email and pause them in campaigns with Lemlist, plus native email and phone support for Linear, Typeform, and Webflow. Error messages now point you to the problem too. See exactly which block received bad data, so a stalled workflow i← Back to the Decision Friction Index