Workflow Launchers Skill — AEM as a Cloud Service

Configure and deploy AEM Cloud Service Workflow Launchers for JCR events.

1|Updated Apr 14, 2026

Search Tags:#automation #deployment #granite-workflow #aem-cloud-service #workflow-launcher #cq:WorkflowLauncher #jcr-events

Ready to run

npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-launchers-skill-aem-as-a-cloud-service

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Workflow Launchers Skill — AEM as a Cloud Service
Source: https://github.com/adobe/aem-auth-demo/tree/main/.agents/skills/aem-workflow/workflow-launchers
Command: npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-launchers-skill-aem-as-a-cloud-service

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the configuration and deployment of Workflow Launchers to automatically start workflows in response to JCR content changes on AEM as a Cloud Service.

Core Features & Use Cases

Understand how cq:WorkflowLauncher nodes trigger Granite Workflow Engine and how to configure eventType, glob, nodetype, and conditions.
Deploy and manage launcher configurations under /conf/global/settings/workflow/launcher/config (Cloud Service) to override OOTB behavior without touching /libs.
Control run modes and exclude lists to fine-tune what triggers workflows; enable/disable launchers at runtime.
Reference common patterns for DAM assets (dam:AssetContent) and page content (cq:PageContent), with examples and templates.

Quick Start

Create a new launcher under /conf/global/settings/workflow/launcher/config with your eventType, glob, nodetype, and workflow path, then deploy via your Cloud Manager pipeline.

Frequently Asked Questions about Workflow Launchers Skill — AEM as a Cloud Service

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

FAQPage Schema

How do I auto-start AEM workflows when content changes in the JCR?▼

To auto-start AEM workflows on content changes, configure Workflow Launchers that listen for JCR events. Define the eventType, glob, nodetype, and workflow path to trigger the Granite Workflow Engine automatically upon modifications.

What is a cq:WorkflowLauncher configuration in AEM Cloud Service?▼

A cq:WorkflowLauncher is a configuration node that maps JCR events to workflow execution. It specifies the eventType, nodetype, and glob path to trigger a designated workflow automatically when matching content changes occur.

How do I deploy custom workflow launchers in AEM as a Cloud Service?▼

Deploy custom workflow launchers by creating configurations under /conf/global/settings/workflow/launcher/config and deploying via your Cloud Manager pipeline. This approach overrides out-of-the-box behavior without modifying /libs.

Can I trigger AEM workflows automatically for DAM assets and page content?▼

Yes, you can trigger workflows for DAM assets and page content using common launcher patterns. Configure launchers targeting dam:AssetContent for assets and cq:PageContent for pages to automate processing on modifications.

How do I disable or fine-tune AEM workflow launchers at runtime?▼

Fine-tune AEM workflow launchers at runtime by controlling run modes and exclude lists. Enable or disable specific launchers to manage what content triggers workflows and prevent unintended automated executions.

What are the limitations of customizing OOTB workflow launchers in AEM?▼

A key constraint is avoiding modifications to /libs. Overlay and override out-of-the-box launcher behavior by deploying custom configurations under /conf/global/settings/workflow/launcher/config to ensure changes persist.