Join our largest event of the year | CamundaCon 2022 October 5-6

Icon Close
Image of slack connectors being utilized in BPMN Diagram

Level up your process communication with the new Slack Connector

If you’re using Camunda Platform 8, you might already be taking advantage of the REST Connector for making API calls or the SendGrid Connector for sending emails. Now we’re excited to announce an out-of-the-box Slack Connector that allows you to send messages to channels or users in your Slack workspace as part of your business processes. The Slack Connector is a convenient way to keep people in your organization up-to-date with important things happening in your business processes; for example, if a certain logical flow is triggered or if someone needs to take action on a specific task.

Camunda Platform 8’s out-of-the-box Connectors are designed to help you overcome one of the biggest hurdles to process orchestration: figuring out how the process should interface with different types of endpoints such as APIs, RPA bots, CRM and ERP platforms, user-facing applications, and so on. Most processes—even fairly simple ones—involve at least a few of these endpoints, and the level of complexity can grow very quickly. For example, if a process invokes an RPA bot, you need to know exactly what data the bot will need to execute its task.

Camunda Platform 8 orchestrates complex business processes across all of the different types of process endpoints in your organization, and Connectors are here to make it easier. They communicate with any system or technology, reducing the time it takes to model, implement, and automate business processes. They’re modular and designed for reuse, so your teams don’t have to reinvent the wheel every time they need to work with a particular endpoint. And they’re user-friendly; if you can add a task to a BPMN process diagram, you can use Connectors.

Connectors for everyone!

The Slack Connector requires a quick one-time setup process; after that, it’s as easy as adding Slack tasks to your BPMN process diagrams. The code that’s required to send a Slack message is built into the Connector, so you only have to provide a few configuration details, such as the name of the Slack channel or user that you want to send a message to. 

This streamlined design makes Connectors ideal for low-code developers, business analysts, and other process designers who might not be adept at Java or other programming languages. Pro-code developers also benefit from the convenience of Connectors; instead of spending time writing and rewriting code to do a relatively simple action like sending a Slack message, they can focus on software development work that’s more complex or work that’s specialized for their company’s business.

Get ready to use the Slack Connector

A one-time setup is required before you can use the Slack Connector:

  1. Figure out your Slack workspace. A workspace is identified by a unique name such as
  2. Create a Slack app and install it in the workspace. The Connector communicates with Slack through a Slack app. Don’t worry, you don’t have to write or test any code; Slack provides a step-by-step process for creating an app. After the app is installed, copy its bot token (which is an OAuth token). The Connector will use this token to authenticate with the Slack API.
  3. Store the bot token as a secret in Camunda Platform 8. Follow our guide for creating secrets and name your secret something easy to read, like SLACK_OAUTH_TOKEN. You’ll reference this name when you use the Slack Connector in a BPMN diagram.

Use the Connector in a BPMN diagram

After you’ve set up the Slack app and stored the bot token in Camunda Platform 8, anyone in your organization can use the Slack Connector in their BPMN diagrams. To do so:

  1. Log in to Camunda Platform 8.
  2. Launch Web Modeler and create a new BPMN diagram or open an existing one.
  3. Click an element in the diagram and click the Append Connector context menu item to add a Connector task. Type Slack in the search box to filter the list of Connectors, or just scroll down and select the Slack Connector.
  4. In the task’s properties panel, set OAuth Token to the name of the secret that you created earlier, in the format secrets.SLACK_OAUTH_TOKEN.
  5. Set Channel/User Name to the Slack channel or name of the user that you want to send the message to. Channel names must start with a hash symbol (#). Usernames must start with an at sign (@).
  6. Set Message to the message that you’d like to send.
Image of slack connectors being utilized in BPMN Diagram

The channel, user name, and message can be static values, or you can use a FEEL expression to reference process variables or dynamically create values. For more information about using FEEL, visit the Slack Connector documentation.

You can apply text formatting to the messages that are sent via Slack Connector; check out the Slack API documentation to learn more.


The Slack Connector is already available for all Camunda Platform 8 SaaS users. For Self-Managed users, the Connector will be available in the Camunda Platform 8.1 release. Try it for yourself today by creating a free account.

Learn more about Connectors

Want to see more out-of-the-box Connectors? You can get your fill at CamundaCon! Join us October 5 and 6, virtually or in-person, to see how Camundos and Camunda partners are building a rich library of out-of-the-box Connectors for you to use in your own business processes.

If you can’t wait for CamundaCon, check out our recent Camunda Nation podcast, Camunda 8 Connectors: Reusable Integrations. Developer Advocate Josh Wulf talks with Principal Software Engineer Nico Rehwaldt about what Connectors are, how they relate to process modeling, and how you can get started. 

To learn about the future of Connectors, watch Camunda Question Corner #22. Camunda Product Manager Preeti Nirwal joins Developer Advocate Nele Uhlemann to discuss our roadmap for out-of-the-box Connectors and the new Connector SDK.

  • Using FEEL with Camunda 8

    What is FEEL As a part of the Decision Model and Notation (DMN) specification, the OMG also defined the Friendly Enough Expression Language (FEEL).  Since DMN is intended to be used by designers and business analysts who would like to build decision tables, FEEL needed to be designed as an uncomplicated and human-readable expression language that would help readers understand the logic being described or executed by the DMN table.  Expression languages are typically used by developers to evaluate data to produce a result based on query parameters or conditions. This means it’s syntactically closer to code than human-readable sentences. Since one of the goals of FEEL is to be “process analyst friendly,” it prioritizes readability more than other expression...

    Read more
  • Camunda supports process automation at scale

    How Camunda 8 supports process automation at...

    Scaling process automation across an enterprise naturally includes a wide array of challenges. To counter these challenges, more and more organizations are evolving their organizational structures accordingly, often creating Centers of Excellence (CoE) and/or communities of practice (CoP). Please note that during this post we will use the term CoE, but keep in mind your organization might call this very differently. That said, in Camunda Platform 8, we included new functionalities that will help companies to scale process automation successfully.  This blog post discusses different aspects of scaling process automation, the role of CoEs, and how new Camunda 8 features support those initiatives.  What does scaling mean? Organizations that want to create a competitive edge through digital transformation (and frankly: which...

    Read more
  • 7 Best programming languages for microservices - Camunda

    7 Best Programming Languages for Microservices

    Microservices are an architectural style that structures an application as a collection of services that are: Highly maintainable and testable Loosely coupled Independently deployable Organized around business capabilities Owned by a small team Conway’s Law states that “any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure”. If your organization has multiple teams working on different parts of a larger system, then microservices can serve as a separation of concerns that map an independent, encapsulated service to a specific team. These teams have clear boundaries of responsibility and can deploy on their own schedule. These factors lend themselves to a polyglot approach. What this means is that because...

    Read more

Ready to get started?

Still have questions?