ffcpe-custom-node-sdk

Wire FFCPE custom actions with async submit and status endpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about ffcpe-custom-node-sdk

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

FAQPage Schema
How do I build an Adobe App Builder custom action for Workflow Builder?

To build an Adobe App Builder custom action for Workflow Builder, implement paired web and worker actions, wire them using `mountFfcpeNodeRoutes`, and set the `submitEndpoint` and `statusEndpoint` in the action's `entry.json` file.

How does asynchronous status polling work with FFCPE custom actions?

Asynchronous status polling in FFCPE custom actions works by separating job submission from status checks. The web action exposes `/submit` and `/status` HTTP endpoints, allowing Workflow Builder to poll job lifecycle states until they reach `completed` or `failed`.

Do I need Adobe IMS authentication for App Builder custom actions?

Yes, Adobe IMS authentication is required for App Builder custom actions. The SDK provides IMS-aware route configuration to ensure secure job orchestration and proper access control when connecting OpenWhisk routes to worker jobs.

What is the best way to map typed inputs and outputs in FFCPE worker jobs?

The best way to map typed inputs and outputs in FFCPE worker jobs is using the SDK's typed helper functions. Validate FFCPE inputs like Text, Image, Video, or Json, map them to worker logic, and produce action outputs with dedicated output creators.

Why does my FFCPE custom action fail to progress in Workflow Builder?

FFCPE custom actions fail to progress in Workflow Builder if the submit/status contract is mismatched. Ensure catalog endpoints, status polling behavior, and job lifecycle states align, and verify `mountFfcpeNodeRoutes` includes the required `web` routing target.

Can I use OpenWhisk and Hono to wire FFCPE custom node routes?

Yes, you can use OpenWhisk and Hono to wire FFCPE custom node routes. The SDK specifically supports custom-action implementations using `mountFfcpeNodeRoutes` web route wiring with OpenWhisk/Hono to connect web actions to long-running worker jobs.