# Build an integration

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

A gadget supplies actions, triggers and authentication for an app or service. In source code and package names, the framework calls it a piece.

## ​Start with a matching release

First choose the development source (https://docs.sydekyks.com/build-pieces/building-pieces/setup-fork), then follow the development setup (https://docs.sydekyks.com/build-pieces/building-pieces/development-setup). Use the SDK and lockfile from the supported release instead of mixing an arbitrary upstream revision with a deployed fork.

Choose a small action or trigger, implement it, and test its inputs, output, authentication and error handling. Start with create an action (https://docs.sydekyks.com/build-pieces/building-pieces/create-action) or create a trigger (https://docs.sydekyks.com/build-pieces/building-pieces/create-trigger). The AI-assisted workflow (https://docs.sydekyks.com/build-pieces/building-pieces/build-with-ai) is an optional development aid; review and verify the resulting code.

## ​Distribution

Public npm distribution (https://docs.sydekyks.com/build-pieces/sharing-pieces/community), upstream contribution (https://docs.sydekyks.com/build-pieces/sharing-pieces/contribute) and a source-built Sydekyks bundle are distinct paths. Confirm the supported installation path on the target deployment before publishing a package.

## ​Support

Use the support route supplied for your deployment. Include the supported source revision, package name/version, a reproducible test case and redacted error details. The guide does not establish a Sydekyks Discord community or a response-time promise.