ffcpe-app-builder-actions

Implement FFCPE custom-action web and worker OpenWhisk actions for App Builder.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/adobe/ffcpe-custom-node-sdk --skill ffcpe-app-builder-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ffcpe-app-builder-actions
Source: https://github.com/adobe/ffcpe-custom-node-sdk/tree/main/skills/ffcpe-app-builder-actions
Command: npx skills add https://github.com/adobe/ffcpe-custom-node-sdk --skill ffcpe-app-builder-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement and troubleshoot Adobe App Builder (OpenWhisk) custom actions for FFCPE by providing a consistent wiring pattern for the Hono web endpoint and the asynchronous worker that performs the job.

Core Features & Use Cases

  • Web + Worker pairing: Mounts FFCPE submit/status routes in a Hono web action and connects them to a corresponding worker action.
  • OpenWhisk runtimeManifest guidance: Shows how to declare raw web actions and disable default auth requirements where required.
  • Worker contract implementation: Guides you to implement FfcpeNodeWorkerHandler, return completed/failed statuses, and produce FFCPE output types (text/image/video/json).
  • Catalog registration workflow: Supports the post-deploy steps to validate and register co-located <action-name>.entry.json with aio ffcpe catalog.
  • Scaffolding/migration fixes: Helps when migrating or scaffolding projects (including init-bare cleanup) by correcting app.config.yaml and bundling output to CommonJS.

Quick Start

Use this skill to scaffold an Adobe App Builder custom action pair for one FFCPE node by following the web Hono mounting steps, implementing the worker handler, updating runtimeManifest, deploying, then validating and registering the co-located action entry JSON.

Frequently Asked Questions about ffcpe-app-builder-actions

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

FAQPage Schema
How do I wire a Hono web action to an OpenWhisk worker for Adobe App Builder?

To wire a Hono web action to an OpenWhisk worker, mount FFCPE submit/status routes using the `mountFfcpeNodeRoutes` adapter in your web action and implement a corresponding worker handler that returns completed or failed job statuses.

What should an FFCPE worker handler return for async job processing?

An FFCPE worker handler must return a completed or failed status contract containing typed outputs like text, image, video, or json to properly report asynchronous job results back to the App Builder web action.

How do I configure the runtimeManifest for raw OpenWhisk web actions?

Configure the runtimeManifest by setting web to "raw" for your OpenWhisk actions and adjusting the require-adobe-auth behavior, ensuring the deployment aligns with FFCPE custom node routing requirements.

Why does my App Builder custom action fail after migrating to CommonJS?

App Builder custom actions fail after migration if the bundling output is not configured for CommonJS or if `app.config.yaml` retains invalid settings, preventing the dist deployment from executing the OpenWhisk action correctly.

How do I register an FFCPE custom action in the catalog after deploying?

To register an FFCPE custom action after deployment, validate the co-located `<action-name>.entry.json` file and execute the `aio ffcpe catalog` command to complete the workflow builder registration process.

Do I need @adobe/ffcpe-custom-node-core to build FFCPE custom actions?

Yes, building FFCPE custom actions requires @adobe/ffcpe-custom-node-core and @adobe/ffcpe-custom-node-app-builder to properly scaffold the Hono web and worker OpenWhisk actions for async job submission and status reporting.