workflow-launchers

Configure and deploy AEM Workflow Launchers that trigger workflows on JCR content changes.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill workflow-launchers-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-launchers
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/workflow-launchers
Command: npx skills add https://github.com/aemgdc/aemdev --skill workflow-launchers-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually starting AEM workflows after every content change is error-prone and does not scale. This Skill teaches how to configure Workflow Launchers that automatically start workflows in response to JCR node events on AEM as a Cloud Service, without editing immutable /libs paths. ## Core Features & Use Cases - Launcher Configuration: Create cq:WorkflowLauncher nodes with eventType, glob, nodetype, conditions, workflow, and runModes properties deployed via ui.content packages. - OOTB Launcher Overlays: Disable or modify out-of-the-box launchers like dam_update_asset_create by placing override nodes under /conf/global/settings/workflow/launcher/config/. - Loop Prevention & Debugging: Apply excludeList, session user data, and condition patterns to avoid infinite workflow loops, and verify launchers via the Launchers UI and OSGi console. - Use Case: Automatically start the DAM Update Asset workflow whenever an original rendition is uploaded under /content/dam, restricted to the author run mode. ## Quick Start Ask the assistant to create a workflow launcher that starts the DAM Update Asset workflow when a new asset is uploaded under /content/dam on the author instance.

Frequently Asked Questions about workflow-launchers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a workflow launcher in AEM as a Cloud Service?▼

Create a cq:WorkflowLauncher node under /conf/global/settings/workflow/launcher/config/ in your ui.content module, setting eventType, glob, nodetype, and the runtime workflow path under /var/workflow/models/. Add a filter.xml entry and deploy via Cloud Manager.

How do I disable an out-of-the-box AEM workflow launcher?▼

Copy the OOTB launcher node from /libs/settings/workflow/launcher/config/ to the same name under /conf/global/settings/workflow/launcher/config/ and set enabled to false. Never edit /libs directly since it is immutable on Cloud Service.

What event types can an AEM workflow launcher listen for?▼

Launchers support JCR event types as a bit-field: 1 for NODE_ADDED, 2 for NODE_MODIFIED, 4 for NODE_REMOVED, plus property events 8, 16, and 32. Combine values by addition, for example 3 listens for both node additions and modifications.

Why does my AEM workflow launcher cause an infinite loop?▼

A loop occurs when a workflow step modifies content at a path the launcher watches, retriggering itself. Prevent it by adding the workflow model to excludeList, setting the workflowmanager user data on the JCR session, or adding a condition on a flag property.

Can I restrict an AEM workflow launcher to author or publish only?▼

Yes, set the runModes property on the launcher node, for example runModes="[author]" to fire only on the author tier. Omitting runModes makes the launcher active on all run modes.