AI integrations for Core: capabilities and checks

Explore core integrations

This directory contains 29 application entries from the Activepieces public-card snapshot observed on 30 October 2026. It helps you shortlist a system before designing a connection. An entry describes an upstream catalog listing; it does not certify a working Tvijo connection, current account permissions, product licensing or successful execution.

The counts below are calculated from the extracted action and trigger lists. They are historical source observations. Follow the individual source card to check changes. A trigger describes an event that can start a workflow; it is not necessarily an MCP callable action. Parameter names and types were absent from this card dataset, so these numbers cannot be used to generate executable tool schemas.

Application directory

Make a shortlist useful

1. Write the business question and the smallest dataset required. Use synthetic examples for the first test.
2. Check the original vendor's API and authentication documentation. Identify who owns the account and the permission scope.
3. Obtain an actual MCP tool list and input schemas from a configured server. Review each selected action; a label such as Get or List alone does not prove read-only behavior.
4. Check missing-permission handling, result limits, credential isolation and data visibility. Keep writes disabled until their approval and idempotency behavior have been tested.
5. Store the source version, setup version, test input and observed result. Advance readiness only for the connection and scope that actually passed.

Exercise: choose two applications from this list and prepare a one-page comparison: task, input data, source URL, authentication, known limits, missing evidence and the next safe test. You can use this method independently of Tvijo.

Acceptance: another person can reproduce your source check and distinguish a catalog entry from a configured, protocol-tested, sandbox-tested or production-enabled connection. No real credentials belong in that comparison.

Understand the limits

The upstream related-app list primarily groups apps by category; it does not establish a data flow or functional dependency. Missing categories remain explicit rather than being guessed. The source's generic license label is an observation about the card, not an independent legal assessment of the vendor or every component. No vendor account has been connected by this publication.

Explore the MCP learning and integration section and AI process learning section. For evidence-based learning, see from knowledge to practice. These guides explain how a potential Tvijo workflow becomes a tested capability without turning catalog presence into a product promise.