---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Slack activities

# Slack activities {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Enable agents and fulfillers to send direct messages and post in Slack
channels during a playbook run, via Workflow Data Fabric's Slack spoke.

## Roles and availability {#pad-activities-slack__section_i2c_tbc_35b}

* These activities are available as an application in the ServiceNow Store. Users with the playbook.admin or pd_author role can add these activities to a playbook.
* You must have access to Workflow Data Fabric's Slack spoke.
{#pad-activities-slack__ul_oqy_xbc_35b}

## Inputs {#pad-activities-slack__section_x15_tcc_35b}

Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).
{#pad-activities-slack__table_qcb_5jc_35b__entry__3}{#pad-activities-slack__activity-input-channel-member-id}{#pad-activities-slack__activity-input-username}{#pad-activities-slack__activity-input-icon}

| Input | Type | Description |
|-|-|-|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Select Show additional options to see this field. |
| Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#pad-activities-slack__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: <!-- --> * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#pad-activities-slack__ul_zzc_3ls_m1c} |
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://servicenow-prod.fluidtopics.net/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Select Show additional options to see this field. |
| Channel/Member ID | String | Slack channel or member that the message is sent to. |
| Message | String | Message text to display to end users. |
| Blocks | String | Code blocks to include in the message to end users. |
| Username | String | Sender of the Slack message. |
| Icon | String | Slack user profile icon of the sender. |
| Collect data from user | True/False | Option to pause the playbook until the end user manually completes or skips the activity. Only users with the playbook.admin role can edit this field. By default, the activity waits for user action or data before it completes. |
[ ]

{#pad-activities-slack__table_qcb_5jc_35b}

## Outputs {#pad-activities-slack__section_gdj_3nc_35b}

Your message posted in a Slack channel or sent as a direct message.

*[\>]: and then