What problem does it solve?
Wiring FFCPE custom actions in Adobe App Builder is error-prone because it requires a correct async submit/status HTTP contract, matching worker inputs/outputs, and IMS-aware route configuration across multiple packages.
Core Features & Use Cases
- End-to-end custom-action wiring guidance: Use the SDK with
mountFfcpeNodeRoutes and createFfcpeNodeWorker to connect web (OpenWhisk) routes to long-running worker jobs.
- Correct submit/status contract for Workflow Builder: Ensure catalog endpoints, status polling behavior, and job lifecycle states align so workflows progress to
completed or failed.
- Typed inputs/outputs helpers: Validate and map FFCPE inputs (Text/Image/Video/Json) to worker logic and produce action outputs using the SDK’s output creators.
Quick Start
Implement the web and worker actions for your custom action pair, wire them using mountFfcpeNodeRoutes (with the required web target), deploy the App Builder app, then set your action’s submitEndpoint and statusEndpoint in the <action-name>.entry.json to the deployed /submit and /status URLs.