Pdfcrowd

Overview

Connect Pdfcrowd with Flows360

Convert web pages and HTML to PDF with advanced formatting options

Use the Pdfcrowd 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 3 actions and no declared triggers.

Available actions

• Convert URL to PDF
• Convert HTML to PDF
• Custom API Call

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: Pdfcrowd
• Package: @activepieces/piece-pdfcrowd@0.2.0
• Exact artifact digest: sha256:e181f6896e50324bcc8d8d818019d9e6baf2178e788c3efd6517d6c34e90db81
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

BASIC 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

• Convert URL to PDF (url_to_pdf), Convert a web page URL to PDF document Classification: read.
• Convert HTML to PDF (html_to_pdf), Convert HTML content (string) to PDF document Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authentication

Authentication method: basic

Authentication profiles

Supported objects

Setup

Setup

1. Add the Pdfcrowd connector to the workflow in the target Flows360 Studio instance.
2. 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.
3. Provide the connection fields declared by the pinned package:

• No provider credential fields are declared by the pinned package.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-pdfcrowd@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 3 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.
• Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Related documentation