Projects take part in the Automations Hub, so delivery can drive automatic follow-up the same way deals and companies do. This article covers the project-specific pieces; the full builder, triggers, and action list live in the Automations section.

A project is one of the record types an automation can watch. On a project automation, the when a field changestrigger and your conditions can read the project's stage, its delivery health (on track, at risk, or off track), its archived state, and its start, target end, and actual end dates. Pair a field-change trigger with a health or stage condition to act the moment a project slips or moves forward: notify a lead when a project turns at risk, or kick off a wrap-up flow when it reaches completed.

The Create project from templateaction packages the sales-to-delivery handoff into a flow. On a deal automation, pair it with a “when stage becomes Closed Won” trigger to create the delivery project the moment a deal is won, with no one having to click through the handoff. Leave the template blank for a plain delivery project, or pick a template to seed the project's starter tasks. It creates only one project per deal, so the flow is safe to re-run.

This action is available on deal automations, because that is where the won-deal handoff begins. The same handoff is available by hand from the deal; see From Won Deal to Delivery Project.