Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Cryptolens

Cryptolens is a Software Licensing as a Service (SLaaS) platform that provides developers with tools to manage software licenses, protect against piracy, and analyze usage data.

CategoryDeveloper Tools
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Cryptolens with Flows360

Cryptolens is a Software Licensing as a Service (SLaaS) platform that provides developers with tools to manage software licenses, protect against piracy, and analyze usage data.

Use the Cryptolens 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 5 actions and 1 trigger.

Available actions

  • Add Customer
  • Block Key
  • Create Key
  • Extend License
  • Custom API Call

Available triggers

  • New API Event

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: Cryptolens
  • Package: @activepieces/piece-cryptolens@0.2.0
  • Exact artifact digest: sha256:d283f3381d16621ee4c77b1479a5c7b1ab959182ae5a0ee202903776234bd842
  • 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

  • Add Customer (addCustomer), Add a new customer to your Cryptolens account Classification: read.
  • Block Key (blockKey), Block a license key to prevent it from being accessible by most Web API methods Classification: read.
  • Create Key (createKey), Create a new license key for a product Classification: read.
  • Extend License (extendLicense), Extend a license key by a specified number of days Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New API Event, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Customer Yes No Add a new customer to your Cryptolens account
Block Key Yes No Block a license key to prevent it from being accessible by most Web API methods
Create Key Yes No Create a new license key for a product
Extend License Yes No Extend a license key by a specified number of days
Custom API Call Yes No Make a custom API call to a specific endpoint
New API Event Yes No polling trigger declared by the pinned package.

Supported actions

Add Customer · Read

Add a new customer to your Cryptolens account

add_customer · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the customer (max 100 characters)
  • email · string · Required, The email of the customer (max 100 characters)
  • companyName · string · Required, The company name the customer belongs to (max 100 characters)
  • notes · string · Optional, Optional notes field (max 1000 characters)
  • enableCustomerAssociation · boolean · Optional, If enabled, a portal link will be returned where the customer can view their licenses
  • allowActivationManagement · boolean · Optional, If enabled, the customer can activate and deactivate devices through the customer portal
  • allowMultipleUserAssociation · boolean · Optional, If enabled, multiple user accounts can be associated with this customer
Block Key · Read

Block a license key to prevent it from being accessible by most Web API methods

block_key · Risk: low · Retry: safe

Inputs

  • productId · number · Required, The product ID
  • key · string · Required, The serial key string to block
Create Key · Read

Create a new license key for a product

create_key · Risk: low · Retry: safe

Inputs

  • productId · number · Required, The product ID
  • period · number · Optional, The number of days from today the license key should be valid. Default is 0 (no expiration).
  • f1 · boolean · Optional, Enable Feature 1
  • f2 · boolean · Optional, Enable Feature 2
  • f3 · boolean · Optional, Enable Feature 3
  • f4 · boolean · Optional, Enable Feature 4
  • f5 · boolean · Optional, Enable Feature 5
  • f6 · boolean · Optional, Enable Feature 6
  • f7 · boolean · Optional, Enable Feature 7
  • f8 · boolean · Optional, Enable Feature 8
  • notes · string · Optional, Additional notes about the license key (max 500 characters)
  • block · boolean · Optional, Block the key from being accessed by the Activation method
  • customerId · number · Optional, The ID of the customer to associate with this license key
  • trialActivation · boolean · Optional, Enable or disable trial activation
  • maxNoOfMachines · number · Optional, The maximum number of computers that can activate the key. Default is 0 (unlimited).
  • allowedMachines · string · Optional, A list of machine codes (separated by new lines) that will be prioritized during activation
  • resellerId · number · Optional, The ID of the reseller to associate with this license key
  • noOfKeys · number · Optional, The number of keys to generate. Default is 1. Maximum 1000 per request.
Extend License · Read

Extend a license key by a specified number of days

extend_license · Risk: low · Retry: safe

Inputs

  • productId · number · Required, The product ID
  • key · string · Required, The serial key string to extend
  • noOfDays · number · Optional, The number of days to extend the license. Use negative numbers to decrease the expiration date.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_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

New API Event · Poll

Trigger when a new API event is logged (activation, deactivation, key creation, etc.)

Inputs

  • productId · number
  • key · string
  • states · string
  • limit · number

Setup

Setup

  1. Add the Cryptolens 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-cryptolens@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 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 Cryptolens 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-cryptolens@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.

github.com