Examples

Example 1: Send a Formatted Block Kit Message to a Channel

Business story: Acme Corp's CI/CD pipeline completes a production deployment. A workflow node automatically posts a rich Block Kit message to the #deployments channel so the engineering team sees build health, environment, and a direct link to the deployment logs — all without anyone manually updating Slack.

[
  {
    "type": "header",
    "text": {
      "type": "plain_text",
      "text": ":white_check_mark: Deployment Succeeded — payment-service"
    }
  },
  {
    "type": "section",
    "fields": [
      { "type": "mrkdwn", "text": "*Service:*\npayment-service" },
      { "type": "mrkdwn", "text": "*Version:*\nv3.7.2" },
      { "type": "mrkdwn", "text": "*Environment:*\nproduction" },
      { "type": "mrkdwn", "text": "*Duration:*\n4m 12s" },
      { "type": "mrkdwn", "text": "*Deployed by:*\nGitHub Actions" },
      { "type": "mrkdwn", "text": "*Commit:*\n`a3f9d22` Fix checkout timeout on high load" }
    ]
  },
  {
    "type": "divider"
  },
  {
    "type": "actions",
    "elements": [
      {
        "type": "button",
        "text": { "type": "plain_text", "text": "View Build Logs" },
        "url": "https://github.com/acmecorp/payment-service/actions/runs/12345678",
        "style": "primary"
      },
      {
        "type": "button",
        "text": { "type": "plain_text", "text": "Rollback" },
        "url": "https://deploy.acmecorp.internal/rollback/payment-service",
        "style": "danger"
      }
    ]
  }
]

Example 2: Create a Private Channel and Invite Users

Business story: Acme Corp launches a new client project, "Project Atlas." The project management workflow automatically creates a private Slack channel for the project team, then invites the project manager, lead engineer, and client success manager so they can collaborate immediately — without an admin manually setting up Slack.

Success output: id: "C07ATLAS01", name: "project-atlas-2026", isPrivate: true.

Post a welcome message to the newly created channel:

[
  {
    "type": "header",
    "text": { "type": "plain_text", "text": ":tada: Welcome to Project Atlas 2026" }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": "This private channel is the home for all *Project Atlas* communication. The project kicks off on *June 1, 2026* with a target Q3 delivery.\n\n*Team:*\n- PM: <@U023SARAH1> (Sarah Chen)\n- Lead Engineer: <@U034LIANG2> (Liang Wu)\n- Client Success: <@U045JAMES3> (James Okafor)"
    }
  },
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": ":link: **  |  **"
    }
  }
]

Example 3: Upload a File with Content to Multiple Channels

Business story: Every Monday morning, Acme Corp's analytics workflow generates a weekly sales summary as a CSV file and posts it to both #sales and #management channels so department heads have the data waiting for them when they start work. The CSV content is assembled inline from workflow variables — no disk access needed.

The FileContent value is assembled by an upstream Code node and passed as a variable. Example content:

Week Ending,Total Revenue,New Customers,Avg Deal Size,Pipeline Added,MRR
2026-05-19,"$842,500",34,"$24,779","$1,240,000","$112,400"
2026-05-12,"$798,200",29,"$27,524","$985,000","$108,900"
2026-05-05,"$901,000",41,"$21,976","$1,410,000","$119,200"

After uploading, post a summary message in #sales with the permalink to the file:

[
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": ":bar_chart: *Weekly Sales Summary — Week Ending 19 May 2026*\n\n*Total Revenue:* $842,500  |  *New Customers:* 34  |  *MRR:* $112,400\n\n:paperclip: *<https://acmecorp.slack.com/files/.../weekly-sales-summary-2026-05-19.csv|Download CSV>*"
    }
  }
]

Example 4: Add an Emoji Reaction to a Message

Business story: Acme Corp's support workflow monitors a #support-queue channel. When a customer ticket is resolved and the resolution is confirmed in the CRM, the workflow automatically reacts to the original Slack support request message with a green checkmark so the support team can immediately see which requests have been closed — without reading every message thread.

The :zap: reaction is the team's visual signal that the ticket was resolved within SLA.

Example 5: Create a User Group for a Department and Assign Members

Business story: Acme Corp's HR system triggers a workflow when a new department is created in the org chart. The workflow automatically creates a matching Slack User Group so department members can be mentioned as a group with @finance-team — and new employees added to the department are automatically added to the group going forward.

Success output: usergroupId: "S05FINGRP1", name: "Finance Team", handle: "finance-team".

This adds all five Finance team members in a single operation.

[
  {
    "type": "section",
    "text": {
      "type": "mrkdwn",
      "text": ":busts_in_silhouette: The *@finance-team* user group is now active with 5 members.\n\nAnyone in the workspace can now mention the entire Finance team by typing `@finance-team`. This group will be kept in sync automatically as team membership changes in HR."
    }
  },
  {
    "type": "context",
    "elements": [
      {
        "type": "mrkdwn",
        "text": "Members: <@U056PRIYA1>, <@U067OMAR02>, <@U078LINDA3>, <@U089KEVIN4>, <@U090NIAMH5>"
      }
    ]
  }
]