# Custom success notification on smart action

**URL:** <https://community.forestadmin.com/t/custom-success-notification-on-smart-action/5856>\
**Category:** Help me!\
**Tags:** smart-action\
**Created:** [January 16, 2023, 11:25am UTC](https://community.forestadmin.com/t/custom-success-notification-on-smart-action/5856 "2023-01-16T11:25:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DLB](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/dlb/32/5626_2.png) [@DLB](https://community.forestadmin.com/u/DLB)\
**Post date:** [January 16, 2023, 11:25am UTC](https://community.forestadmin.com/t/custom-success-notification-on-smart-action/5856/1 "2023-01-16T11:25:58Z")

</div>

## Feature(s) impacted

Custom success notification on smart action: [Create and manage Smart Actions | Developer Guide](https://docs.forestadmin.com/documentation/reference-guide/actions/create-and-manage-smart-actions#custom-success-notification)

## Observed behavior

The notification displays the default message and not the custom one.

## Expected behavior

I want to display a custom message when the smart action succeeds.

About the documentation, it’s written a 200 should be returned with the custom message but in the code example the default status code is used (201). I tried both but neither of them works.

To be sure I tried to return a custom error message and it works. So it seems to have an issue only with the custom success notification.

## Failure Logs

## Context

- Project name: Swan back-office
- Agent type & version: 8.5.11

---

<div class="post-metadata">

**Author:** ![anon7311026](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@anon7311026](https://community.forestadmin.com/u/anon7311026)\
**Post date:** [January 16, 2023, 11:53am UTC](https://community.forestadmin.com/t/custom-success-notification-on-smart-action/5856/3 "2023-01-16T11:53:03Z")

</div>

Hi @DLB, welcome to the community.

200 or 201 are just variations of the success code in HTTP, 201 being slightly more specific (ressource created), but both should work.

Could you please share your implementation (or a simplified version reproducing the issue) to highlight how you created the smart action, and help us provide suggestions ?  
Thanks

Regards,

Nicolas
