pluggy-integration
Core Pluggy integration patterns and best practices. Use when setting up Pluggy SDK, implementing Connect Widget, managing Items, or configuring webhooks.
Works with
--- name: pluggy-integration description: Core Pluggy integration patterns and best practices. Use when setting up Pluggy SDK, implementing Connect Widget, managing Items, or configuring webhooks. license: MIT --- # Pluggy Integration Comprehensive integration guide for Pluggy Open Finance API. Contains rules across 5 categories, prioritized by impact to guide accurate implementation. ## When to Apply Reference these guidelines when: - Setting up Pluggy SDK and authentication - Implementing the Connect Widget in frontend applications - Creating, updating, or managing Items (connections) - Handling MFA (Multi-Factor Authentication) flows - Configuring webhooks for real-time data sync - Managing API keys and tokens - Handling connection errors and edge cases ## Rule Categories by Priority | Priority | Category | Impact | Prefix | | -------- | ---------------------- | -------- | --------- | | 1 | Authentication | CRITICAL | `auth-` | | 2 | Connect Widget | CRITICAL | `widget-` | | 3 | Webhook Configuration | CRITICAL | `webhook-`| | 4 | Item Lifecycle | HIGH | `item-` | | 5 | Error Handling | MEDIUM | `error-` | ## How to Use Read individual rule files for detailed explanations and code examples: ``` rules/auth-api-keys.md rules/widget-integration.md rules/item-lifecycle.md ``` Each rule file contains: - Brief explanation of why it matters - Incorrect code example with explanation - Correct code example with explanation - Additional context and references - Pluggy-specific notes ## Key Concepts ### Connection Sync vs Data Sync | Responsibility | Who Handles | How | | -------------- | ----------- | --- | | Connection sync | **Pluggy** | Auto-sync every 24/12/8h | | Triggering updates | **User** | Only when user explicitly requests | | Entity data sync | **You** | Fetch all on `item/updated` webhook | | Transaction sync | **You** | Use `transactions/*` webhook events | ### API Key vs Connect Token - **API Key**: Backend token (2h expiration) for accessing user data - **Connect Token**: Frontend token (30min expiration) for Connect Widget only ### Item Lifecycle 1. User opens Connect Widget with Connect Token 2. User selects connector and authenticates 3. Pluggy creates Item and starts data sync 4. Webhook notifies when sync completes 5. Backend retrieves data using API Key 6. Pluggy auto-syncs daily; webhook triggers data refresh ## Full Compiled Document For the complete guide with all rules expanded: `AGENTS.md`
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

