Create User with Clerk API on New Order Created from Lemon Squeezy API

Pipedream makes it easy to connect APIs for Clerk, Lemon Squeezy and 2,400+ other apps remarkably fast.

Trigger workflow on

New Order Created from the Lemon Squeezy API

Next, do this

Create User with the Clerk API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Lemon Squeezy trigger and Clerk action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Order Created trigger
1. Connect your Lemon Squeezy account
2. Configure timer
Configure the Create User action
1. Connect your Clerk account
2. Optional- Configure External Id
3. Optional- Configure First Name
4. Optional- Configure Last Name
5. Configure Email Addresses
6. Optional- Configure Phone Numbers
7. Optional- Configure Web3 Wallets
8. Optional- Configure Username
9. Configure Password
10. Optional- Configure Password Digest
11. Optional- Configure Password Hasher
12. Optional- Configure Skip Password Checks
13. Optional- Configure Skip Password Requirement
14. Optional- Configure TOTP Secret
15. Optional- Configure Backup Codes
16. Optional- Configure Public Metadata
17. Optional- Configure Private Metadata
18. Optional- Configure Unsafe Metadata
19. Optional- Configure Created At
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Order Created on Lemon Squeezy

Description:Emit new event when a new order is created.

Version:0.0.1

Key:lemon_squeezy-order-created

View on GitHub

Lemon Squeezy Overview#

The Lemon Squeezy API lets you manage and sell digital products with ease. On Pipedream, you can integrate Lemon Squeezy with your sales, marketing, and support tools to automate tasks like customer follow-ups, license management, and sales reporting. With Pipedream's serverless platform, you can create workflows that trigger on Lemon Squeezy events or schedule tasks, process data, and connect to a vast array of other apps and services without writing backend infrastructure.

Trigger Code#

import { defineSource } from "@pipedream/types";
import common from "../common/base.mjs";
export default defineSource({
    ...common,
    key: "lemon_squeezy-order-created",
    name: "New Order Created",
    description: "Emit new event when a new order is created.",
    version: "0.0.1",
    type: "source",
    dedupe: "unique",
    methods: {
        ...common.methods,
        getFunc() {
            return this.lemonSqueezy.listOrders;
        },
        getSummary({ id }) {
            return `A new order with id ${id} was created!`;
        },
    },
});

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Lemon Squeezy	`lemonSqueezy`	`app`	This component uses the Lemon Squeezy app.
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

Lemon Squeezy uses API keys for authentication. When you connect your Lemon Squeezy account, Pipedream securely stores the keys so you can easily authenticate to Lemon Squeezy APIs in both code and no-code steps.

To connect Pipedream with your Lemon Squeezy account,

Sign in to your Lemon Squeezy account
Create a new API key here
Paste that below

About Lemon Squeezy#

Lemon Squeezy is the all-in-one platform for running your SaaS business. Payments, subscriptions, global tax compliance, fraud prevention, multi-currency support, failed payment recovery, PayPal integration and more. We make running your software business easy peasy.

Action#

Create User on Clerk

Description:Creates a new user. Your user management settings determine how you should setup your user model. [See the documentation](https://clerk.com/docs/reference/backend-api/tag/Users#operation/CreateUser)

Version:0.0.1

Key:clerk-create-user

View on GitHub

Clerk Overview#

The Clerk API lets you manage user authentication and create secure, delightful user experiences in your apps. Within Pipedream's serverless platform, you can harness this API to automate workflows that trigger on user events, sync user data across apps, and maintain robust user management without the heavy lifting of building authentication infrastructure from scratch.

Action Code#

import clerk from "../../clerk.app.mjs";
import {
  parseError, parseObject,
} from "../../common/utils.mjs";

export default {
  key: "clerk-create-user",
  name: "Create User",
  version: "0.0.1",
  description: "Creates a new user. Your user management settings determine how you should setup your user model. [See the documentation](https://clerk.com/docs/reference/backend-api/tag/Users#operation/CreateUser)",
  type: "action",
  props: {
    clerk,
    externalId: {
      propDefinition: [
        clerk,
        "externalId",
      ],
      optional: true,
    },
    firstName: {
      propDefinition: [
        clerk,
        "firstName",
      ],
      optional: true,
    },
    lastName: {
      propDefinition: [
        clerk,
        "lastName",
      ],
      optional: true,
    },
    emailAddress: {
      type: "string[]",
      label: "Email Addresses",
      description: "Email addresses to add to the user. Must be unique across your instance. The first email address will be set as the user's primary email address.",
    },
    phoneNumber: {
      type: "string[]",
      label: "Phone Numbers",
      description: "Phone numbers to add to the user. Must be unique across your instance. The first phone number will be set as user's primary phone number.",
      optional: true,
    },
    web3Wallet: {
      type: "string[]",
      label: "Web3 Wallets",
      description: "Web3 wallets to add to the user. Must be unique across your instance. The first wallet will be set as the user's primary wallet.",
      optional: true,
    },
    username: {
      propDefinition: [
        clerk,
        "username",
      ],
      optional: true,
    },
    password: {
      propDefinition: [
        clerk,
        "password",
      ],
    },
    passwordDigest: {
      type: "string",
      label: "Password Digest",
      description: "In case you already have the password digests and not the passswords, you can use them for the newly created user via this property. The digests should be generated with one of the supported algorithms. The hashing algorithm can be specified using the `Password Hasher` property.",
      optional: true,
    },
    passwordHasher: {
      type: "string",
      label: "Password Hasher",
      description: "The hashing algorithm that was used to generate the password digest. The algorithms that Clerk supports at the moment are `bcrypt`, `bcrypt_sha256_django`, `md5`, `pbkdf2_sha256`, `pbkdf2_sha256_django`, `phpass`, `scrypt_firebase` and 2 `argon2` variants, `argon2i` and `argon2id`. Each of the above expects the incoming digest to be of a particular format. [See the documentarion](https://clerk.com/docs/reference/backend-api/tag/Users#operation/CreateUser!path=password_hasher&t=request) for further information.",
      optional: true,
    },
    skipPasswordChecks: {
      propDefinition: [
        clerk,
        "skipPasswordChecks",
      ],
      optional: true,
    },
    skipPasswordRequirement: {
      type: "boolean",
      label: "Skip Password Requirement",
      description: "When set to `true`, `password` is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. Please note that you cannot use this flag if password is the only way for a user to sign into your instance.",
      optional: true,
    },
    totpSecret: {
      propDefinition: [
        clerk,
        "totpSecret",
      ],
      optional: true,
    },
    backupCodes: {
      propDefinition: [
        clerk,
        "backupCodes",
      ],
      optional: true,
    },
    publicMetadata: {
      propDefinition: [
        clerk,
        "publicMetadata",
      ],
      optional: true,
    },
    privateMetadata: {
      propDefinition: [
        clerk,
        "privateMetadata",
      ],
      optional: true,
    },
    unsafeMetadata: {
      propDefinition: [
        clerk,
        "unsafeMetadata",
      ],
      optional: true,
    },
    createdAt: {
      propDefinition: [
        clerk,
        "createdAt",
      ],
      optional: true,
    },
  },
  async run({ $ }) {
    if (this.passwordDigest) {
      this.password = null;
    }
    try {
      const response = await this.clerk.createUser({
        $,
        data: {
          external_id: this.externalId,
          first_name: this.firstName,
          last_name: this.lastName,
          email_address: parseObject(this.emailAddress),
          phone_number: parseObject(this.phoneNumber),
          web3_wallet: parseObject(this.web3Wallet),
          username: this.username,
          password: this.password,
          password_digest: this.passwordDigest,
          password_hasher: this.passwordHasher,
          skip_password_checks: this.skipPasswordChecks,
          skip_password_requirement: this.skipPasswordRequirement,
          totp_secret: this.totpSecret,
          backup_codes: parseObject(this.backupCodes),
          public_metadata: parseObject(this.publicMetadata),
          private_metadata: parseObject(this.privateMetadata),
          unsafe_metadata: parseObject(this.unsafeMetadata),
          created_at: this.createdAt,
        },
      });

      $.export("$summary", `A new user with Id: ${response.id} was successfully created!`);
      return response;
    } catch (err) {
      return parseError(err);
    }
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Clerk	`clerk`	`app`	This component uses the Clerk app.
External Id	`externalId`	`string`	The ID of the user as used in your external systems or your previous authentication solution. Must be unique across your instance.
First Name	`firstName`	`string`	The first name to assign to the user.
Last Name	`lastName`	`string`	The last name to assign to the user.
Email Addresses	`emailAddress`	`string[]`	Email addresses to add to the user. Must be unique across your instance. The first email address will be set as the user's primary email address.
Phone Numbers	`phoneNumber`	`string[]`	Phone numbers to add to the user. Must be unique across your instance. The first phone number will be set as user's primary phone number.
Web3 Wallets	`web3Wallet`	`string[]`	Web3 wallets to add to the user. Must be unique across your instance. The first wallet will be set as the user's primary wallet.
Username	`username`	`string`	The username to give to the user. It must be unique across your instance.
Password	`password`	`string`	The plaintext password to give to the user. Must be at least 8 characters long, and can not be in any list of hacked passwords.
Password Digest	`passwordDigest`	`string`	In case you already have the password digests and not the passswords, you can use them for the newly created user via this property. The digests should be generated with one of the supported algorithms. The hashing algorithm can be specified using the `Password Hasher` property.
Password Hasher	`passwordHasher`	`string`	The hashing algorithm that was used to generate the password digest. The algorithms that Clerk supports at the moment are `bcrypt`, `bcrypt_sha256_django`, `md5`, `pbkdf2_sha256`, `pbkdf2_sha256_django`, `phpass`, `scrypt_firebase` and 2 `argon2` variants, `argon2i` and `argon2id`. Each of the above expects the incoming digest to be of a particular format. See the documentarion for further information.
Skip Password Checks	`skipPasswordChecks`	`boolean`	When set to `true` all password checks are skipped. It is recommended to use this method only when migrating plaintext passwords to Clerk. Upon migration the user base should be prompted to pick stronger password.
Skip Password Requirement	`skipPasswordRequirement`	`boolean`	When set to `true`, `password` is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. Please note that you cannot use this flag if password is the only way for a user to sign into your instance.
TOTP Secret	`totpSecret`	`string`	In case TOTP is configured on the instance, you can provide the secret to enable it on the newly created user without the need to reset it.
Backup Codes	`backupCodes`	`string[]`	If Backup Codes are configured on the instance, you can provide them to enable it on the newly created user without the need to reset them. You must provide the backup codes in plain format or the corresponding bcrypt digest.
Public Metadata	`publicMetadata`	`object`	Metadata saved on the user, that is visible to both your Frontend and Backend APIs.
Private Metadata	`privateMetadata`	`object`	Metadata saved on the user, that is only visible to your Backend API.
Unsafe Metadata	`unsafeMetadata`	`object`	Metadata saved on the user, that can be updated from both the Frontend and Backend APIs. `Note: Since this data can be modified from the frontend, it is not guaranteed to be safe.`
Created At	`createdAt`	`string`	A custom date/time denoting when the user signed up to the application, specified in RFC3339 format (e.g. `2012-10-20T07:15:20.902Z`).

Action Authentication#

Clerk uses API keys for authentication. When you connect your Clerk account, Pipedream securely stores the keys so you can easily authenticate to Clerk APIs in both code and no-code steps.

About Clerk#

Drop-in authentication for React and React Native.

More Ways to Connect Clerk + Lemon Squeezy#

Other Popular Integrations#

Create User with Clerk API on New Subscription Cancelled from Lemon Squeezy API

Lemon Squeezy + Clerk

Try it

Create User with Clerk API on New Subscription Created from Lemon Squeezy API

Lemon Squeezy + Clerk

Try it

Create User Invitation with Clerk API on New Order Created from Lemon Squeezy API

Lemon Squeezy + Clerk

Try it

Create User Invitation with Clerk API on New Subscription Cancelled from Lemon Squeezy API

Lemon Squeezy + Clerk

Try it

Create User Invitation with Clerk API on New Subscription Created from Lemon Squeezy API

Lemon Squeezy + Clerk

Try it

Popular Triggers#

New Order Created from the Lemon Squeezy API

Emit new event when a new order is created.

Try it

New Subscription Cancelled from the Lemon Squeezy API

Emit new event when a new subscription is cancelled.

Try it

New Subscription Created from the Lemon Squeezy API

Emit new event when a new subscription is created.

Try it

Popular Actions#

Retrieve A Customer with the Lemon Squeezy API

Retrive an existent customer. See docs here

Try it

Retrieve A Product with the Lemon Squeezy API

Retrive an existent product. See docs here

Try it

Retrieve An Order with the Lemon Squeezy API

Retrive an existent order. See docs here

Try it

Create User with the Clerk API

Creates a new user. Your user management settings determine how you should setup your user model. See the documentation

Try it

Create User Invitation with the Clerk API

Creates a new invitation for the given email address and sends the invitation email. Keep in mind that you cannot create an invitation if there is already one for the given email address. Also, trying to create an invitation for an email address that already exists in your application will result to an error. See the documentation

Try it