Overview
Connect PDFMonkey with Flows360
PDFMonkey integration for Flows360 workflows.
Use the PDFMonkey 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 4 actions and 1 trigger.
Available actions
- Generate Document
- Delete Document
- Find Document
- Custom API Call
Available triggers
- Document Generated
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: PDFMonkey
- Package:
@activepieces/piece-pdfmonkey@0.2.0 - Exact artifact digest:
sha256:f064c5f737bba4afdcfaa24d3e2aa1b047f7c8e287da7420d33428153cd442a7 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Generate Document (
generateDocument), Generates a new document using a specified template. Classification: read. - Delete Document (
deleteDocument), Deletes a document. Classification: read. - Find Document (
findDocument), Finds a document by ID. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- Document Generated, polling.
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: custom
Authentication profiles
connection · custom
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Generate Document | Yes | No | Generates a new document using a specified template. |
| Delete Document | Yes | No | Deletes a document. |
| Find Document | Yes | No | Finds a document by ID. |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
| Document Generated | Yes | No | polling trigger declared by the pinned package. |
Supported actions
Generate Document · Read
Generates a new document using a specified template.
generate_document · Risk: low · Retry: safe
Inputs
document_template_id· string · Requiredpayload· object · Required, Data to use for the Document generation.meta· object · Optional, Meta-Data to attach to the Document.fileName· string · Optionalstatus· string · Optional
Delete Document · Read
Deletes a document.
delete_document · Risk: low · Retry: safe
Inputs
document_id· string · Required
Find Document · Read
Finds a document by ID.
find_document · Risk: low · Retry: safe
Inputs
document_id· string · Required
Custom API Call · Read
Make a custom API call to a specific endpoint
custom_api_call · Risk: low · Retry: safe
Inputs
url· object · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_is_binary· boolean · Optional, Enable for files like PDFs, images, etc.failsafe· boolean · Optional, On a failed request, output the error instead of failing the step.timeout· number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).followRedirects· boolean · Optional, Follow 3xx redirects instead of returning them as the response.
Triggers
Document Generated · Poll
Triggers when a document generation completes successfully.
Setup
Setup
- Add the PDFMonkey 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:
- No provider credential fields are declared by the pinned package.
- 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-pdfmonkey@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 4 actions and 1 trigger 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
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required PDFMonkey 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-pdfmonkey@0.2.0 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.