@tangle-network/agent-integrations 0.9.0 → 0.14.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 +73 -0
- package/data/activepieces-catalog.json +40907 -0
- package/dist/index.d.ts +344 -2
- package/dist/index.js +5181 -4243
- 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
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
# Catalog Registry
|
|
2
|
+
|
|
3
|
+
`agent-integrations` can ingest several catalog sources:
|
|
4
|
+
|
|
5
|
+
- first-party adapters
|
|
6
|
+
- generated setup specs
|
|
7
|
+
- gateway catalogs
|
|
8
|
+
- vendored Activepieces metadata
|
|
9
|
+
- planning coverage stubs
|
|
10
|
+
|
|
11
|
+
Those sources intentionally overlap. The public product surface should not.
|
|
12
|
+
Use `composeIntegrationRegistry()` or `buildDefaultIntegrationRegistry()` before
|
|
13
|
+
building agent tools, connection pickers, setup flows, or planning context.
|
|
14
|
+
|
|
15
|
+
## Support Tiers
|
|
16
|
+
|
|
17
|
+
The registry assigns one tier per canonical connector:
|
|
18
|
+
|
|
19
|
+
| Tier | Meaning |
|
|
20
|
+
| --- | --- |
|
|
21
|
+
| `catalogOnly` | Known integration metadata. Useful for search/planning, not execution. |
|
|
22
|
+
| `setupReady` | Has setup/auth/spec metadata, but still needs an execution provider. |
|
|
23
|
+
| `gatewayExecutable` | Executable through a gateway provider. |
|
|
24
|
+
| `firstPartyExecutable` | Executable through a first-party adapter. |
|
|
25
|
+
| `sandboxExecutable` | Safe to invoke directly from generated sandbox apps. |
|
|
26
|
+
|
|
27
|
+
Precedence is explicit:
|
|
28
|
+
|
|
29
|
+
```txt
|
|
30
|
+
sandboxExecutable
|
|
31
|
+
> firstPartyExecutable
|
|
32
|
+
> gatewayExecutable
|
|
33
|
+
> setupReady
|
|
34
|
+
> catalogOnly
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
When multiple catalogs define the same integration, the registry keeps one
|
|
38
|
+
canonical connector, retains source provenance, merges non-conflicting
|
|
39
|
+
actions/triggers, and reports auth/category conflicts.
|
|
40
|
+
|
|
41
|
+
## Example
|
|
42
|
+
|
|
43
|
+
```ts
|
|
44
|
+
import {
|
|
45
|
+
buildDefaultIntegrationRegistry,
|
|
46
|
+
buildIntegrationToolCatalog,
|
|
47
|
+
searchIntegrationTools,
|
|
48
|
+
} from '@tangle-network/agent-integrations'
|
|
49
|
+
|
|
50
|
+
const registry = buildDefaultIntegrationRegistry()
|
|
51
|
+
const tools = buildIntegrationToolCatalog(registry.connectors)
|
|
52
|
+
const matches = searchIntegrationTools(tools, 'send a slack message', {
|
|
53
|
+
maxRisk: 'write',
|
|
54
|
+
})
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
Aliases such as `notion -> notion-database`, `stripe -> stripe-pack`,
|
|
58
|
+
`twilio -> twilio-sms`, and `outlook-calendar -> microsoft-calendar` resolve to
|
|
59
|
+
one canonical entry while preserving lookup by either name.
|
|
@@ -17,11 +17,13 @@ Goal: cover the integrations that make agents useful for 99% of practical produc
|
|
|
17
17
|
- [x] Coverage catalog for 100+ high-value integrations.
|
|
18
18
|
- [x] Builder API consumes the coverage catalog for app planning.
|
|
19
19
|
- [x] Declarative REST adapter factory for fast first-party promotion of REST-shaped APIs.
|
|
20
|
+
- [x] Provider gateway catalog adapter can normalize 500+ Nango/Pipedream/Activepieces-style connectors.
|
|
21
|
+
- [x] Canonical registry dedupes overlapping catalogs, aliases, support tiers, and conflict diagnostics.
|
|
20
22
|
- [ ] Generated sandbox apps can request missing connections from the catalog.
|
|
21
23
|
- [ ] Live smoke credentials exist for Tier 0 connectors.
|
|
22
24
|
- [ ] Tier 0 connector failures are classified by auth, scope, rate-limit, provider outage, validation, approval, and conflict.
|
|
23
25
|
- [ ] Tier 0 write actions have idempotency and approval tests.
|
|
24
|
-
- [
|
|
26
|
+
- [x] Provider gateway adapters can import/sync catalog metadata from Nango/Pipedream/Activepieces registries.
|
|
25
27
|
|
|
26
28
|
## Tier 0 First-Party Promotion Queue
|
|
27
29
|
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
# Activepieces Community Catalog Attribution
|
|
2
|
+
|
|
3
|
+
`src/activepieces-catalog.generated.ts` is generated from the Activepieces
|
|
4
|
+
Community pieces catalog:
|
|
5
|
+
|
|
6
|
+
- Source repository: https://github.com/activepieces/activepieces
|
|
7
|
+
- Source path: `packages/pieces/community`
|
|
8
|
+
- License: MIT
|
|
9
|
+
- Imported surface: piece ids, display names, descriptions, package names,
|
|
10
|
+
versions, high-level action names, trigger names, auth shape hints, and
|
|
11
|
+
category/domain metadata.
|
|
12
|
+
|
|
13
|
+
The generated catalog is connector metadata for `agent-integrations`; it does
|
|
14
|
+
not vendor the Activepieces runtime or execute Activepieces piece code directly.
|
|
15
|
+
Consumers can run these connectors through an Activepieces-backed provider,
|
|
16
|
+
promote selected entries to first-party adapters, or use the metadata for
|
|
17
|
+
planning and connection setup.
|
|
18
|
+
|
|
19
|
+
Regenerate after checking out Activepieces:
|
|
20
|
+
|
|
21
|
+
```sh
|
|
22
|
+
ACTIVEPIECES_ROOT=/path/to/activepieces node scripts/import-activepieces-catalog.mjs
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
## Upstream License Notice
|
|
26
|
+
|
|
27
|
+
Copyright (c) 2020-2024 Activepieces Inc.
|
|
28
|
+
|
|
29
|
+
Portions of this software are licensed as follows:
|
|
30
|
+
|
|
31
|
+
- All content that resides under the "packages/ee/" and
|
|
32
|
+
"packages/server/api/src/app/ee" directory of this repository, if that
|
|
33
|
+
directory exists, is licensed under the license defined in
|
|
34
|
+
packages/ee/LICENSE.
|
|
35
|
+
- All third party components incorporated into the Activepieces Inc Software
|
|
36
|
+
are licensed under the original license provided by the owner of the
|
|
37
|
+
applicable component.
|
|
38
|
+
- Content outside of the above mentioned directories or restrictions above is
|
|
39
|
+
available under the "MIT Expat" license as defined below.
|
|
40
|
+
|
|
41
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
42
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
43
|
+
in the Software without restriction, including without limitation the rights
|
|
44
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
45
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
46
|
+
furnished to do so, subject to the following conditions:
|
|
47
|
+
|
|
48
|
+
The above copyright notice and this permission notice shall be included in all
|
|
49
|
+
copies or substantial portions of the Software.
|
|
50
|
+
|
|
51
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
52
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
53
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
54
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
55
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
56
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
57
|
+
SOFTWARE.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tangle-network/agent-integrations",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.14.0",
|
|
4
4
|
"description": "Vendor-neutral integration contracts and runtime helpers for sandbox and agent apps.",
|
|
5
5
|
"homepage": "https://github.com/tangle-network/agent-integrations#readme",
|
|
6
6
|
"repository": {
|
|
@@ -21,6 +21,7 @@
|
|
|
21
21
|
}
|
|
22
22
|
},
|
|
23
23
|
"files": [
|
|
24
|
+
"data",
|
|
24
25
|
"dist",
|
|
25
26
|
"docs",
|
|
26
27
|
"examples",
|