Overview
Connect Parser Expert with Flows360
Parse documents and extract data from PDFs, DOCX files, images, and webpages using Parser Expert's powerful API.
Use the Parser Expert 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
- Upload Document
- Get Extracted Data
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: Parser Expert
- Package:
@activepieces/piece-parser-expert@0.1.7 - Exact artifact digest:
sha256:379c4da99da4a0e12ed747b9dc10a51da3777c97fe163950afa5274c2a13a102 - 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
- Upload Document (
upload_document), Upload a document or provide a webpage URL to parse. Supported formats: PDF, DOCX, Image, Txt File (maximum 10 pages per document). Classification: read. - Get Extracted Data (
get_extracted_data), Retrieve the extracted data using the parser ID and bucket ID. The parser ID is returned when you upload a document. 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: custom
Authentication profiles
connection · custom
- API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Upload Document | Yes | No | Upload a document or provide a webpage URL to parse. Supported formats: PDF, DOCX, Image, Txt File (maximum 10 pages per document). |
| Get Extracted Data | Yes | No | Retrieve the extracted data using the parser ID and bucket ID. The parser ID is returned when you upload a document. |
Supported actions
Upload Document · Read
Upload a document or provide a webpage URL to parse. Supported formats: PDF, DOCX, Image, Txt File (maximum 10 pages per document).
upload_document · Risk: low · Retry: safe
Inputs
bucket_id· string · Required, The ID of the bucket where the data will be stored. You can find this in your dashboard under Manage Bucket.file· object · Optional, The file to upload. Supported formats: PDF, DOCX, Image, Txt File (maximum 10 pages per document). This will be ignored if webpage URL is provided.webpage_url· string · Optional, The URL of the webpage to extract content from. This will be ignored if file is provided.
Get Extracted Data · Read
Retrieve the extracted data using the parser ID and bucket ID. The parser ID is returned when you upload a document.
get_extracted_data · Risk: low · Retry: safe
Inputs
parser_id· string · Required, The ID of the parser. This is returned when content is uploaded.bucket_id· string · Required, The ID of the bucket where the data is stored.
Setup
Setup
- Add the Parser Expert 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-parser-expert@0.1.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.
- 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 Parser Expert 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-parser-expert@0.1.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.