workflow-triggering

Start AEM Cloud Service workflows via UI, APIs, and launchers.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-triggering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-triggering
Source: https://github.com/adobe/aem-auth-demo/tree/main/.agents/skills/workflow-triggering
Command: npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-triggering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating and starting AEM Cloud Service workflows across multiple entry points can be error-prone and manual-heavy. This skill provides a unified mechanism to trigger workflows from UI, programmatic API, HTTP endpoints, and automated launchers, enabling consistent and repeatable starts.

Core Features & Use Cases

  • Supports Timeline UI starts (manual), Manage Publication (multi-page), WorkflowSession API (programmatic), HTTP Workflow API, and Launcher-driven starts.
  • Ideal for CI/CD pipelines, automated content changes, and multi-channel workflow initiation across environments.
  • Example: trigger a review workflow for a new page via API or automatically launch a content-change workflow via a launcher.

Quick Start

Trigger a sample workflow on a test payload via the HTTP API using the runtime model path.

Frequently Asked Questions about workflow-triggering

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

FAQPage Schema
How do I trigger an AEM Cloud Service workflow from an external application?

You can trigger an AEM Cloud Service workflow externally by sending a request to the HTTP Workflow API. This requires the runtime model to be available at /var/workflow/models and proper payload handling to ensure reliable execution.

What are the available mechanisms for starting AEM workflows?

AEM workflows can be started via the Timeline UI, Manage Publication, the WorkflowSession API, the HTTP Workflow API, and automated Launchers. These mechanisms cover manual, programmatic, and event-driven workflow initiation.

Can I automatically launch an AEM workflow when content changes?

Yes, you can automatically launch an AEM workflow when content changes by configuring Launchers. Launchers start workflow models automatically based on specific repository events, requiring proper service user configuration.

Why does my AEM workflow fail to start via the API?

An AEM workflow may fail to start if the runtime model is missing from /var/workflow/models or if service user configuration is incorrect. Reliable starts require both proper service user setup and correct payload handling.

How do I trigger a review workflow for multiple AEM pages?

To trigger a review workflow for multiple AEM pages, use the Manage Publication UI mechanism. This allows multi-page workflow initiation, ensuring consistent starts across content assets without manualheavy individual processing.