# Script to notify user of newly created entity with direct link or redirect **URL:** \ **Category:** Get Help\ **Created:** [June 11, 2023, 12:26pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600 "2023-06-11T12:26:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [June 11, 2023, 12:26pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/1 "2023-06-11T12:26:00Z")
If a user creates an automation button what creates a new entity, this results in a confirmation, but the result is not visible or clickable. I would like to try these solutions: (1) create a script that notifies the user of the created entity, and shows a direct link to the created entity. (2) create a script that redirects the user to the newly created entity display. (3) create a script that opens the newly created entity display in a new panel. Can anyone help me out with his? Thanks ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 11, 2023, 10:07pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/2 "2023-06-11T22:07:52Z")
Fibery Automations and scripts unfortunately have no ability to control the UI - the most they can do is display a “result message” (and Button scripts can also send info to the browser’s debug console). Automations can also create Notifications, but that is not quite the same. I doubt a script could create a clickable link in a Button result message, since these messages do not support any HTML or formatting. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [June 18, 2023, 1:28pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/3 "2023-06-18T13:28:24Z")
We currently use automation buttons to convert one item into another, clean the old one and provide some extra information when needed. For example - We have a ‘braindump’ item \> it only has a title + description - We have a button to convert that into a task and provide data such as deadline, planning, project, etc. We would also be very happy if user has the option to open the entity that has just been created 😄 ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [October 23, 2023, 7:31pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/4 "2023-10-23T19:31:50Z")
Maybe one of the developers can help out here since such feature (html in automation script messages) would be so helpful. ---
**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\ **Post date:** [February 25, 2024, 11:28pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/5 "2024-02-25T23:28:09Z")
I’m not sure if this is still relevant to anyone, but it turns out you can create user notifications using Graphql mutations and execute them using fibery.graphql() in scripts and automations. I’ve been able to generate user notifications with both automations and buttons. There are some good examples here: [. | Fibery](https://the.fibery.io/@public/search/fXvXm#User_Guide/Guide/GraphQL-Mutations-256). ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [February 26, 2024, 10:08pm UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/6 "2024-02-26T22:08:22Z")
> [@Tommy\_Hedley](#): > > I’m not sure if this is still relevant to anyone, but it turns out you can create user notifications using Graphql mutations and execute them using fibery.graphql() in scripts and automations. I’ve been able to generate user notifications with both automations and buttons. There are some good examples here: [. | Fibery](https://the.fibery.io/@public/search/fXvXm#User_Guide/Guide/GraphQL-Mutations-256). I don’t see how to GraphQL generated messages can support HTML? How does it relate to this topic? ---
**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\ **Post date:** [February 27, 2024, 1:08am UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/7 "2024-02-27T01:08:06Z")
Given that you provide an entity to send the notification about, I figured that you could filter for the new entity that was created and send confirmation as a notification. When you click on the notification it opens the entity in question. I realize it’s not a direct link in the traditional sense but it does provide the user with easy access to the new entity. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [February 27, 2024, 8:54am UTC](https://community.fibery.io/t/script-to-notify-user-of-newly-created-entity-with-direct-link-or-redirect/4600/8 "2024-02-27T08:54:43Z")
Yes, thats the workaround that I use also (without script) but it fills up big amount of screen real estate. ![chrome_P6WqL63fPr](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8a5050a2dbeb395dc84253c285094490ee0945a1.png) This would be okay if Fibery implements **Field Visibility Rules as part of their future entity view improvements**. Then such field could appear and disappear when it contains content.