Our future generation platform is in closed beta. During the beta, expect some rough edges, broken windows overlooking blue sky vistas, and regularly scheduled changes.

Already signed up? Great! You can ignore this.
Need to sign up? Apply to join the beta.

Beta FAQ

Our next-generation platform evolves regularly and you can expect new "releases" every two weeks or so. Occasionally, we get so excited about features we know are coming around the bend that we might document them early and confuse the heck out of folks. For this, and other reasons, we put together this FAQ and errata reference.

FAQ

Some of these questions we've seen frequently asked internally or by alpha and beta developers but to tell you the truth most FAQs are made up of questions you imagine people having. If we're missing a glory of gotchas, please do let us know.

What are the requirements to join the beta?

Any Slack customer on any paid plan can sign up for the beta.

How do I set up my developer environment?

First, make sure you've applied and been granted access to the future generation platform private beta. The workspace you use when applying will become the workspace enabled for the beta.

After receiving beta approval, head to the Quickstart guide to use our automated installer script— or download the latest version of the slack CLI and follow instructions to install it manually.

Using a combination of your favorite text editor, the slack CLI tool, and the included future generation SDK, you will program in TypeScript for a Deno-based runtime.

Start with our Quickstart to go through the entire process.

How do I add the slack CLI to my path?

If you're on Mac or Linux, consider using the automated installer script in the Quickstart guide to get your workstation ready to start using slack right away.

To add the program to your path manually:

Mac/Linux: Copy the CLI into any folder that is already in your path—such as /usr/local/bin—or add a new folder to your path by listing whatever folder you installed the CLI to in /etc/paths.

Windows: Copy the CLI into any folder that is already in your path, or add a new folder to your path by listing whatever folder you installed teh CLI to in your Environment Variables. You may not have access to edit System variables, so you might need to add it to your account's User variables.

On Windows, you can open the Environment Variables dialog by pressing the Win+R keys to open the Run window, and entering the following command: rundll32.exe sysdm.cpl,EditEnvironmentVariables.

The CLI is throwing the following error: TypeError: Deno.emit is not a function

This may be due to a recently deprecated Deno feature. For example, when Deno released v1.22, the function Deno.emit() was removed. If you have already upgraded Deno to the latest version, you'll need to use the specific version supported by the Slack SDK: 1.21.3. This should be resolved in our next minor CLI release.

You can specify which version of Deno you use with deno upgrade:

$ deno upgrade --version 1.21.3

How do I build a slash command in the future generation platform?

Slash commands as they've been known in previous generations of the platform are not part of the new platform. You can, however, still invoke your app by pulling up the Shortcut menu with the slash (/) key and typing the name of your Shortcut. Think of Shortcuts as the modern version of Slash commands; they have a similar front-end (where you can invoke them /like this) but are more robust on the back-end. We may refer to this clever way of executing a shortcut as a slash command, especially to end users, so fear not fellow slash commandos.

What about my Tables and the data in them?

Tables were an early beta feature that have since been supplanted by Datastores.

We will keep your tables and the API routes to access them (apps.tables.*) for two weeks. Please use this time to extract any data that you would like to extract via the API. We've put together some scripts to help the migration process.

What languages are supported?

At this time, apps that run on Slack are built with Typescript in a Deno runtime environment.

Errata

Deployment and installation

  • Workspace owners and administrators cannot run slack deploy to deploy apps when a workspace has admin-approved apps turned on. Use an alternative non-admin or non-owner account to build, test, and deploy beta apps.
  • JSON or YAML-based app manifests are no longer how your app's configuration is canonically defined. Instead, both your app's configuration and your function definitions will reside in manifest.ts.