new-integration

Scaffold Fuse integrations with OAuth 2.0 or API key credential providers.

1|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill new-integration-bibektimilsina00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-integration
Source: https://github.com/bibektimilsina00/fuse_monorepo/tree/main/.agents/skills/new-integration
Command: npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill new-integration-bibektimilsina00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the end-to-end setup of a new external service integration by scaffolding credentials, API clients, service methods, loadOptions endpoints, and frontend wiring so you can launch nodes faster with consistent patterns.

Core Features & Use Cases

  • Scaffold OAuth 2.0 integrations: Generate an OAuth provider, register it in the OAuth provider registry, add required env vars, and implement the token exchange flow following the existing provider pattern.
  • Scaffold API key integrations: Add a provider with the right credential field(s) so nodes can automatically consume the key.
  • Expose integration operations via loadOptions: Create FastAPI endpoints that back the frontend dropdown inspector flows, mapping results into UI-friendly label/value pairs.
  • Wire nodes to use dynamic data: Add loadOptions and dependsOn so credential-dependent fields can populate from the integration’s endpoints.

Quick Start

Ask the skill to scaffold an integration named Stripe using OAuth, provide its icon URL, API base URL, key operations needed for dropdowns, and its OAuth environment variable names and endpoints.

Frequently Asked Questions about new-integration

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

FAQPage Schema
How do I scaffold an OAuth 2.0 integration for a new third-party service?

Scaffolding an OAuth 2.0 integration generates an OAuth provider, registers it in the provider registry, adds required environment variables, and implements the token exchange flow. You provide the service name, icon, API base URL, and OAuth endpoints to launch nodes faster with consistent patterns.

How do I create FastAPI endpoints for frontend dropdown loadOptions?

Creating FastAPI endpoints for loadOptions backs frontend dropdown inspector flows by mapping API results into UI-friendly label/value pairs. You expose endpoint paths that match the node loadOptions configuration to populate dynamic inspector dropdowns based on integration operations.

Can I use API key credential management for new third-party service integrations?

API key credential management supports new integrations by adding a provider with the correct credential fields. Nodes automatically consume the API key to authenticate requests, streamlining end-to-end setup of external service connections.

How do I wire frontend nodes to use dynamic data from credential-dependent fields?

Wiring frontend nodes to use dynamic data involves adding loadOptions and dependsOn properties to credential-dependent fields. This populates field options from the integration's FastAPI endpoints, ensuring dropdowns respect credential selection.

What is needed to scaffold secure AI integrations with dynamic inspector dropdowns?

Scaffolding secure AI integrations requires generating credential providers, HTTP client and service layers using httpx, FastAPI loadOptions endpoints, and frontend node wiring. It applies to OAuth 2.0 or API key integrations for new third-party services.

Does scaffolding a new integration require following existing repository patterns?

Scaffolding a new integration requires following the repository's existing credential manager and integrations router patterns. Providers must be registered consistently, and exposed endpoint paths must match the node loadOptions configuration to maintain structural integrity.