Flows keep getting more capable, and this is a big batch of new building blocks. A single automation can now do work that used to need custom code or a separate tool.
New bricks
- Generate PDFs — produce a document from your data: an invoice, a work order, a certificate — then attach it, email it, or store it.
- HTTP requests — richer options for calling external APIs, with control over headers, body, and how the response maps back into your data.
- Email — send from a specific address, include attachments, and optionally send silently when it's a system message rather than a notification.
- Add comment — post a comment to a record from a flow, so automated updates land in the same conversation as human ones.
- If changed / changed to — branch on exactly what changed about a record, not just its current state, so flows react precisely.
Why it matters
Put together, these turn flows into something closer to a workflow engine. "When a deal is marked won, generate the contract PDF, email it to the client, post a comment, and call our billing API" is now a handful of bricks — no developer required.
See what's possible on the features page.