action-builder-skill

Name: action-builder-skill
Availability: InStock
Author: Nango

Automate creation and refactoring of Nango integration actions in TypeScript projects.

45|32|Updated Sep 23, 2024

Search Tags:#typescript #integration #patterns #nango #proxy #action-builder

Ready to run

npx skills add https://github.com/NangoHQ/integration-templates --skill action-builder-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: action-builder-skill
Source: https://github.com/NangoHQ/integration-templates/tree/main/.claude/skills/action-builder-skill
Command: npx skills add https://github.com/NangoHQ/integration-templates --skill action-builder-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating or refactoring Nango integration actions can lead to inconsistent wrappers, duplicated logic, and maintenance pain. This skill provides a standardized blueprint for thin API wrappers that promotes reusable patterns and predictable behavior.

Core Features & Use Cases

Enforces a clean createAction() structure (description, version, endpoint, input/output, scopes) with inline schemas.
Provides guidance for deterministic proxy calls, error handling, and consistent data transformation.
Use Case: Quickly add or refactor an API endpoint into a reusable Nango action with minimal boilerplate and strong type safety.

Quick Start

Create a new action using a small, well-scoped proxy following the integration-patterns-skill guidelines.

Frequently Asked Questions about action-builder-skill

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

FAQPage Schema

How do I create a Nango action with consistent TypeScript patterns?▼

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.

What is the correct structure for a Nango createAction integration?▼

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.

Can I use inline schemas with default values in Nango createSync?▼

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.

What's the best way to refactor API endpoints into Nango actions?▼

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.

Why does my Nango integration action fail pattern consistency checks?▼

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.