# Gadgets and integrations

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

A Gadget is a Sydekyks integration. It provides an app’s supported actions, triggers or both. Use it to move information between tools without recreating the same steps by hand.

Search the Gadget catalog (https://www.sydekyks.com/#integrations) to find apps by name or category. The website catalog is generated from the checked-in integration source, dated 7 October 2026. It is a source catalog, not a list of apps already connected to your account or tested in your deployment.

## ​Gadget, action and Connected Account

 | Term | What it gives you

 | Gadget | The integration with an app or a built-in workflow tool

 | Action | One supported operation, such as creating a record or sending a message

 | Trigger | A supported event that can start a mission

 | Connected Account | The credentials and permissions used to access the app

A Gadget may have actions without a trigger. Exact steps depend on the Gadget version installed for your deployment. Check the step picker in your workspace and ask us if your needed action is missing.

## ​Check your apps before setup

Tell us which apps, versions and tasks you use. We confirm the integration and the access needed for your workflow. An app may require a provider subscription, API access, an administrator’s permission or its own OAuth configuration. AI Gadgets require a configured AI provider and can incur separate provider usage costs.

For example, seeing Odoo, Microsoft Outlook or HubSpot in the catalog does not mean your account is connected. Use the Connected Accounts guide (https://docs.sydekyks.com/getting-started/connections) after your deployment and provider setup are ready.

If your app is missing, discuss it with us (https://www.sydekyks.com/#conversation). An existing API may make a custom connection possible; we confirm the scope before promising support.

## ​Technical names

Developer references retain piece, @activepieces/pieces-framework and related package and API identifiers. These are compatibility names beneath the Sydekyks product language. They do not require a vendor cloud account.

App names identify their respective products and do not imply endorsement of Sydekyks.