integration-patterns-skill

To enforce type safety for Nango actions and syncs, apply inline schemas, ensure null-safe optional fields, and avoid default values in schemas. These patterns guarantee strict validation and prevent runtime type mismatches.

The best coding standards for Nango integration patterns involve explicit parameter naming, mandatory index.ts imports, and static endpoint documentation. Following these registration patterns ensures integrations are reliable, type-safe, and easily maintainable.

To document API endpoints and parameter naming for Nango syncs, use static endpoint guidance and explicit parameter naming conventions. This practice ensures API endpoints are clearly documented and parameter mappings remain transparent during code reviews.

Yes, this integration patterns guidance applies to code reviews of existing Nango actions. It evaluates existing syncs against requirements like inline schemas, null-safe optional fields, and mandatory index.ts imports to ensure robust integration quality.

You should use inline schemas instead of default values in Nango integrations to maintain strict type safety and predictable parameter behavior. Avoiding default values in schemas prevents silent data masking and ensures explicit parameter registration.