[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736CADH8M6RQ8RVC76Z2DR8":3,"skill-same:01M736CADH8M6RQ8RVC76Z2DR8":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M736CADH8M6RQ8RVC76Z2DR8","workflow-triggering",null,"Start AEM Workflows on AEM as a Cloud Service using all available triggering mechanisms. Use when starting workflows manually via the Timeline UI, programmatically via WorkflowSession.startWorkflow(), via the HTTP Workflow API, through Manage Publication, or passing initial metadata and payload to a workflow instance.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: workflow-triggering\ndescription: Start AEM Workflows on AEM as a Cloud Service using all available triggering mechanisms. Use when starting workflows manually via the Timeline UI, programmatically via WorkflowSession.startWorkflow(), via the HTTP Workflow API, through Manage Publication, or passing initial metadata and payload to a workflow instance.\nlicense: Apache-2.0\n---\n\n# Workflow Triggering (Cloud Service)\n\nAll mechanisms to start a workflow on AEM Cloud Service — from UI, programmatic API, HTTP API, and Manage Publication.\n\n## Variant Scope\n\n- AEM Cloud Service only.\n- Use service users with `workflow-process-service` sub-service mapping for programmatic triggering.\n\n## Triggering Mechanisms Summary\n\n| Mechanism | Use Case |\n|---|---|\n| **Timeline UI** | One-off manual start on a single page or asset |\n| **Manage Publication** | Multi-page batch start, integrates with publish pipeline |\n| **WorkflowSession API** | Backend Java code, scheduled jobs, event handlers |\n| **HTTP Workflow API** | REST calls, scripts, external integrations |\n| **Workflow Launchers** | Automatic on JCR events — see `workflow-launchers` skill |\n\n## 1. Manual via Timeline UI\n\n1. Navigate to a page or asset in Sites\u002FAssets console\n2. Open **Timeline** panel (clock icon)\n3. Click **Start Workflow**\n4. Select the model from the dropdown\n5. Optionally enter a workflow title and comment\n6. Click **Start**\n\nThe workflow starts with the selected item as `JCR_PATH` payload and the current user as initiator.\n\n## 2. Manage Publication (Multi-Page)\n\n1. Sites Console → select pages → **Manage Publication**\n2. Choose action (Publish \u002F Unpublish)\n3. Check **Include Workflow**\n4. Select workflow model\n5. Click **Publish Later** or **Publish Now**\n\nAEM creates a `cq:WorkflowContentPackage` containing all selected pages as the workflow payload.\n\n## 3. Programmatic (WorkflowSession API)\n\n```java\n@Component(service = MyWorkflowService.class)\npublic class MyWorkflowService {\n\n    @Reference\n    private ResourceResolverFactory resolverFactory;\n\n    public String startWorkflow(String payloadPath, String modelId,\n                                Map\u003CString, Object> initialMeta) throws Exception {\n        Map\u003CString, Object> auth = Collections.singletonMap(\n            ResourceResolverFactory.SUBSERVICE, \"workflow-process\");\n        try (ResourceResolver resolver = resolverFactory.getServiceResourceResolver(auth)) {\n            WorkflowSession wfSession = resolver.adaptTo(WorkflowSession.class);\n            WorkflowModel model = wfSession.getModel(modelId);\n            WorkflowData data = wfSession.newWorkflowData(\"JCR_PATH\", payloadPath);\n\n            \u002F\u002F Set initial metadata\n            MetaDataMap meta = data.getMetaDataMap();\n            if (initialMeta != null) {\n                initialMeta.forEach(meta::put);\n            }\n\n            Workflow instance = wfSession.startWorkflow(model, data);\n            return instance.getId();\n        }\n    }\n}\n```\n\n**Model ID format:** `\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow` (the runtime path, not the design-time path)\n\n## 4. HTTP Workflow API\n\n```bash\n# Start a workflow\ncurl -u admin:admin -X POST \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances\" \\\n  -d \"model=\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow\" \\\n  -d \"payloadType=JCR_PATH\" \\\n  -d \"payload=\u002Fcontent\u002Fmy-site\u002Fen\u002Fhome\" \\\n  -d \"workflowTitle=Review Request from CI\"\n\n# Response: 201 Created with Location header pointing to instance path\n\n# Get workflow instance details\ncurl -u admin:admin \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances\u002F\u003CinstanceId>.json\"\n\n# List running instances\ncurl -u admin:admin \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances?state=RUNNING&model=\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow\"\n```\n\n## Guardrails\n\n- Always specify a `workflowTitle` when starting programmatically — it helps operators identify instances in the console.\n- Never start workflows with admin credentials from production code. Use a service user.\n- Model ID must be the `\u002Fvar\u002Fworkflow\u002Fmodels\u002F` path (runtime). Do not use the `\u002Fconf` design-time path.\n- Check that the model is synced to `\u002Fvar\u002Fworkflow\u002Fmodels\u002F` before calling `startWorkflow()`.\n\n## References\n\n- [triggering-mechanisms.md](.\u002Freferences\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md) — detailed guide for each mechanism\n- [programmatic-api.md](.\u002Freferences\u002Fworkflow-triggering\u002Fprogrammatic-api.md) — WorkflowSession API patterns and service user setup\n- [api-reference.md](.\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md)\n- [jcr-paths-reference.md](.\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md)\n- [cloud-service-guardrails.md](.\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md)\n","# Workflow Triggering (Cloud Service)\n\nAll mechanisms to start a workflow on AEM Cloud Service — from UI, programmatic API, HTTP API, and Manage Publication.\n\n## Variant Scope\n\n- AEM Cloud Service only.\n- Use service users with `workflow-process-service` sub-service mapping for programmatic triggering.\n\n## Triggering Mechanisms Summary\n\n| Mechanism | Use Case |\n|---|---|\n| **Timeline UI** | One-off manual start on a single page or asset |\n| **Manage Publication** | Multi-page batch start, integrates with publish pipeline |\n| **WorkflowSession API** | Backend Java code, scheduled jobs, event handlers |\n| **HTTP Workflow API** | REST calls, scripts, external integrations |\n| **Workflow Launchers** | Automatic on JCR events — see `workflow-launchers` skill |\n\n## 1. Manual via Timeline UI\n\n1. Navigate to a page or asset in Sites\u002FAssets console\n2. Open **Timeline** panel (clock icon)\n3. Click **Start Workflow**\n4. Select the model from the dropdown\n5. Optionally enter a workflow title and comment\n6. Click **Start**\n\nThe workflow starts with the selected item as `JCR_PATH` payload and the current user as initiator.\n\n## 2. Manage Publication (Multi-Page)\n\n1. Sites Console → select pages → **Manage Publication**\n2. Choose action (Publish \u002F Unpublish)\n3. Check **Include Workflow**\n4. Select workflow model\n5. Click **Publish Later** or **Publish Now**\n\nAEM creates a `cq:WorkflowContentPackage` containing all selected pages as the workflow payload.\n\n## 3. Programmatic (WorkflowSession API)\n\n```java\n@Component(service = MyWorkflowService.class)\npublic class MyWorkflowService {\n\n    @Reference\n    private ResourceResolverFactory resolverFactory;\n\n    public String startWorkflow(String payloadPath, String modelId,\n                                Map\u003CString, Object> initialMeta) throws Exception {\n        Map\u003CString, Object> auth = Collections.singletonMap(\n            ResourceResolverFactory.SUBSERVICE, \"workflow-process\");\n        try (ResourceResolver resolver = resolverFactory.getServiceResourceResolver(auth)) {\n            WorkflowSession wfSession = resolver.adaptTo(WorkflowSession.class);\n            WorkflowModel model = wfSession.getModel(modelId);\n            WorkflowData data = wfSession.newWorkflowData(\"JCR_PATH\", payloadPath);\n\n            \u002F\u002F Set initial metadata\n            MetaDataMap meta = data.getMetaDataMap();\n            if (initialMeta != null) {\n                initialMeta.forEach(meta::put);\n            }\n\n            Workflow instance = wfSession.startWorkflow(model, data);\n            return instance.getId();\n        }\n    }\n}\n```\n\n**Model ID format:** `\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow` (the runtime path, not the design-time path)\n\n## 4. HTTP Workflow API\n\n```bash\n# Start a workflow\ncurl -u admin:admin -X POST \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances\" \\\n  -d \"model=\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow\" \\\n  -d \"payloadType=JCR_PATH\" \\\n  -d \"payload=\u002Fcontent\u002Fmy-site\u002Fen\u002Fhome\" \\\n  -d \"workflowTitle=Review Request from CI\"\n\n# Response: 201 Created with Location header pointing to instance path\n\n# Get workflow instance details\ncurl -u admin:admin \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances\u002F\u003CinstanceId>.json\"\n\n# List running instances\ncurl -u admin:admin \\\n  \"http:\u002F\u002Flocalhost:4502\u002Fapi\u002Fworkflow\u002Finstances?state=RUNNING&model=\u002Fvar\u002Fworkflow\u002Fmodels\u002Fmy-workflow\"\n```\n\n## Guardrails\n\n- Always specify a `workflowTitle` when starting programmatically — it helps operators identify instances in the console.\n- Never start workflows with admin credentials from production code. Use a service user.\n- Model ID must be the `\u002Fvar\u002Fworkflow\u002Fmodels\u002F` path (runtime). Do not use the `\u002Fconf` design-time path.\n- Check that the model is synced to `\u002Fvar\u002Fworkflow\u002Fmodels\u002F` before calling `startWorkflow()`.\n\n## References\n\n- [triggering-mechanisms.md](.\u002Freferences\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md) — detailed guide for each mechanism\n- [programmatic-api.md](.\u002Freferences\u002Fworkflow-triggering\u002Fprogrammatic-api.md) — WorkflowSession API patterns and service user setup\n- [api-reference.md](.\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md)\n- [jcr-paths-reference.md](.\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md)\n- [cloud-service-guardrails.md](.\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md)\n",{"name":5,"license":15,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-aem-workflow\u002Fworkflow-triggering","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill workflow-triggering",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill workflow-triggering",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill workflow-triggering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002FSKILL.md",true,[46,52,56,60,64,68,72,76],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fworkflow-foundation\u002Fapi-reference.md","REFERENCE","参考文档",3606,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fworkflow-foundation\u002Farchitecture-overview.md",2363,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002Farchitecture-overview.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md",2724,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fworkflow-foundation\u002Fjcr-paths-reference.md",2481,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fworkflow-foundation\u002Fquick-start-guide.md",2038,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002Fquick-start-guide.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fworkflow-foundation\u002FREADME.md",826,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-foundation\u002FREADME.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fworkflow-triggering\u002Fprogrammatic-api.md",5275,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Fprogrammatic-api.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md",4710,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]