Skip to main content
skill CX Codex

pluggy-integration — Claude Code skill: what it does, how to install

Integrates Pluggy Open Finance API patterns. It guides authentication, Connect Widget configuration, webhook event handling, and connection lifecycle.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pluggyai/agent-skills --skill pluggy-integration -a claude-code
Open on GitHub

What pluggy-integration does

The skill provides implementation rules for Pluggy Open Finance API categorized by impact. Critical levels focus on authentication (auth-) and Connect Widget integration (widget-). Further sections regulate webhook configuration (webhook-), connection lifecycle (item-), and error handling (error-).

It defines clear boundaries between connection and data sync. Pluggy automatically refreshes provider connections every 8, 12, or 24 hours. Your backend handles the actual data ingestion by listening to item/updated or transactions/* webhook events.

Authentication enforces strict separation between client and server credentials. The frontend Connect Token expires after 30 minutes and only serves the widget. Sending the backend API Key to client apps breaks integration security, as it holds broader user data access with a 2-hour lifetime.

What it helps with

  • embed Connect Widget into client applications
  • configure webhook listeners for transaction sync
  • separate API Key from short-lived Connect Token logic
  • handle multi-factor authentication (MFA) challenges

Example prompts for the agent

  • Configure the frontend Connect Widget using a Connect Token
  • Write a backend webhook handler for item/updated events
  • Show the correct flow for handling MFA challenges during connection

How to install pluggy-integration

1Skills CLI (Vercel)

npx skills add pluggyai/agent-skills --skill pluggy-integration -a claude-code

2Manually: put the files in place

~/.claude/skills/pluggy-integration/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pluggy-integration/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about pluggy-integration

How to install pluggy-integration in Claude Code?

Run npx skills add pluggyai/agent-skills --skill pluggy-integration -a claude-code in your terminal. The rule definitions will be stored in ~/.claude/skills/pluggy-integration/SKILL.md.

What does pluggy-integration do?

It guides code assistants through Pluggy Open Finance implementations using structured rule files. Each rule includes positive and negative examples for token management, widget mounting, and sync flows.

How do API Key and Connect Token differ in Pluggy?

A Connect Token is a frontend credential that expires in 30 minutes, used only by the Connect Widget. The API Key belongs on the backend, expires in 2 hours, and queries user account records.

Source text

SKILL.md · MIT
---
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
metadata:
  author: pluggy
  version: "1.0.0"
---

# 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`

© pluggy · MIT · pluggyai/agent-skills

Similar skills

All skills for Finance and business →

From the same set4

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor