Overview
Captain-data
This CDK catalogue package is pinned to @activepieces/piece-captain-data@0.2.0 and declares 3 declared actions and no declared triggers. Its definition is derived from the exact reviewed Activepieces source.
Provider runtime verification is recorded separately when an approved test connection is exercised; this catalogue entry does not claim that verification.
Technical guide
Technical reference
- Package:
@activepieces/piece-captain-data@0.2.0 - Exact artifact digest:
sha256:0d93e270f642ce3338ecaa95e9695c8a948a1de92e224297343a3e7096e898cb - Source: the exact reviewed Activepieces source
- Authentication, action and trigger schemas are taken from the exact pinned package.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API key Required · protected credential
- Project ID Required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Launch a workflow | Yes | No | |
| Get job results | Yes | No | |
| Custom API Call | Yes | No |
Setup
Setup
Create a tenant connection only in the consuming Studio instance when this connector is made available there. Credentials remain in that tenant's Vault-backed connection and are not stored in CDK package metadata.
Limitations
The package has passed deterministic offline package-load and contract validation. No provider credentials, provider API call or live webhook delivery is represented by this release state.