Zapier
How to integrate Zapier with Cloudsmith
Cloudsmith provides a Zapier integration to manage your entitlement codes; allowing you to hook up almost any shopping cart to enable Cloudsmith as your digital asset distribution provider.
The Cloudsmith API gives you full control of repository entitlements; allowing you to create, destroy and distribute tokens when you detect an event. Just create a Zap, configure your API Key, and you'll be all set.
Setup
The Cloudsmith Zapier Integration uses your Cloudsmith API Key for authentication:
Zapier Cloudsmith API Key setup
You can get your Cloudsmith API key from your user settings page when you have logged into the Cloudsmith website, or by using the Cloudsmith CLI cloudsmith login command.
Actions
The Cloudsmith Zapier Integration currently provides two actions:
- Create Entitlement Token
- Disable Entitlement Token
Please see Entitlements for more information on Cloudsmith Entitlement Tokens.
Create Entitlement Token
The Create Entitlement Token action has three required fields:
Zapier Create Entitlement Token Fields
Fields
| Field Name | Description | Required |
|---|---|---|
| Token Name | A name for the Token within the repository |  |
| Repository Owner | The username or organisation name that owns the repository | |
| Repository | The repository identifier (also called the slug) | |
| Token String | A string for the token itself. If one is not provided, a random string will be generated. |  |
| Is Active | A boolean defines if the token is enabled or disabled | |
| Valid From | The start date that the token is valid from | |
| Valid To | The end date that the token is valid until | |
| Limit Number of Downloads | The maximum number of downloads that the Token allows | |
| Limit Number of Clients | The maximum number of clients (Unique IP addresses) allowed by the token | |
| Limit Package Query | The package-based search query to apply to restrict downloads. See Searching / Filtering for further details. | |
| Limit Path Query | The path-based search query to apply to restrict downloads.The path evaluated does not include the domain name, the namespace, the entitlement code used, the package format, etc. and it always starts with a forward slash. | |
Disable Entitlement Token
The Disable Entitlement Token action has three required fields:
Zapier Delete Entitlement Token Fields
Fields
| Field Name | Description | Required |
|---|---|---|
| Repository Owner | The username or organisation name that owns the repository | |
| Repository | The repository identifier (also called the slug) | |
| Entitlement Identifier | The unique identifier for a token within a repository (see Entitlements for further information on tokens and identifiers) | |
Updated over 3 years ago