Chess.com

Overview

Connect Chess.com with Flows360

Access Chess.com player data

Use the Chess.com connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 3 actions and no declared triggers.

Available actions

• Get Player Profile
• Get Player Stats
• Get Daily Puzzle

Available triggers

• No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: Chess.com
• Package: @activepieces/piece-chess-com@0.0.6
• Exact artifact digest: sha256:8e2d55b5d3ccd8b06bdc159302b3c0be866614b1138cd5fc54cd2b5772e8de04
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Get Player Profile (get_player_profile), Retrieve a Chess.com player's public profile by username (avatar, country, join date, followers). Classification: read.
• Get Player Stats (get_player_stats), Retrieve a Chess.com player's ratings and W/D/L for rapid, blitz, bullet, and chess960. Classification: read.
• Get Daily Puzzle (get_daily_puzzle), Retrieve today's Chess.com daily puzzle. Classification: read.

Trigger contracts

• No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authentication

Authentication method: No authentication required

Supported objects

Supported actions

Setup

Setup

1. Add the Chess.com connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• No provider credential fields are declared by the pinned package.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-chess-com@0.0.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 3 actions and 0 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Related documentation