This plugin-specific Automation event creates a full project structure from a selected template. Sub-projects, tasks, assignments, blocking relationships, and template-authored defaults all come from the template; the event itself provides the root project's basic input values.
Use this event when your automation needs to materialize a whole project structure from a trigger. It is especially helpful for repeatable processes such as onboarding, intake, follow-up, or request-driven work where one triggering event should produce the same project scaffold every time.
Fields
- Project Template is required and dictates the created project's type and structure.
- Project Name is required and can use trigger merge fields to generate a dynamic root-project name.
- Details is optional and can also use trigger merge fields.
- Due Date In Days optionally sets the root project's due date relative to today, which in turn anchors any template due-date offsets.
Tip
This event is fire-and-forget. If you need to keep working with the newly-created project later in the automation, launch a workflow and use the Create Project workflow action instead so you can store the created project's Guid in a workflow attribute.
The event is best when the automation only needs to create the project and then stop. If the next steps depend on the newly-created project itself, such as setting more attributes, routing it, or doing additional logic against that specific record, launch a workflow and use the Create Project workflow action instead.
The event's own Lava fields are rendered against the trigger's merge fields. That is separate from Lava embedded inside the selected project template. Template-authored names, descriptions, and attribute values render later against ParentProject, RootProject, and CurrentPerson; see Lava in Templates for details.