Create User with Clerk API on New Message In Channels (Instant) from Slack API

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

Trigger workflow on

New Message In Channels (Instant) from the Slack 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 Slack 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 Message In Channels (Instant) trigger
1. Connect your Slack account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
6. Optional- Configure Ignore replies in threads
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 Message In Channels (Instant) on Slack

Description:Emit new event when a new message is posted to one or more channels

Version:1.0.22

Key:slack-new-message-in-channels

View on GitHub

Slack Overview#

The Pipedream Slack app enables you to build event-driven workflows that interact with the Slack API. Once you authorize the Pipedream app's access to your workspace, you can use Pipedream workflows to perform common Slack actions or write your own code against the Slack API.

The Pipedream Slack app is not a typical app. You don't interact with it directly as a bot, and it doesn't add custom functionality to your workspace out of the box. It makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Automate posting updates to your team channels
Create a bot to answer common questions
Integrate with your existing tools and services
And much more!

Trigger Code#

import common from "../common/base.mjs";
import constants from "../common/constants.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.22",
  description: "Emit new event when a new message is posted to one or more channels",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    conversations: {
      propDefinition: [
        common.props.slack,
        "conversation",
      ],
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
    },
    // eslint-disable-next-line pipedream/props-description,pipedream/props-label
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [
          "message",
        ];
      },
    },
    resolveNames: {
      propDefinition: [
        common.props.slack,
        "resolveNames",
      ],
    },
    ignoreBot: {
      propDefinition: [
        common.props.slack,
        "ignoreBot",
      ],
    },
    ignoreThreads: {
      type: "boolean",
      label: "Ignore replies in threads",
      description: "Ignore replies to messages in threads",
      optional: true,
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New message in channel";
    },
    async processEvent(event) {
      if (event.type !== "message") {
        console.log(`Ignoring event with unexpected type "${event.type}"`);
        return;
      }
      if (event.subtype && !constants.ALLOWED_MESSAGE_IN_CHANNEL_SUBTYPES.includes(event.subtype)) {
        // This source is designed to just emit an event for each new message received.
        // Due to inconsistencies with the shape of message_changed and message_deleted
        // events, we are ignoring them for now. If you want to handle these types of
        // events, feel free to change this code!!
        console.log("Ignoring message with subtype.");
        return;
      }
      if ((this.ignoreBot) && (event.subtype == "bot_message" || event.bot_id)) {
        return;
      }
      // There is no thread message type only the thread_ts field
      // indicates if the message is part of a thread in the event.
      if (this.ignoreThreads && event.thread_ts) {
        console.log("Ignoring reply in thread");
        return;
      }
      if (this.resolveNames) {
        if (event.user) {
          event.user_id = event.user;
          event.user = await this.getUserName(event.user);
        } else if (event.bot_id) {
          event.bot = await this.getBotName(event.bot_id);
        }
        event.channel_id = event.channel;
        event.channel = await this.getConversationName(event.channel);
        if (event.team) {
          event.team_id = event.team;
          event.team = await this.getTeamName(event.team);
        }
      }
      return event;
    },
  },
  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
Slack	`slack`	`app`	This component uses the Slack app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`conversations`	`string[]`	Select a value from the drop down menu.
	`slackApphook`	`$.interface.apphook`
Resolve Names	`resolveNames`	`boolean`	Instead of returning `channel`, `team`, and `user` as IDs, return their human-readable names.
Ignore Bots	`ignoreBot`	`boolean`	Ignore messages from bots
Ignore replies in threads	`ignoreThreads`	`boolean`	Ignore replies to messages in threads

Trigger Authentication#

Slack uses OAuth authentication. When you connect your Slack account, Pipedream will open a popup window where you can sign into Slack and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Slack API.

Pipedream requests the following authorization scopes when you connect your account:

bookmarks:writecalls:readcalls:writechannels:historychannels:readchannels:writednd:readdnd:writeemoji:readfiles:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writepins:readpins:writereactions:readreactions:writereminders:readreminders:writeremote_files:readremote_files:sharestars:readstars:writeteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:usercommandsfiles:write:userusers.profile:writeusers.profile:readsearch:read

About Slack#

Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.

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`).

Create User with Clerk API on New Message In Channels (Instant) from Slack API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular