Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Crypto

Generate random passwords and hash existing text

CategoryCore
AuthenticationNo authentication required
Version0.0.28
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Crypto with Flows360

Generate random passwords and hash existing text

Use the Crypto 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

  • Text to Hash
  • Generate HMAC Signature
  • Generate RSA Signature
  • Generate Password
  • Base64 Decode
  • Base64 Encode
  • OpenPGP Encrypt

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: Crypto
  • Package: @activepieces/piece-crypto@0.0.28
  • Exact artifact digest: sha256:dbd4b6cbac33b46a2b7190880c5daa4570bfd16916d572e465dc675aca35dc1a
  • 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

  • Text to Hash (hash-text), Converts text to a hash value using various hashing algorithms Classification: read.
  • Generate HMAC Signature (hmac-signature), Converts text to a HMAC signed hash value using various hashing algorithms Classification: read.
  • Generate RSA Signature (rsa-signature), Signs text with an RSA private key using SHA-256, SHA-384, or SHA-512 (RSA-SHA256 by default) Classification: read.
  • Generate Password (generate-password), Generates a random password with the specified length Classification: read.
  • Base64 Decode (base64-decode), Converts base64 text back to plain text. Classification: read.
  • Base64 Encode (base64-encode), Converts plain text into base64 format. Classification: read.
  • OpenPGP Encrypt (openpgpEncrypt), Encrypt a file using OpenPGP public key Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Text to Hash Yes No Converts text to a hash value using various hashing algorithms
Generate HMAC Signature Yes No Converts text to a HMAC signed hash value using various hashing algorithms
Generate RSA Signature Yes No Signs text with an RSA private key using SHA-256, SHA-384, or SHA-512 (RSA-SHA256 by default)
Generate Password Yes No Generates a random password with the specified length
Base64 Decode Yes No Converts base64 text back to plain text.
Base64 Encode Yes No Converts plain text into base64 format.
OpenPGP Encrypt Yes No Encrypt a file using OpenPGP public key

Supported actions

Text to Hash · Read

Converts text to a hash value using various hashing algorithms

hash_text · Risk: low · Retry: safe

Inputs

  • method · string · Required, The hashing algorithm to use
  • text · string · Required, The text to be hashed
Generate HMAC Signature · Read

Converts text to a HMAC signed hash value using various hashing algorithms

hmac_signature · Risk: low · Retry: safe

Inputs

  • secretKey · string · Required, The secret key to encrypt
  • secretKeyEncoding · string · Required, The secret key encoding to use
  • method · string · Required, The hashing algorithm to use
  • text · string · Required, The text to be hashed and encrypted
  • outputEncoding · string · Optional, The encoding of the output signature
Generate RSA Signature · Read

Signs text with an RSA private key using SHA-256, SHA-384, or SHA-512 (RSA-SHA256 by default)

rsa_signature · Risk: low · Retry: safe

Inputs

  • privateKey · string · Required, The RSA private key in PEM format (PKCS#1 or PKCS#8)
  • passphrase · string · Optional, The passphrase protecting the private key, leave empty if it is not encrypted
  • method · string · Required, The hashing algorithm to use
  • text · string · Required, The text to be signed
  • outputEncoding · string · Optional, The encoding of the output signature
Generate Password · Read

Generates a random password with the specified length

generate_password · Risk: low · Retry: safe

Inputs

  • length · number · Required, The length of the password (maximum 256)
  • characterSet · string · Required, The character set to use when generating the password
Base64 Decode · Read

Converts base64 text back to plain text.

base64_decode · Risk: low · Retry: safe

Inputs

  • text · string · Required, The text to be decoded.
Base64 Encode · Read

Converts plain text into base64 format.

base64_encode · Risk: low · Retry: safe

Inputs

  • text · string · Required, The text to be encoded.
OpenPGP Encrypt · Read

Encrypt a file using OpenPGP public key

openpgp_encrypt · Risk: low · Retry: safe

Inputs

  • file · object · Required, The file to encrypt
  • publicKey · string · Required, The PGP public key in ASCII armor format

Setup

Setup

  1. Add the Crypto 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-crypto@0.0.28; 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 Crypto 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-crypto@0.0.28 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.

github.com