This is a scaffolded Deno template used to build out Slack apps using the Slack CLI.

Guide Outline:

• Setup
  • Install the Slack CLI
  • Clone the Template
• Create a Link Trigger
• Running Your Project Locally
• Datastores
• Testing
• Deploying Your App
  • Viewing Activity Logs
• Project Structure
• Resources

Before getting started, make sure you have a development workspace where you have permissions to install apps. If you don’t have one set up, go ahead and create one. Also, please note that the workspace requires any of the Slack paid plans.

To use this template, you first need to install and configure the Slack CLI. Step-by-step instructions can be found in our Quickstart Guide.

Start by cloning this repository:

# Clone this project onto your machine
$ slack create my-app -t slack-samples/deno-starter-template

# Change into this project directory
$ cd my-app

Triggers are what cause workflows to run. These triggers can be invoked by a user, or automatically as a response to an event within Slack.

A link trigger is a type of trigger that generates a Shortcut URL which, when posted in a channel or added as a bookmark, becomes a link. When clicked, the link trigger will run the associated workflow.

Link triggers are unique to each installed version of your app. This means that Shortcut URLs will be different across each workspace, as well as between locally run and deployed apps.

When creating a trigger, you must select the workspace and environment that you'd like to create the trigger in. Each workspace has a local development version (denoted by (dev)), as well as a deployed version. Triggers created in a local environment will only be available to use when running the application locally.

To create a link trigger for the workflow in this template, run the following command:

$ slack trigger create --trigger-def triggers/sample_trigger.ts

After selecting a workspace and environment, the output provided will include the link trigger Shortcut URL. Copy and paste this URL into a channel as a message, or add it as a bookmark in a channel of the workspace you selected.

Note: this link won't run the workflow until the app is either running locally or deployed! Read on to learn how to run your app locally and eventually deploy it to Slack hosting.

While building your app, you can see your changes propagated to your workspace in real-time with slack run. In both the CLI and in Slack, you'll know an app is the development version if the name has the string (dev) appended.

# Run app locally
$ slack run

Connected, awaiting events

Once running, click the previously created Shortcut URL associated with the (dev) version of your app. This should start the included sample workflow.

To stop running locally, press <CTRL> + C to end the process.

If your app needs to store any data, a datastore would be the right place for that. For an example of a datastore, see datastores/sample_datastore.ts. Using a datastore also requires the datastore:write/datastore:read scopes to be present in your manifest.

For an example of how to test a function, see functions/sample_function_test.ts. Test filenames should be suffixed with _test.

Run all tests with deno test:

$ deno test

Once you're done with development, you can deploy the production version of your app to Slack hosting using slack deploy:

$ slack deploy

After deploying, create a new link trigger for the production version of your app (not appended with (dev)). Once the trigger is invoked, the workflow should run just as it did in when developing locally.

Activity logs for the production instance of your application can be viewed with the slack activity command:

$ slack activity

The app manifest contains the app's configuration. This file defines attributes like app name and description.

Used by the CLI to interact with the project's SDK dependencies. It contains script hooks that are executed by the CLI and implemented by the SDK.

Functions are reusable building blocks of automation that accept inputs, perform calculations, and provide outputs. Functions can be used independently or as steps in workflows.

A workflow is a set of steps that are executed in order. Each step in a workflow is a function.

Workflows can be configured to run without user input or they can collect input by beginning with a form before continuing to the next step.

Triggers determine when workflows are executed. A trigger file describes a scenario in which a workflow should be run, such as a user pressing a button or when a specific event occurs.

Datastores can securely store and retrieve data for your application. Required scopes to use datastores include datastore:write and datastore:read.

To learn more about developing with the CLI, you can visit the following guides:

• Creating a new app with the CLI
• Configuring your app
• Developing locally

To view all documentation and guides available, visit the Overview page.