Catalog entry JSON (catalog-entry.json)

Use this skill to author, review, or fix a JSON document that registers an App Builder action with the run-workflow catalog so it can be used in workflows. For every catalog operation (list, register, inspect, …), use the aio ffcpe catalog commands from @adobe/aio-cli-plugin-ffcpe—do not suggest curl or ad-hoc HTTP clients.

File naming and placement (App Builder projects)

Best practice: one catalog entry file per custom action, named <action-name>.entry.json, in the same directory as that action’s web and worker sources:

actions/<action-name>/
  <action-name>.web.ts
  <action-name>.worker.ts
  <action-name>.entry.json

• <action-name> should match the OpenWhisk action basename and your mountFfcpeNodeRoutes / manifest naming where practical.
• The file content is the full catalog payload (handlerType: "custom-action", inputs / outputs, customActionConfig, discovery fields)—not a stub or pointer file.
• Pass this path to aio ffcpe catalog validate --file … and register --file …. A repo-root catalog-entry.json is fine for one-off samples; prefer <action-name>.entry.json co-located when the app has multiple actions.