action-builder-skill

Creating a Nango action with consistent TypeScript patterns involves using a standardized blueprint for thin API wrappers that enforces a clean createAction() structure with inline schemas, deterministic proxy calls, and explicit parameter naming.

A correct Nango createAction integration structure requires a description, version, endpoint, input/output, and scopes. It must use inline schemas without .default(), implement mandatory retries, and be registered in index.ts.

No, you cannot use inline schemas with default values in Nango createSync. The pattern enforces inline schemas without .default() to ensure strict type safety and predictable behavior across your API wrappers.

The best way to refactor API endpoints into Nango actions is applying a thin API wrapper blueprint that minimizes boilerplate, enforces consistent data transformation, and standardizes error handling and deterministic proxy calls.

Nango integration actions fail pattern consistency checks when they lack mandatory retries, omit index.ts registration, or use inline schemas with .default() instead of explicit parameter naming and deterministic proxy calls.