\u2757Note: <\/strong>Before you begin, you’ll need the Slack CLI installed and your new workspace authorized. Run Slack auth list to verify this.<\/p>\n\n\n<\/div>\n\n <\/a><\/p>\n\n\n\n Let\u2019s walk through the steps needed to create and integrate a Slack bot<\/a>.<\/p>\n\n\n\n To make it easy, we’ll describe the process with an example\u2014how to write a Slack bot that sends welcome text to new users. <\/strong>Please note that the process is more or less similar to other bot functions.<\/p>\n\n\n\n Each step requires some coding. But don\u2019t worry\u2014this guide will walk you through every detail to ensure you can create your chatbot without any hassle.<\/p>\n\n\n\n Before you dive into building your Slack bot, you’ll need the right tools in place. The first step involves creating your Slack app using the command-line interface (CLI).<\/p>\n\n\n\n Begin by setting up a blank app with the Slack CLI using this command: Running this command will create an app folder linked to your Slack account. Inside your new app folder, create three key directories that will serve as the foundation for your Slack bot:<\/p>\n\n\n\n With these folders and permissions in place, you\u2019re ready to start building your Slack app!<\/p>\n\n\n\n Alternatively, instead of writing all the code yourself, you can use the following command to create the Welcome Bot app directly:<\/p>\n\n\n\n Once your project is created, navigate to your project directory to customize your Slack bot.<\/p>\n\n\n\n The app manifest is your blueprint for the Slack bot. For a Welcome Bot, your manifest will include:<\/p>\n\n\n\n Workflows:<\/strong><\/p>\n\n\n\n Datastore:<\/strong><\/p>\n\n\n\n Scopes:<\/strong><\/p>\n\n\n\n When you bring all these components together, your manifest.ts file will resemble something like this:<\/p>\n\n\n\n First, we start by defining the workflow:<\/p>\n\n\n\n Here’s how the workflow definition will look:<\/p>\n\n\n\n Next, we add a form:<\/p>\n\n\n\n Here’s how to add the OpenForm function to your create_welcome_message.ts workflow:<\/p>\n\n\n\n Then, we add confirmation.<\/p>\n\n\n\n Add the following step to your create_welcome_message.ts workflow:<\/p>\n\n\n\n Start with creating a datastore.<\/p>\n\n\n\n In this file, you\u2019ll define the structure of the datastore where the text field welcome messages will be stored:<\/p>\n\n\n\n First, define the custom function.<\/p>\n\n\n\n Here\u2019s the code to define the custom function:<\/p>\n\n\n\n Next, add your required functionality.<\/p>\n\n\n\n Then, integrate the Slack bot into your workflow.<\/p>\n\n\n\n With this step, your workflow is now capable of:<\/p>\n\n\n\n First, create a link trigger.<\/p>\n\n\n\n Your code will look something like this.<\/p>\n\n\n\n Now, create the event trigger. This is essentially where you enable events that activate the bot. In this example, the bot user event trigger will be a new user joining a channel.<\/p>\n\n\n\n Here\u2019s the code to add.<\/p>\n\n\n\n Result:<\/p>\n\n\n\n This workflow retrieves the stored welcome message and sends it to the appropriate channel when a new user joins, enhancing engagement and automating the onboarding process.<\/p>\n\n\n\n 1. Define the custom function:<\/p>\n\n\n\n 2. Add function definition:<\/p>\n\n\n\n 3. Add functionality:<\/p>\n\n\n\n 4. Integrate custom function:<\/p>\n\n\n\n With this custom function, your Slack app settings will now send messages to any user who joins a private or public channel with a specific channel.<\/p>\n\n\n\n Congratulations on reaching the final step of building your Slack bot! Your bot will now automatically send messages to new users. Test it out to make sure it’s working properly on a public channel.<\/p>\n\n\n\n By now, you must have realized the convenience Slack bots bring to workplace communication<\/a>. After all, who doesn\u2019t love a little help with automation? <\/p>\n\n\n\n But there are a few limitations you should be wary of.<\/p>\n\n\n\n Knowing these limitations will allow you to make an informed decision about which workplace communication platform<\/a> is most efficient for you.<\/p>\n\n\n\n Slack bots can be a double-edged sword when it comes to focus.<\/p>\n\n\n\n Sure, it provides quick information and helps with tasks with a simple query. But it also comes with a barrage of notifications, from the bot’s token updates to team messages.<\/p>\n\n\n\n This constant distraction can hinder work. It often makes it difficult for your employees to prioritize work with the additional bot noise.<\/p>\n\n\n\n This is probably the biggest problem when it comes to communication tools like Slack<\/a>: they can become really expensive quickly.<\/p>\n\n\n\n Slack offers various plans, each with its own features, but as your team grows, so does the total cost of ownership for a SaaS product.<\/p>\n\n\n\n For example, the Pro plan costs $7.25 per user per month, which might seem reasonable initially. However, when you have a large team, these costs can quickly escalate, leading to a significant monthly expense. At that price, you can find Slack alternatives<\/a> that offer better features.<\/p>\n\n\n\n Slack bots, much like any other chatbot, rely on the data they have been trained with. If a bot user asks for information that hasn’t been integrated into the bot’s system, it will likely fail to provide a satisfactory response. <\/p>\n\n\n\n This means that your Slack bot will require constant updates to stay relevant and useful.<\/p>\n\n\n\n You’ll need to keep track of the most common questions being asked and regularly feed your Slack bot new, relevant information. This ongoing maintenance can become a significant workload, especially as your Slack workspace grows.<\/p>\n\n\n\n Slack has minimal storage capacity, and as these limits are reached, Slack automatically deletes older files and messages to make room for new ones.<\/p>\n\n\n\n This process can lead to the unintentional loss of important documents or communication history, especially if you’re using bots to automate tasks that generate a lot of data.<\/p>\n\n\n\n This is a no-brainer, but bots aren\u2019t usually the smartest tool in the shed. They lack critical thinking and the ability to approach a situation from different perspectives. <\/p>\n\n\n\n Therefore, in a sticky situation where problem-solving is required, you cannot depend on your Slack bot to provide unique solutions.<\/p>\n\n\n\n If you think Slack is an efficient communication tool, wait until you integrate it with ClickUp<\/a>.<\/p>\n\n\n\n Together, Slack and ClickUp form the ultimate dream team<\/a> in a collaborative environment.<\/p>\n\n\n\n Let’s explore how different teams can benefit from this integration while keeping Slack etiquette in mind.<\/p>\n\n\n\n Once you’ve integrated ClickUp with Slack<\/a>, you can sync all your ClickUp activity with your Slack workspace for specific spaces, folders, and lists. <\/p>\n\n\n\n Your ClickUp activities will be automatically sent as messages to your Slack channel. You can select public or private channels where ClickUp can access these notifications. <\/p>\n\n\n To grant ClickUp access to a private channel, use the \/invite @ClickUp command.<\/p>\n\n\n How does this help?<\/p>\n\n\n\n Imagine you’re part of a marketing team working on a high-stakes campaign with a tight deadline. This integration removes the need to update your team members<\/a> on your progress manually. <\/p>\n\n\n\n Instead, ClickUp automatically sends updates to your Slack channel, giving everyone a 360-degree view of where the project currently stands. <\/p>\n\n\n\n Similarly, critical updates from the tech teams\u2014like bug fixes, feature deployments, or server maintenance tasks\u2014are immediately shared with the team in real time.<\/p>\n\n\n\n When you link tasks, comments, or Docs in Slack, you’ll see a preview of each item, a process referred to as “unfurling.” This feature lets your team view details like task status, assignees, priorities, and more directly in Slack. <\/p>\n\n\n For instance, say a sales team has created a Slack channel to discuss a key account. When a task related to this account is shared on Slack, everyone can immediately see who\u2019s assigned, what the priority is, and the current status. <\/p>\n\n\n\n Now, sales reps (or any other team) can respond quickly to client needs without digging through multiple apps.<\/p>\n\n\n\n You can create ClickUp tasks directly from Slack by using a \/Slash command like \/clickup new<\/strong> or adding a Slack message as a comment to an existing task. <\/p>\n\n\n\n This is particularly helpful when delegating tasks. Imagine the marketing head likes a creative idea shared in the Slack chat; they can instantly turn that message into a task in ClickUp without ever leaving Slack. <\/p>\n\n\n Also read:<\/strong> The DOs and DON\u2019Ts of Using Slack at Work<\/a><\/p>\n\n\n<\/div>\n\n\n At the end of the day, you\u2019re using Slack to communicate effectively with your team<\/a> and across departments. But communication is more streamlined, effective, and intuitive on ClickUp. Let\u2019s explore more. <\/p>\n\n\n\n ClickUp\u2019s Chat View<\/a> lets your team engage in real-time conversations<\/a> without leaving the platform. <\/p>\n\n\n\n Whether you’re an IT team troubleshooting an urgent issue or a sales team discussing a new lead, the Chat View keeps all your communications centralized. <\/p>\n\n\n\n Marketing teams particularly struggle with scattered conversations across different apps. On ClickUp, you can brainstorm ideas, share creative briefs, and make quick decisions\u2014all within the same workspace. <\/p>\n\n\n\n And when it\u2019s time to turn those ideas into action, ClickUp lets you do it right from the chat. Assign tasks, set deadlines, and move projects forward without leaving the conversation.<\/p>\n\n\n\n Need to brainstorm a strategy or plan a project? ClickUp\u2019s Whiteboards<\/a> offer a virtual space where teams can visually collaborate. <\/p>\n\n\n\n While Slack lets you brainstorm with your teammates through text-based discussions, ClickUp Whiteboards take your projects to the next level by allowing your team to draw, annotate, and turn ideas into actionable tasks on the board. <\/p>\n\n\n\n If you\u2019re part of an engineering team that needs to map out workflows or a project manager handling a complex project timeline, this will become your new favorite tool.<\/p>\n\n\n\n One of ClickUp\u2019s standout features is the ability to assign comments to specific team members using @mentions<\/strong>. If you’re discussing a critical update in Chat View, you can instantly tag a team member and turn that comment into a task.<\/p>\n\n\n\n For example, during a product development meeting, an engineering lead can assign a bug fix directly from the chat, ensuring nothing slips through the cracks.<\/p>\n\n\n\n Are you a visual learner? If yes, ClickUp Clips<\/a> is about to enhance your experience tenfold by allowing you to record and share screen recordings<\/a>. <\/p>\n\n\n\n Imagine an IT team recording a step-by-step guide for troubleshooting a common issue\u2014team members can access this clip anytime, making it easier for them to understand and implement changes.<\/p>\n\n\n\nHow to Make Your Own Slack Chatbot<\/h2>\n\n\n\n
Step 1: Create a Slack app using the CLI<\/h3>\n\n\n\n
slack create welcome-bot-app –template https:\/\/github.com\/slack-samples\/deno-welcome-bot<\/strong><\/p>\n\n\n\n\n
slack create welcome-bot-app --template https:\/\/github.com\/slack-samples\/deno-welcome-bot<\/pre>\n\n\n\n
Step 2: Create the app mandate<\/h3>\n\n\n\n
\n
\n
\n
\/\/ \/manifest.ts\nimport { Manifest } from \"deno-slack-sdk\/mod.ts\";\nimport { WelcomeMessageDatastore } from \".\/datastores\/messages.ts\";\nimport { MessageSetupWorkflow } from \".\/workflows\/create_welcome_message.ts\";\nimport { SendWelcomeMessageWorkflow } from \".\/workflows\/send_welcome_message.ts\";\nexport default Manifest({\n\u00a0\u00a0name: \"Welcome Message Bot\",\n\u00a0\u00a0description:\n\u00a0\u00a0\u00a0\u00a0\"Quick way to setup automated welcome messages for channels in your workspace.\",\n\u00a0\u00a0icon: \"assets\/default_new_app_icon.png\",\n\u00a0\u00a0workflows: [MessageSetupWorkflow, SendWelcomeMessageWorkflow],\n\u00a0\u00a0outgoingDomains: [],\n\u00a0\u00a0datastores: [WelcomeMessageDatastore],\n\u00a0\u00a0botScopes: [\n\u00a0\u00a0\u00a0\u00a0\"chat:write\",\n\u00a0\u00a0\u00a0\u00a0\"chat:write.public\",\n\u00a0\u00a0\u00a0\u00a0\"datastore:read\",\n\u00a0\u00a0\u00a0\u00a0\"datastore:write\",\n\u00a0\u00a0\u00a0\u00a0\"channels:read\",\n\u00a0\u00a0\u00a0\u00a0\"triggers:write\",\n\u00a0\u00a0\u00a0\u00a0\"triggers:read\",\n\u00a0\u00a0],\n});<\/pre>\n\n\n\nStep 3: Create a workflow for setting up the welcome message<\/h3>\n\n\n\n
\n
\/\/ \/workflows\/create_welcome_message.ts\nimport { DefineWorkflow, Schema } from \"deno-slack-sdk\/mod.ts\";\nimport { WelcomeMessageSetupFunction } from \"..\/functions\/create_welcome_message.ts\";\n\/**\n\u00a0* The MessageSetupWorkflow opens a form where the user creates a\n\u00a0* welcome message. The trigger for this workflow is found in\n\u00a0* `\/triggers\/welcome_message_trigger.ts`\n\u00a0*\/\nexport const MessageSetupWorkflow = DefineWorkflow({\n\u00a0\u00a0callback_id: \"message_setup_workflow\",\n\u00a0\u00a0title: \"Create Welcome Message\",\n\u00a0\u00a0description: \" Creates a message to welcome new users into the channel.\",\n\u00a0\u00a0input_parameters: {\n\u00a0\u00a0\u00a0\u00a0properties: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0interactivity: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.interactivity,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0required: [\"interactivity\"],\n\u00a0\u00a0},\n});<\/pre>\n\n\n\n\n
\/\/ \/workflows\/create_welcome_message.ts\n\/**\n\u00a0* This step uses the OpenForm Slack function. The form has two\n\u00a0* inputs -- a welcome message and a channel id for that message to\n\u00a0* be posted in.\n\u00a0*\/\nconst SetupWorkflowForm = MessageSetupWorkflow.addStep(\n\u00a0\u00a0Schema.slack.functions.OpenForm,\n\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0title: \"Welcome Message Form\",\n\u00a0\u00a0\u00a0\u00a0submit_label: \"Submit\",\n\u00a0\u00a0\u00a0\u00a0description: \":wave: Create a welcome message for a channel!\",\n\u00a0\u00a0\u00a0\u00a0interactivity: MessageSetupWorkflow.inputs.interactivity,\n\u00a0\u00a0\u00a0\u00a0fields: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0required: [\"channel\", \"messageInput\"],\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0elements: [\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0name: \"messageInput\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0title: \"Your welcome message\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.types.string,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0long: true,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0name: \"channel\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0title: \"Select a channel to post this message in\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0default: MessageSetupWorkflow.inputs.channel,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0],\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0},\n);<\/pre>\n\n\n\n\/\/ \/workflows\/create_welcome_message.ts\n\/**\n\u00a0* This step takes the form output and passes it along to a custom\n\u00a0* function which sets the welcome message up.\n\u00a0* See `\/functions\/setup_function.ts` for more information.\n\u00a0*\/\nMessageSetupWorkflow.addStep(WelcomeMessageSetupFunction, {\n\u00a0\u00a0message: SetupWorkflowForm.outputs.fields.messageInput,\n\u00a0\u00a0channel: SetupWorkflowForm.outputs.fields.channel,\n\u00a0\u00a0author: MessageSetupWorkflow.inputs.interactivity.interactor.id,\n});\n\/**\n\u00a0* This step uses the SendEphemeralMessage Slack function.\n\u00a0* An ephemeral confirmation message will be sent to the user\n\u00a0* creating the welcome message, after the user submits the above\n\u00a0* form.\n\u00a0*\/\nMessageSetupWorkflow.addStep(Schema.slack.functions.SendEphemeralMessage, {\n\u00a0\u00a0channel_id: SetupWorkflowForm.outputs.fields.channel,\n\u00a0\u00a0user_id: MessageSetupWorkflow.inputs.interactivity.interactor.id,\n\u00a0\u00a0message:\n\u00a0\u00a0\u00a0\u00a0`Your welcome message for this channel was successfully created! :white_check_mark:`,\n});\nexport default MessageSetupWorkflow;<\/pre>\n\n\n\nStep 4: Use a datastore to store the welcome message<\/h3>\n\n\n\n
\n
\/\/ \/datastores\/messages.ts\nimport { DefineDatastore, Schema } from \"deno-slack-sdk\/mod.ts\";\n\/**\n\u00a0* Datastores are a Slack-hosted location to store\n\u00a0* and retrieve data for your app.\n\u00a0* https:\/\/api.slack.com\/automation\/datastores\n\u00a0*\/\nexport const WelcomeMessageDatastore = DefineDatastore({\n\u00a0\u00a0name: \"messages\",\n\u00a0\u00a0primary_key: \"id\",\n\u00a0\u00a0attributes: {\n\u00a0\u00a0\u00a0\u00a0id: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.types.string,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0message: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.types.string,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0author: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.user_id,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0},\n});<\/pre>\n\n\n\nStep 5: Create a custom function to store the welcome message in the datastore<\/h3>\n\n\n\n
\n
\/\/ \/functions\/create_welcome_message.ts\nimport { DefineFunction, Schema, SlackFunction } from \"deno-slack-sdk\/mod.ts\";\nimport { SlackAPIClient } from \"deno-slack-sdk\/types.ts\";\nimport { SendWelcomeMessageWorkflow } from \"..\/workflows\/send_welcome_message.ts\";\nimport { WelcomeMessageDatastore } from \"..\/datastores\/messages.ts\";\n\/**\n\u00a0* This custom function will take the initial form input, store it\n\u00a0* in the datastore and create an event trigger to listen for\n\u00a0* user_joined_channel events in the specified channel.\n\u00a0*\/\nexport const WelcomeMessageSetupFunction = DefineFunction({\n\u00a0\u00a0callback_id: \"welcome_message_setup_function\",\n\u00a0\u00a0title: \"Welcome Message Setup\",\n\u00a0\u00a0description: \"Takes a welcome message and stores it in the datastore\",\n\u00a0\u00a0source_file: \"functions\/create_welcome_message.ts\",\n\u00a0\u00a0input_parameters: {\n\u00a0\u00a0\u00a0\u00a0properties: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0message: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.types.string,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0description: \"The welcome message\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0description: \"Channel to post in\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0author: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.user_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0description:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"The user ID of the person who created the welcome message\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0required: [\"message\", \"channel\"],\n\u00a0\u00a0},\n});<\/pre>\n\n\n\n\n
\/\/ \/functions\/create_welcome_message.ts\nexport default SlackFunction(\n\u00a0\u00a0WelcomeMessageSetupFunction,\n\u00a0\u00a0async ({ inputs, client }) => {\n\u00a0\u00a0\u00a0\u00a0const { channel, message, author } = inputs;\n\u00a0\u00a0\u00a0\u00a0const uuid = crypto.randomUUID();\n\u00a0\u00a0\u00a0\u00a0\/\/ Save information about the welcome message to the datastore\n\u00a0\u00a0\u00a0\u00a0const putResponse = await client.apps.datastore.put<\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0typeof WelcomeMessageDatastore.definition\n\u00a0\u00a0\u00a0\u00a0>({\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0datastore: WelcomeMessageDatastore.name,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0item: { id: uuid, channel, message, author },\n\u00a0\u00a0\u00a0\u00a0});\n\u00a0\u00a0\u00a0\u00a0if (!putResponse.ok) {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return { error: `Failed to save welcome message: ${putResponse.error}` };\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0\/\/ Search for any existing triggers for the welcome workflow\n\u00a0\u00a0\u00a0\u00a0const triggers = await findUserJoinedChannelTrigger(client, channel);\n\u00a0\u00a0\u00a0\u00a0if (triggers.error) {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return { error: `Failed to lookup existing triggers: ${triggers.error}` };\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0\/\/ Create a new user_joined_channel trigger if none exist\n\u00a0\u00a0\u00a0\u00a0if (!triggers.exists) {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0const newTrigger = await saveUserJoinedChannelTrigger(client, channel);\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0if (!newTrigger.ok) {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0error: `Failed to create welcome trigger: ${newTrigger.error}`,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0};\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0return { outputs: {} };\n\u00a0\u00a0},\n);<\/pre>\n\n\n\n\n
\/\/ \/workflows\/create_welcome_message.ts\n\/**\n\u00a0* This step takes the form output and passes it along to a custom\n\u00a0* function which sets the welcome message up.\n\u00a0* See `\/functions\/setup_function.ts` for more information.\n\u00a0*\/\nMessageSetupWorkflow.addStep(WelcomeMessageSetupFunction, {\n\u00a0\u00a0message: SetupWorkflowForm.outputs.fields.messageInput,\n\u00a0\u00a0channel: SetupWorkflowForm.outputs.fields.channel,\n\u00a0\u00a0author: MessageSetupWorkflow.inputs.interactivity.interactor.id,\n});\nexport default MessageSetupWorkflow;<\/pre>\n\n\n\n\n
Step 6: Create triggers to activate workflows<\/h3>\n\n\n\n
\n
\/\/ triggers\/create_welcome_message_shortcut.ts\nimport { Trigger } from \"deno-slack-api\/types.ts\";\nimport MessageSetupWorkflow from \"..\/workflows\/create_welcome_message.ts\";\nimport { TriggerContextData, TriggerTypes } from \"deno-slack-api\/mod.ts\";\n\/**\n\u00a0* This link trigger prompts the MessageSetupWorkflow workflow.\n\u00a0*\/\nconst welcomeMessageTrigger: Trigger<typeof MessageSetupWorkflow.definition> = {\n\u00a0\u00a0type: TriggerTypes.Shortcut,\n\u00a0\u00a0name: \"Setup a Welcome Message\",\n\u00a0\u00a0description: \"Creates an automated welcome message for a given channel.\",\n\u00a0\u00a0workflow: `#\/workflows\/${MessageSetupWorkflow.definition.callback_id}`,\n\u00a0\u00a0inputs: {\n\u00a0\u00a0\u00a0\u00a0interactivity: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0value: TriggerContextData.Shortcut.interactivity,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0value: TriggerContextData.Shortcut.channel_id,\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0},\n};\nexport default welcomeMessageTrigger;<\/pre>\n\n\n\n\n
\/\/ \/functions\/create_welcome_message.ts\n\/**\n\u00a0* findUserJoinedChannelTrigger returns if the user_joined_channel trigger\n\u00a0* exists for the \"Send Welcome Message\" workflow in a channel.\n\u00a0*\/\nexport async function findUserJoinedChannelTrigger(\n\u00a0\u00a0client: SlackAPIClient,\n\u00a0\u00a0channel: string,\n): Promise<{ error?: string; exists?: boolean }> {\n\u00a0\u00a0\/\/ Collect all existing triggers created by the app\n\u00a0\u00a0const allTriggers = await client.workflows.triggers.list({ is_owner: true });\n\u00a0\u00a0if (!allTriggers.ok) {\n\u00a0\u00a0\u00a0\u00a0return { error: allTriggers.error };\n\u00a0\u00a0}\n\u00a0\u00a0\/\/ Find user_joined_channel triggers for the \"Send Welcome Message\"\n\u00a0\u00a0\/\/ workflow in the specified channel\n\u00a0\u00a0const joinedTriggers = allTriggers.triggers.filter((trigger) => (\n\u00a0\u00a0\u00a0\u00a0trigger.workflow.callback_id ===\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0SendWelcomeMessageWorkflow.definition.callback_id &&\n\u00a0\u00a0\u00a0\u00a0trigger.event_type === \"slack#\/events\/user_joined_channel\" &&\n\u00a0\u00a0\u00a0\u00a0trigger.channel_ids.includes(channel)\n\u00a0\u00a0));\n\u00a0\u00a0\/\/ Return if any matching triggers were found\n\u00a0\u00a0const exists = joinedTriggers.length > 0;\n\u00a0\u00a0return { exists };\n}\n\/**\n\u00a0* saveUserJoinedChannelTrigger creates a new user_joined_channel trigger\n\u00a0* for the \"Send Welcome Message\" workflow in a channel.\n\u00a0*\/\nexport async function saveUserJoinedChannelTrigger(\n\u00a0\u00a0client: SlackAPIClient,\n\u00a0\u00a0channel: string,\n): Promise<{ ok: boolean; error?: string }> {\n\u00a0\u00a0const triggerResponse = await client.workflows.triggers.create<\n\u00a0\u00a0\u00a0\u00a0typeof SendWelcomeMessageWorkflow.definition\n\u00a0\u00a0>({\n\u00a0\u00a0\u00a0\u00a0type: \"event\",\n\u00a0\u00a0\u00a0\u00a0name: \"User joined channel\",\n\u00a0\u00a0\u00a0\u00a0description: \"Send a message when a user joins the channel\",\n\u00a0\u00a0\u00a0\u00a0workflow:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0`#\/workflows\/${SendWelcomeMessageWorkflow.definition.callback_id}`,\n\u00a0\u00a0\u00a0\u00a0event: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0event_type: \"slack#\/events\/user_joined_channel\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel_ids: [channel],\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0inputs: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: { value: channel },\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0triggered_user: { value: \"{{data.user_id}}\" },\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0});\n\u00a0\u00a0if (!triggerResponse.ok) {\n\u00a0\u00a0\u00a0\u00a0return { ok: false, error: triggerResponse.error };\n\u00a0\u00a0}\n\u00a0\u00a0return { ok: true };\n}<\/pre>\n\n\n\n\n
Step 7: Create a workflow for sending the welcome message<\/h3>\n\n\n\n
\n
\/\/ \/workflows\/send_welcome_message.ts\nimport { DefineWorkflow, Schema } from \"deno-slack-sdk\/mod.ts\";\nimport { SendWelcomeMessageFunction } from \"..\/functions\/send_welcome_message.ts\";\n\/**\n\u00a0* The SendWelcomeMessageWorkFlow will retrieve the welcome message\n\u00a0* from the datastore and send it to the specified channel, when\n\u00a0* a new user joins the channel.\n\u00a0*\/\nexport const SendWelcomeMessageWorkflow = DefineWorkflow({\n\u00a0\u00a0callback_id: \"send_welcome_message\",\n\u00a0\u00a0title: \"Send Welcome Message\",\n\u00a0\u00a0description:\n\u00a0\u00a0\u00a0\u00a0\"Posts an ephemeral welcome message when a new user joins a channel.\",\n\u00a0\u00a0input_parameters: {\n\u00a0\u00a0\u00a0\u00a0properties: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0triggered_user: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.user_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0required: [\"channel\", \"triggered_user\"],\n\u00a0\u00a0},\n});<\/pre>\n\n\n\nStep 8: Create a custom function to send the welcome message<\/h3>\n\n\n\n
\n
\/\/ \/functions\/send_welcome_message.ts\nimport { DefineFunction, Schema, SlackFunction } from \"deno-slack-sdk\/mod.ts\";\nimport { WelcomeMessageDatastore } from \"..\/datastores\/messages.ts\";\n\/**\n\u00a0* This custom function will pull the stored message from the datastore\n\u00a0* and send it to the joining user as an ephemeral message in the\n\u00a0* specified channel.\n\u00a0*\/\nexport const SendWelcomeMessageFunction = DefineFunction({\n\u00a0\u00a0callback_id: \"send_welcome_message_function\",\n\u00a0\u00a0title: \"Sending the Welcome Message\",\n\u00a0\u00a0description: \"Pull the welcome messages and sends it to the new user\",\n\u00a0\u00a0source_file: \"functions\/send_welcome_message.ts\",\n\u00a0\u00a0input_parameters: {\n\u00a0\u00a0\u00a0\u00a0properties: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.channel_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0description: \"Channel where the event was triggered\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0triggered_user: {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0type: Schema.slack.types.user_id,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0description: \"User that triggered the event\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0},\n\u00a0\u00a0\u00a0\u00a0required: [\"channel\", \"triggered_user\"],\n\u00a0\u00a0},\n});<\/pre>\n\n\n\n\n
\/\/ \/functions\/send_welcome_message.ts\nexport default SlackFunction(SendWelcomeMessageFunction, async (\n\u00a0\u00a0{ inputs, client },\n) => {\n\u00a0\u00a0\/\/ Querying datastore for stored messages\n\u00a0\u00a0const messages = await client.apps.datastore.query<\n\u00a0\u00a0\u00a0\u00a0typeof WelcomeMessageDatastore.definition\n\u00a0\u00a0>({\n\u00a0\u00a0\u00a0\u00a0datastore: WelcomeMessageDatastore.name,\n\u00a0\u00a0\u00a0\u00a0expression: \"#channel = :mychannel\",\n\u00a0\u00a0\u00a0\u00a0expression_attributes: { \"#channel\": \"channel\" },\n\u00a0\u00a0\u00a0\u00a0expression_values: { \":mychannel\": inputs.channel },\n\u00a0\u00a0});\n\u00a0\u00a0if (!messages.ok) {\n\u00a0\u00a0\u00a0\u00a0return { error: `Failed to gather welcome messages: ${messages.error}` };\n\u00a0\u00a0}\n\u00a0\u00a0\/\/ Send the stored messages ephemerally\n\u00a0\u00a0for (const item of messages[\"items\"]) {\n\u00a0\u00a0\u00a0\u00a0const message = await client.chat.postEphemeral({\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0channel: item[\"channel\"],\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0text: item[\"message\"],\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0user: inputs.triggered_user,\n\u00a0\u00a0\u00a0\u00a0});\n\u00a0\u00a0\u00a0\u00a0if (!message.ok) {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return { error: `Failed to send welcome message: ${message.error}` };\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0}\n\u00a0\u00a0return {\n\u00a0\u00a0\u00a0\u00a0outputs: {},\n\u00a0\u00a0};\n});<\/pre>\n\n\n\n\n
\/\/ \/workflows\/send_welcome_message.ts\nSendWelcomeMessageWorkflow.addStep(SendWelcomeMessageFunction, {\n\u00a0\u00a0channel: SendWelcomeMessageWorkflow.inputs.channel,\n\u00a0\u00a0triggered_user: SendWelcomeMessageWorkflow.inputs.triggered_user,\n});<\/pre>\n\n\n\nStep 9: Use your Slack app<\/h3>\n\n\n\n
1. Run your Slack app locally<\/h4>\n\n\n\n
\n
\n
\n
\n
\ud83d\udcda App Manifest\n Created app manifest for \"welcomebot (local)\" in \"myworkspace\" workspace\n\u26a0\ufe0f Outgoing domains\n No allowed outgoing domains are configured\n If your function makes network requests, you will need to allow the outgoing domains\n Learn more about upcoming changes to outgoing domains: https:\/\/api.slack.com\/changelog\n\ud83c\udfe0 Workspace Install\n Installed \"welcomebot (local)\" app to \"myworkspace\" workspace\n Finished in 1.5s\n\u26a1 Trigger created\n Trigger ID: Ft0123ABC456\n Trigger Type: shortcut\n Trigger Name: Setup a Welcome Message\n Shortcut URL: \nhttps:\/\/slack.com\/shortcuts\/Ft0123ABC456\/XYZ123\n...\n<\/pre>\n\n\n\n
2. Launch your Slack app<\/h4>\n\n\n\n
\n
\n
\n
\n
\n
\n
Step 10: Your Slack bot is ready!<\/h3>\n\n\n\n
![\"Slackbot\"](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/Slackbot.png\")
<\/figure>\n\n\n\nLimitations of Using Slack Bots for Communication<\/h2>\n\n\n\n
1. Slack bots can be distracting<\/h3>\n\n\n\n
2. Slack can be expensive, and so can its bots<\/h3>\n\n\n\n
3. Slack bots need maintenance <\/h3>\n\n\n\n
4. Bots can eat up space<\/h3>\n\n\n\n
5. Slack bots aren\u2019t creative <\/h3>\n\n\n\n
Enhancing Team Communication with ClickUp and Slack<\/h2>\n\n\n\n
Enable ClickUp activity sync with Slack<\/h3>\n\n\n\n
![\"Sync](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/ClickUp-with-Slackbot.png\")
![\"ClickUp](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/slack-bot.png\")
Tasks, comments, and docs, all on your Slack screen<\/h3>\n\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/Slack-bot-2.png\")
Turn messages into tasks<\/h3>\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/Slackbot-1.png\")
ClickUp Does What Slack Can, and More<\/h2>\n\n\n\n
Real-time conversations with chat view<\/h3>\n\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/slackbot-2-1.png\")
<\/figure>\n\n\n\nCollaboration, brainstorming, and whiteboards<\/h3>\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/image-362.png\")
Task management with Assigned Comments<\/h3>\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/slackbot-3.png\")
Visual communication with ClickUp Clips<\/h3>\n\n\n
![\"How](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/09\/image-42.gif\")
Strategize actions with templates<\/h3>\n\n\n\n
![\"ClickUp](\"https:\/\/clickup.com\/blog\/wp-content\/uploads\/2024\/08\/image-416.png\")