Overview
Connect Pastebin with Flows360
Simple and secure text sharing
Use the Pastebin connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and no declared triggers.
Available actions
- Create Paste
- Get Paste Content
Available triggers
- No triggers are declared in this pinned package.
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: Pastebin
- Package:
@activepieces/piece-pastebin@0.2.7 - Exact artifact digest:
sha256:6c135f645807eeb1d54db135c937f2f247e6275307563b673f624869f6589f0d - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Create Paste (
create_paste), Creates a new paste Classification: read. - Get Paste Content (
get_paste_content), Retrieves the content of a paste Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Developer Key Required · protected credential
- Username Optional
- Password Optional · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Paste | Yes | No | Creates a new paste |
| Get Paste Content | Yes | No | Retrieves the content of a paste |
Supported actions
Create Paste · Read
Creates a new paste
create_paste · Risk: low · Retry: safe
Inputs
content· string · Requiredformat· string · Optionalname· string · Optionalprivacy· string · Optionalexpiry· string · Optionalfolder· string · Optional
Get Paste Content · Read
Retrieves the content of a paste
get_paste_content · Risk: low · Retry: safe
Inputs
paste_id· string · Required
Setup
Setup
- Add the Pastebin connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- Developer Key (
token), required; stored as a sensitive connection value. - Username (
username), optional. - Password (
password), optional; stored as a sensitive connection value.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-pastebin@0.2.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 2 actions and 0 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Runtime execution evidence is managed separately from package metadata.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Pastebin connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-pastebin@0.2.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.