Workflows: Slack notification

This article explains the Slack notification node that can be configured as part of Workflows. Learn more about using workflows here.

‍

Used For

1. Notifying other Clappia users on Slack regarding submission created/edited events.
2. Notifying Clappia users on Slack when their submissions are approved, rejected or moved to any other status.
3. Notifying external users of events happening within the Clappia workplace.

‍

Editing the block

Click on the block and start editing on the panel that appears on the right side.

‍

‍

Step name

This is the name that appears in the Workflow on the left side. If there are multiple Slack nodes in the workflow, set different step names like Slack Private, Slack Company etc.

‍

To Slack Channel

Webhook URL of the Slack Channel to which notification is to be sent. See how to configure the Webhook URL of your Slack channel here. The URL will be of the format https://hooks.slack.com/services/XXXXXXXXX/YYYYYYYYY/ZZZZ

‍

Subject

Subject of the Slack notification. It can be a fixed subject or it can also use variables defined in the app. Learn more about using variables in workflows here.

‍

‍

‍

‍

‍

‍

Body

Body of the Slack notification. It can also use variables defined in the app. Learn more about using variables in workflows here.

‍

‍

‍

‍

‍

‍

‍

Parent Step

Parent step refers to the function which is just above the Slack node. Here, it is the If function.

‍

Enable this Step

This step is enabled by default. Disable this node to stop this workflow step and all the workflow steps below it.

‍

Example of Slack node

‍

Note on Workflows and Bulk Operations

Workflows in Clappia run on individual submissions, such as when a user submits or manually edits a record. However, when using Bulk Upload or Bulk Edit from the Submissions tab, workflows are not triggered, even though new submissions may be added or existing ones updated.

This is because workflows are designed to process one submission at a time. Triggering them for bulk operations can lead to incomplete or inconsistent results, especially for complex workflows.

If you need workflows to run after a bulk operation, currently you will need to open each submission manually and save it. This will count as an edit and trigger the workflow normally.