yida-connector

Create, configure, and test HTTP connectors for Yida with six authentication methods.

201|43|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/openyida/openyida --skill yida-connector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yida-connector
Source: https://github.com/openyida/openyida/tree/main/yida-skills/skills/yida-connector
Command: npx skills add https://github.com/openyida/openyida --skill yida-connector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

宜搭 HTTP 连接器管理,帮助用户创建、配置和测试连接器,打通钉钉、自建系统和第三方 API,提升对外系统的互操作性。

Core Features & Use Cases

  • 创建、配置与测试连接器,支持多种鉴权方式
  • 将连接器ID记录到本地缓存,便于后续跟踪与使用
  • 适用于对外接口集成、钉钉开放平台接入、内部系统对接的场景
  • Use Case: 需要连接外部 API 时,快速创建并验证连接器的连通性

Quick Start

创建一个新的 HTTP 连接器并测试其连通性。

Frequently Asked Questions about yida-connector

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

FAQPage Schema
How do I create an HTTP connector for DingTalk APIs in Yida?

Creating an HTTP connector for DingTalk APIs involves configuring endpoint details, selecting one of six authentication methods, and testing connectivity. The system securely handles credentials and caches the connector ID locally for future use.

What authentication methods can I use for Yida HTTP connectors?

Yida HTTP connectors support six distinct authentication methods to accommodate various API security requirements. This multi-method approach allows integration with DingTalk, internal systems, and external APIs that enforce different credential validation mechanisms.

Does Yida support testing external API connectivity before finalizing a connector?

Yida supports testing external API connectivity during connector creation. You can verify endpoint configurations, authentication credentials, and request parameters before finalizing the connector for production use.

Can I use HTTP connectors to integrate internal systems with the Yida platform?

You can use HTTP connectors to integrate internal systems with the Yida platform. They are designed for scenarios requiring connection to external APIs, the DingTalk open platform, or internal corporate systems to improve interoperability.

Why does Yida cache the connector ID after creating an HTTP connector?

Yida caches the connector ID after creation to maintain a local record for subsequent tracking and usage. This ensures the configured connector can be quickly referenced and invoked within later automated workflows.