Slack notification failed as the API is out of date

[vincent-tarrit]

To Reproduce

Create a slack notification with "Deployment build success", deploy something and the api fail with the error :

Error: Failed to send slack notification Failed to send slack notification Unprocessable Entity
at async NE.TE.autorun [as processFn] (dist/server.mjs:1:1111)

Current vs. Expected behavior

The notification isn't send, i would like to receive the notification.

Provide environment information

Ubuntu 24.04

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Additional context

the file :

dokploy/packages/server/src/utils/notifications/build-success.ts

Line 222 in 6fb4a13

if (slack) {

use an out of date API. the actions key is blocking. Can you update the content with :

if (slack) {
const { channel } = slack;

await sendSlackNotification(slack, {
channel: channel,
attachments: [
{
color: "#00FF00",
pretext: ":white_check_mark: Build Success",
fields: [
{
title: "Project",
value: projectName || "N/A",
short: true,
},
{
title: "Application",
value: applicationName || "N/A",
short: true,
},
{
title: "Environment",
value: environmentName || "N/A",
short: true,
},
{
title: "Type",
value: applicationType || "N/A",
short: true,
},
{
title: "Time",
value: date?.toLocaleString?.() || "N/A",
short: true,
},
{
title: "Details",
value: <${buildLink}|View Build Details>,
short: false,
},
],
},
],
});
}

Will you send a PR to fix it?

YES : https://github.com/Dokploy/dokploy/pull/4054/changes

[dosubot]

Hi @vincent-tarrit! I'm Dosu and I’m helping the dokploy team.

Thanks for the detailed report! I can confirm the issue — the actions key in the Slack notification payload is causing the Unprocessable Entity error.

The current code in build-success.ts (lines 257-263) uses the deprecated actions array:

actions: [
    {
        type: "button",
        text: "View Build Details",
        url: buildLink,
    },
],

Interestingly, database-backup.ts doesn't include the actions key and works fine, which validates the fix you've suggested.

Your proposed solution of replacing the actions button with a <${buildLink}|View Build Details> Slack link format in the fields array is a good approach. Note that build-error.ts also has the same issue, so both files should be updated together.

If you decide to submit a PR, make sure to target the canary branch per the contributing guidelines.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[vincent-tarrit]

@dosu Here is the pr : #4054

[dosubot]

Thanks for submitting PR #4054! That's a solid fix for the deprecated Slack actions key issue. Appreciate you taking the initiative to address this — hopefully the maintainers can get it reviewed and merged soon. 🙌

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.