Verify Channel Exists activity

An activity that checks whether a channel exists in Slack.


Verify Channel Exists screen

Configure the Verify Channel Exists activity

To configure the Verify Channel Exists activity, do the procedure in this topic.

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the Slack tab.

    Open Slack tab
  3. On the Slack tab, drag the Verify Channel Exists activity onto your process.

    Drag Verify Channel Exists activity

General Configuration

Specifies the basic settings for the Verify Channel Exists activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

  • Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field NameDefinition

Display Name

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Verify Channel Exists Configuration

Specifies the settings checks whether a channel exists in Slack.

Figure: Verify Channel Exists Configuration screen

Verify Channel Exists Configuration screen

Fields

Field NameDefinition

Slack

Function:
Specifies the access token that connects to your Slack service.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None

Create Add Token icon

Opens this Screen:
Access Token for Slack
Function of this Screen:
Configure an access token to connect to Slack.

Public/Private

Function:
Specifies whether the channel is open to all Slack users.
Accepted Values:
  • Public - The channel for conversations that are open to all Slack users to see and join the channel.
  • Private - The channel members can see the content of this channel.
Default Value:
Public
Accepts Process Data Variables:
No

Channel

Function:
Specifies the name of the channel or a process data variable that contains the channel ID.
Accepted Values:
A channel name from the list.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Store Response in this Variable

Function:
Specifies a process data variable that stores a Boolean value of true or false.

The value is true if the channel exists in Slack.

Accepted Values:
A process data variable that accepts a Boolean value, or the text true or false.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?