This automations page is moving! We've been working hard at building out our tools documentation at tools.slack.dev β€” the new home of our Deno Slack SDK and Slack CLI docs! You can start using the new docs today, but we'll keep the content on both sites up to date during the transition.

Deploy to Slack

Developing automations requires a paid plan. Don't have one? Join the Developer Program and provision a sandbox with access to all Slack features for free.

Your apps can be deployed to Slack's managed infrastructure by running the slack deploy command at the root of your project.

npm dependencies are supported but are still in beta, so ensure that you test any npm: specifiers when using the slack deploy command (the slack run command is not affected).

No local development server is started when running the slack deploy command, and your app will have a different ID than the one created for your app if you previously ran the slack run command. For more details about the differences between local and deployed apps, refer to team collaboration.

Using the slack deploy command

When you run the slack deploy command and you are logged into a Slack Enterprise Grid, you may also be asked to select a workspace within your organization to deploy your app to (default is all workspaces).

You may also specify a workspace within your organization to grant your app access to with the --org-workspace-grant flag.

The Slack CLI will package up your app and deploy it to the workspace you specify. At that point, anyone in your workspace will be able to find and add your app by navigating to Apps > Manage > Browse apps.

The slack deploy command behavior may vary slightly based on the operating system used.

Function access

To make a function available so that another user (or group of users) can access workflows that reference your function after you deploy your app, you can execute the slack function access command. After choosing your workspace, you'll also be prompted to select which function you want to deploy, as well as who you would like to give access to your function -- app collaborators only, specific users, or everyone. Your function will then be accessible to those users the next time you deploy your app.

✨ For more information about function access, refer to custom function access.

Workflow apps are currently not eligible for distributing to the Slack Marketplace.

Redeploying your app

If you need to make any changes to your app, you must redeploy it using the slack deploy command again.

In addition, if administrators of your workspace have enabled Admin-Approved Apps, it means your app will need approval before it can be deployed or redeployed to your workspace.

✨ For more information about getting your app approved, check out access controls for developers.


Have 2 minutes to provide some feedback?

We'd love to hear about your experience building Slack automations. Please complete our short survey so we can use your feedback to improve.