Update User with Clerk API on New Submission (Instant) from Jotform API

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

Trigger workflow on

New Submission (Instant) from the Jotform API

Next, do this

Update 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 Jotform 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 Submission (Instant) trigger
1. Connect your Jotform account
2. Optional- Select a Team
3. Select a Form
Configure the Update User action
1. Connect your Clerk account
2. Select a User Id
3. Optional- Configure External Id
4. Optional- Configure First Name
5. Optional- Configure Last Name
6. Optional- Select a Primary Email Address Id
7. Optional- Configure Notify Primary Email Address Changed
8. Optional- Select a Primary Phone Number Id
9. Optional- Select a Primary Web3 Wallet Id
10. Optional- Configure Username
11. Optional- Configure Profile Image Id
12. Optional- Configure Password
13. Optional- Configure Skip Password Checks
14. Optional- Configure Sign Out Of Other Sessions
15. Optional- Configure TOTP Secret
16. Optional- Configure Backup Codes
17. Optional- Configure Public Metadata
18. Optional- Configure Private Metadata
19. Optional- Configure Unsafe Metadata
20. Optional- Configure Delete Self Enable
21. Optional- Configure Create Organization Enabled
22. 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 Submission (Instant) on Jotform

Description:Emit new event when a form is submitted

Version:0.1.5

Key:jotform-new-submission

View on GitHub

Jotform Overview#

Jotform’s API is a powerhouse for automating form and survey data management. With Pipedream, harness this API to trigger workflows from new form submissions, manipulate and analyze your form data, and sync it across various platforms. Think streamlined data entry to CRMs, instant notifications for new leads or feedback, and timely data backups to cloud storage.

Trigger Code#

import jotform from "../../jotform.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "jotform-new-submission",
  name: "New Submission (Instant)",
  description: "Emit new event when a form is submitted",
  version: "0.1.5",
  type: "source",
  dedupe: "unique",
  props: {
    jotform,
    http: "$.interface.http",
    teamId: {
      propDefinition: [
        jotform,
        "teamId",
      ],
    },
    formId: {
      propDefinition: [
        jotform,
        "formId",
        (c) => ({
          teamId: c.teamId,
          excludeDeleted: true,
        }),
      ],
    },
  },
  hooks: {
    async deploy() {
      const { content: form } = await this.jotform.getForm(this.formId, this.teamId);
      const { content: submissions } = await this.jotform.getFormSubmissions({
        formId: this.formId,
        teamId: this.teamId,
        params: {
          limit: 25,
          orderby: "created_at",
        },
      });
      for (let submission of submissions.reverse()) {
        const meta = {
          id: submission.id,
          summary: form.title,
          ts: Date.now(),
        };
        this.$emit(submission, meta);
      }
    },
    async activate() {
      return (await this.jotform.createHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        teamId: this.teamId,
      }));
    },
    async deactivate() {
      return (await this.jotform.deleteHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        teamId: this.teamId,
      }));
    },
  },
  async run(event) {
    const { body } = event;
    let { content: submission } = await this.jotform.getFormSubmission({
      submissionId: body.submissionID,
      teamId: this.teamId,
    });

    // insert answers from the webhook event
    const rawRequest = JSON.parse(body.rawRequest);
    for (const key of Object.keys(rawRequest)) {
      const regex = /^q(\d+)_/;
      const match = key.match(regex);
      if (match && match[1]) {
        submission.answers[match[1]].answer = rawRequest[key];
      }
    }

    this.$emit(submission, {
      summary: body.formTitle || JSON.stringify(body),
      id: body.submissionID,
      ts: Date.now(),
    });
  },
  sampleEmit,
};

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
Jotform	`jotform`	`app`	This component uses the Jotform app.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Team	`teamId`	`string`	Select a value from the drop down menu.
Form	`formId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

About Jotform#

Jotform enables you to create online forms, collect responses directly in your email, and create fillable PDF forms.

Action#

Update User on Clerk

Description:Update a user's attributes. You can set the user's primary contact identifiers (email address and phone numbers) by updating the `Primary Email Address Id` and `Primary Phone Number Id` attributes respectively. Both IDs should correspond to verified identifications that belong to the user. [See the documentation](https://clerk.com/docs/reference/backend-api/tag/Users#operation/CreateUser)

Version:0.0.1

Key:clerk-update-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 { parseObject } from "../../common/utils.mjs";

export default {
  key: "clerk-update-user",
  name: "Update User",
  version: "0.0.1",
  description: "Update a user's attributes. You can set the user's primary contact identifiers (email address and phone numbers) by updating the `Primary Email Address Id` and `Primary Phone Number Id` attributes respectively. Both IDs should correspond to verified identifications that belong to the user. [See the documentation](https://clerk.com/docs/reference/backend-api/tag/Users#operation/CreateUser)",
  type: "action",
  props: {
    clerk,
    userId: {
      propDefinition: [
        clerk,
        "userId",
      ],
    },
    externalId: {
      propDefinition: [
        clerk,
        "externalId",
      ],
      optional: true,
    },
    firstName: {
      propDefinition: [
        clerk,
        "firstName",
      ],
      optional: true,
    },
    lastName: {
      propDefinition: [
        clerk,
        "lastName",
      ],
      optional: true,
    },
    primaryEmailAddressId: {
      propDefinition: [
        clerk,
        "primaryEmailAddressId",
        ({ userId }) => ({
          userId,
        }),
      ],
      optional: true,
    },
    notifyPrimaryEmailAddressChanged: {
      type: "boolean",
      label: "Notify Primary Email Address Changed",
      description: "If set to `true`, the user will be notified that their primary email address has changed. By default, no notification is sent.",
      optional: true,
    },
    primaryPhoneNumberId: {
      propDefinition: [
        clerk,
        "primaryPhoneNumberId",
        ({ userId }) => ({
          userId,
        }),
      ],
      optional: true,
    },
    primaryWeb3WalletId: {
      propDefinition: [
        clerk,
        "primaryWeb3WalletId",
        ({ userId }) => ({
          userId,
        }),
      ],
      optional: true,
    },
    username: {
      propDefinition: [
        clerk,
        "username",
      ],
      optional: true,
    },
    profileImageId: {
      type: "string",
      label: "Profile Image Id",
      description: "The ID of the image to set as the user's profile image",
      optional: true,
    },
    password: {
      propDefinition: [
        clerk,
        "password",
      ],
      optional: true,
    },
    skipPasswordChecks: {
      propDefinition: [
        clerk,
        "skipPasswordChecks",
      ],
      optional: true,
    },
    signOutOfOtherSessions: {
      type: "boolean",
      label: "Sign Out Of Other Sessions",
      description: "Set to `true` to sign out the user from all their active sessions once their password is updated. This parameter can only be used when providing a `password`.",
      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,
    },
    deleteSelfEnable: {
      type: "boolean",
      label: "Delete Self Enable",
      description: "If `true`, the user can delete themselves with the Frontend API.",
      optional: true,
    },
    createOrganizationEnabled: {
      type: "boolean",
      label: "Create Organization Enabled",
      description: "If true, the user can create organizations with the Frontend API.",
      optional: true,
    },
    createdAt: {
      propDefinition: [
        clerk,
        "createdAt",
      ],
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      clerk,
      userId,
    } = this;

    const response = await clerk.updateUser({
      $,
      userId,
      data: {
        external_id: this.externalId,
        first_name: this.firstName,
        last_name: this.lastName,
        primary_email_address_id: this.primaryEmailAddressId,
        notify_primary_email_address_changed: this.notifyPrimaryEmailAddressChanged,
        primary_phone_number_id: this.primaryPhoneNumberId,
        primary_web3_wallet_id: this.primaryWeb3WalletId,
        username: this.username,
        profile_image_id: this.profileImageId,
        password: this.password,
        skip_password_checks: this.skipPasswordChecks,
        sign_out_of_other_sessions: this.signOutOfOtherSessions,
        totp_secret: this.totpSecret,
        backup_codes: parseObject(this.backupCodes),
        public_metadata: parseObject(this.publicMetadata),
        private_metadata: parseObject(this.privateMetadata),
        unsafe_metadata: parseObject(this.unsafeMetadata),
        delete_self_enabled: this.deleteSelfEnable,
        create_organization_enabled: this.createOrganizationEnabled,
        created_at: this.createdAt,
      },
    });

    $.export("$summary", `The user with Id: ${userId} was successfully updated!`);
    return response;
  },
};

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.
User Id	`userId`	`string`	Select a value from the drop down menu.
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.
Primary Email Address Id	`primaryEmailAddressId`	`string`	Select a value from the drop down menu.
Notify Primary Email Address Changed	`notifyPrimaryEmailAddressChanged`	`boolean`	If set to `true`, the user will be notified that their primary email address has changed. By default, no notification is sent.
Primary Phone Number Id	`primaryPhoneNumberId`	`string`	Select a value from the drop down menu.
Primary Web3 Wallet Id	`primaryWeb3WalletId`	`string`	Select a value from the drop down menu.
Username	`username`	`string`	The username to give to the user. It must be unique across your instance.
Profile Image Id	`profileImageId`	`string`	The ID of the image to set as the user's profile image
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.
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.
Sign Out Of Other Sessions	`signOutOfOtherSessions`	`boolean`	Set to `true` to sign out the user from all their active sessions once their password is updated. This parameter can only be used when providing a `password`.
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.`
Delete Self Enable	`deleteSelfEnable`	`boolean`	If `true`, the user can delete themselves with the Frontend API.
Create Organization Enabled	`createOrganizationEnabled`	`boolean`	If true, the user can create organizations with the Frontend API.
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 + Jotform#

Other Popular Integrations#

Create User with Clerk API on New Submission (Instant) from Jotform API

Jotform + Clerk

Try it

Create User Invitation with Clerk API on New Submission (Instant) from Jotform API

Jotform + Clerk

Try it

Delete User with Clerk API on New Submission (Instant) from Jotform API

Jotform + Clerk

Try it

Get User Memberships with Clerk API on New Submission (Instant) from Jotform API

Jotform + Clerk

Try it

Get User with Clerk API on New Submission (Instant) from Jotform API

Jotform + Clerk

Try it

Popular Triggers#

New Submission (Instant) from the Jotform API

Emit new event when a form is submitted

Try it

Popular Actions#

Get Form Submissions with the Jotform API

Gets a list of form responses See the docs here

Try it

Get Monthly User Usage with the Jotform API

Gets number of form submissions received this month. Also, get number of SSL form submissions, payment form submissions and upload space used by user See the docs here

Try it

Get User Submissions with the Jotform API

Gets a list of all submissions for all forms on the account See the 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