Overview
Approval (Legacy)
This CDK catalogue package is pinned to @activepieces/piece-approval@0.1.28 and declares 2 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-approval@0.1.28 - Exact artifact digest:
sha256:34f7ad9d7ad44b67812ff03efaa08b42ad4c506f459810f8aa6d359ed19cd6de - Source: the exact reviewed Activepieces source
- Authentication, action and trigger schemas are taken from the exact pinned package.
Capability summary
Authentication
Authentication method: No authentication required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Wait for Approval | Yes | No | |
| Create Approval Links | Yes | No |
Supported actions
Wait for Approval · Read
Pauses the flow and wait for the approval from the user
wait_for_approval · Risk: low · Retry: safe
Inputs
markdown· string · Optional, This piece is legacy but still supported. For a new flow, prefer the approval actions in the Approvals tab, which deliver the request and wait for the answer in one step.
Create Approval Links · Read
Create links only without pausing the flow, use wait for approval to pause
create_approval_links · Risk: low · Retry: safe
Inputs
markdown· string · Optional, This piece is legacy but still supported. Unlike the approval actions in the Approvals tab, it hands out a link without pausing the flow.
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.