Duaer

Integrations

Approvals in Slack for Duaer

With the Send and Wait for Response operation on the Duaer Slack node, approvers approve or decline inside Slack, the workflow resumes at once, and Duaer records who responded.

How Duaer approvals in Slack differ from link buttons

  • Link buttons (default): a click opens a Duaer page in the browser; anyone with the link can respond; the output has only approved and respondedAt.
  • Approvals in Slack: one click inside Slack; you can restrict approvers; Duaer verifies each callback with Slack request signing; the output adds the responder, channel, and message.

Requirements

  • Slack can reach your Duaer instance over public HTTPS.
  • A Slack credential (access token or OAuth2) with the app Signing Secret in Signature Secret. Without it the buttons render but clicks do not resume the workflow.
  • For the responder email, the app needs the users:read and users:read.email scopes. Without them the output just omits the email.

1. Create a Slack app and credential

Create the app and credential as in Slack credentials, and add users:read and users:read.email to the scopes.

2. Turn on Interactivity

  1. In Slack API Apps, open the app, go to Interactivity & Shortcuts, and turn on Interactivity.
  2. Set Request URL to https://<your Duaer host>/webhook-waiting-slack and save. Every workflow on the instance shares this URL. If you changed DUAER_ENDPOINT_WEBHOOK_WAIT, adjust the path.

A Slack app has one Request URL, so one app serves one Duaer instance.

3. Add the signing secret to the credential

Copy the Signing Secret from Basic Information > App Credentials in the Slack app and paste it into Signature Secret on the Duaer Slack credential. Callbacks that fail verification are rejected and the workflow keeps waiting.

4. Configure the node

In the Slack node, choose Message > Send and Wait for Response and set Response Type to Approval. Under Advanced Interactivity:

  • Capture Who Responded: switches to Slack interactive buttons and records the responder. The settings below appear once it is on.
  • Restrict Who Can Approve: the users allowed to act. Anyone else who clicks gets a private notice and the workflow keeps waiting. Leave it empty to let anyone who sees the message respond.
  • Unauthorized Reply: the private notice for people not on the list. Default: You are not authorized to respond to this request.
  • After Decision: Show Outcome and Remove Buttons (default; removes the buttons and adds the decision and responder), Remove Buttons Only, or Keep Message Unchanged (the first decision stands).

The list controls who can respond, not who can see the request. Post sensitive approvals to a private channel or direct message.

Node output

{
  "data": {
    "approved": true,
    "respondedAt": "2026-09-29T08:00:00.000Z",
    "channel": "C0123ABC456",
    "messageId": "1759132800.123456",
    "responder": { "id": "U0123ABC456", "name": "Jo Doe", "username": "jo.doe", "email": "jo@example.com", "source": "slack" }
  }
}

With Response Type set to Free Text or Custom Form, or Capture Who Responded off, the node still sends link buttons.

Questions

What Request URL do Duaer approvals in Slack need?

Set Interactivity in the Slack app to https://<your Duaer host>/webhook-waiting-slack. All workflows on the Duaer instance share it.

In this section