Overview
Connect Files Helper with Flows360
Read file content and return it in different formats.
Use the Files Helper 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 7 actions and no declared triggers.
Available actions
- Read File
- Create file
- Change File Encoding
- Check file type
- Zip Files
- Unzip File
- Get File Name
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: Files Helper
- Package:
@activepieces/piece-file-helper@0.1.30 - Exact artifact digest:
sha256:646c921f5e14654723e34b5274f38fd8f5f6ff9a7bf20544b346ee653e8810ae - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Read File (
read_file), Read a file from the file system Classification: read. - Create file (
createFile), Create file from content Classification: read. - Change File Encoding (
change_file_encoding), Changes the encoding of a file Classification: read. - Check file type (
checkFileType), Check MIME type of a file and filter based on selected types Classification: read. - Zip Files (
zipFiles), Create compressed zip file from one or many files Classification: read. - Unzip File (
unzipFile), Unzip compressed zip file Classification: read. - Get File Name (
get_file_name), Get the name of a file 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: No authentication required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Read File | Yes | No | Read a file from the file system |
| Create file | Yes | No | Create file from content |
| Change File Encoding | Yes | No | Changes the encoding of a file |
| Check file type | Yes | No | Check MIME type of a file and filter based on selected types |
| Zip Files | Yes | No | Create compressed zip file from one or many files |
| Unzip File | Yes | No | Unzip compressed zip file |
| Get File Name | Yes | No | Get the name of a file |
Supported actions
Read File · Read
Read a file from the file system
read_file · Risk: low · Retry: safe
Inputs
file· object · RequiredreadOptions· string · Required, The output format
Create file · Read
Create file from content
create_file · Risk: low · Retry: safe
Inputs
content· string · RequiredfileName· string · Requiredencoding· string · Required
Change File Encoding · Read
Changes the encoding of a file
change_file_encoding · Risk: low · Retry: safe
Inputs
inputFile· object · RequiredinputEncoding· string · RequiredoutputFileName· string · RequiredoutputEncoding· string · Required
Check file type · Read
Check MIME type of a file and filter based on selected types
check_file_type · Risk: low · Retry: safe
Inputs
file· object · RequiredmimeTypes· string · Required, Choose one or more MIME types to check against the file.
Zip Files · Read
Create compressed zip file from one or many files
zip_files · Risk: low · Retry: safe
Inputs
files· array · RequiredoutputFileName· string · RequiredusePassword· boolean · Optional, Enable password protection for the zip filepasswordOptions· object · Optional
Unzip File · Read
Unzip compressed zip file
unzip_file · Risk: low · Retry: safe
Inputs
file· object · RequiredmaxResults· number · Optional, nThrow an error if zip file has more than expected entries.n- This is a safe measure when working with untrusted zip files.n- Exclude this field or set to 0 to skip this check.nusePassword· boolean · Optional, Enable if the zip file is password protectedpasswordOptions· object · Optional
Get File Name · Read
Get the name of a file
get_file_name · Risk: low · Retry: safe
Inputs
file· object · Required
Setup
Setup
- Add the Files Helper 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-file-helper@0.1.30; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 7 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 Files Helper 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-file-helper@0.1.30 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.