@tangle-network/agent-integrations 0.9.0 → 0.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +25 -0
- package/data/activepieces-catalog.json +40907 -0
- package/dist/index.d.ts +148 -2
- package/dist/index.js +4876 -4245
- package/dist/index.js.map +1 -1
- package/docs/catalog-registry.md +59 -0
- package/docs/integration-coverage-checklist.md +3 -1
- package/docs/third-party/activepieces.md +57 -0
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -15,6 +15,7 @@ agent-facing tool contract.
|
|
|
15
15
|
- [Architecture](#architecture)
|
|
16
16
|
- [Install](#install)
|
|
17
17
|
- [Core Primitives](#core-primitives)
|
|
18
|
+
- [Catalog Registry](#catalog-registry)
|
|
18
19
|
- [Provider Strategy](#provider-strategy)
|
|
19
20
|
- [Executable Coverage](#executable-coverage)
|
|
20
21
|
- [Examples](#examples)
|
|
@@ -31,10 +32,14 @@ agent-facing tool contract.
|
|
|
31
32
|
- Policy checks for read/write/destructive actions.
|
|
32
33
|
- Invocation-envelope validation before sandbox tool calls reach the hub.
|
|
33
34
|
- A generic HTTP provider boundary for hosted integration gateways.
|
|
35
|
+
- A gateway catalog provider for Nango, Pipedream, Activepieces, Zapier,
|
|
36
|
+
executor-style gateways, and internal connector registries.
|
|
34
37
|
- A first-party `ConnectorAdapter` boundary for direct provider execution.
|
|
35
38
|
- A declarative REST adapter factory for promoting REST APIs from reviewed specs.
|
|
36
39
|
- A broad coverage catalog for planning hundreds of integrations without
|
|
37
40
|
pretending every catalog item is executable.
|
|
41
|
+
- A canonical registry that deduplicates overlapping catalogs, keeps support
|
|
42
|
+
tiers explicit, and reports auth/category conflicts.
|
|
38
43
|
- A generated `IntegrationSpec` registry used for setup docs, admin UI steps,
|
|
39
44
|
normalized permissions, healthcheck plans, and tool descriptions.
|
|
40
45
|
|
|
@@ -74,7 +79,10 @@ pnpm add @tangle-network/agent-integrations
|
|
|
74
79
|
| `IntegrationCapability` | Short-lived authorization for a specific subject, connection, scope set, and action set. |
|
|
75
80
|
| `buildIntegrationToolCatalog` | Converts connector actions into agent/tool definitions. |
|
|
76
81
|
| `searchIntegrationTools` | Intent search over normalized integration tools. |
|
|
82
|
+
| `buildDefaultIntegrationRegistry` | Composes setup specs and vendored catalog metadata into one deduplicated connector registry. |
|
|
83
|
+
| `composeIntegrationRegistry` | Merges arbitrary catalog sources with explicit aliases, precedence, support tiers, and conflict diagnostics. |
|
|
77
84
|
| `buildIntegrationCoverageConnectors` | Planning catalog for 100+ high-value integrations. |
|
|
85
|
+
| `createGatewayCatalogProvider` | Normalizes 500+ gateway-backed connectors into the same provider contract. |
|
|
78
86
|
| `buildIntegrationInvocationEnvelope` | Sandbox-safe action envelope. |
|
|
79
87
|
| `validateIntegrationInvocationEnvelope` | Runtime validation for tool/action consistency and input limits. |
|
|
80
88
|
| `createHttpIntegrationProvider` | Adapter for hosted integration gateways. |
|
|
@@ -84,6 +92,23 @@ pnpm add @tangle-network/agent-integrations
|
|
|
84
92
|
| `renderRunbookMarkdown` / `renderConsoleSteps` | Render operator docs or admin UI steps from the same spec source. |
|
|
85
93
|
| `validateCredentialSet` / `buildHealthcheckPlan` | Validate setup input and describe the correct healthcheck path. |
|
|
86
94
|
|
|
95
|
+
## Catalog Registry
|
|
96
|
+
|
|
97
|
+
Catalog breadth and runtime execution are separate. Activepieces metadata gives
|
|
98
|
+
the package broad connector inventory; first-party adapters and gateways decide
|
|
99
|
+
which connectors can actually run.
|
|
100
|
+
|
|
101
|
+
Use `buildDefaultIntegrationRegistry()` before creating tool catalogs or
|
|
102
|
+
connection pickers. It produces one canonical connector per integration,
|
|
103
|
+
dedupes aliases such as `notion -> notion-database`, keeps source provenance in
|
|
104
|
+
metadata, and marks each connector with a support tier:
|
|
105
|
+
|
|
106
|
+
```txt
|
|
107
|
+
catalogOnly < setupReady < gatewayExecutable < firstPartyExecutable < sandboxExecutable
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
See [Catalog Registry](./docs/catalog-registry.md).
|
|
111
|
+
|
|
87
112
|
## Provider Strategy
|
|
88
113
|
|
|
89
114
|
The package deliberately avoids vendor lock-in.
|