# \[✔️\] Generating notifications as part of "actions"/automation **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [August 24, 2020, 7:49pm UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912 "2020-08-24T19:49:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [August 24, 2020, 7:49pm UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/1 "2020-08-24T19:49:20Z")
If I recall correctly there is a significant feature planned for implementing “actions”, i.e. automation, where we can setup conditions to evaluate and actions to execute when they are true. I imagine this may already be part of the plan, but I wanted to make sure that one of the available actions will be “generate notification”. Ideally it would allow for creating notifications for a specific user or users, keyed off of an assignee, but _also_ the option of notifying _everyone_, if desired. Or people of a certain user group (i.e. admin vs. user). This could be very powerful and useful, especially once the notification system itself (UI/UX, mainly) gets improved as well. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [August 25, 2020, 4:57am UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/2 "2020-08-25T04:57:00Z")
Support this 100%! And can’t wait for automations. You are right, there has been discussion and I have good faith Fibery will do a great job with them! ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [October 5, 2020, 8:06pm UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/3 "2020-10-05T20:06:26Z")
I wanted to add here that it would be very useful if you could apply this Notification automation to certain fields, and set up rules as such. So for example, your “Date” field would be able to trigger notifications if it became “less than” now, such as “overdue.” Another use would be tie-in to Workflow. If somebody changes to “closed,” which has a certain distinction already in the Workflow Extension, that could trigger a Notification. This relates to this request, which I think is specifically talking about this functionality on a “user” type field: > [@Set up Notifications for Secondary User Fields](https://community.fibery.io/t/set-up-notifications-for-secondary-user-fields/904/3): > > I have also created a request for this functionality: It would follow that a “watcher” type of user would also be incorporated into Notifications, as is the case with most other Work Management apps. Feel free to add a " heart" vote for that as it’s the only way I know in this community to “upvote” requests! This has really been hard for my team, who has to keep looking in Fibery to see where things are assigned, overdue, completed, etc. having relied on notifications for this in the past, since this is a typical feature of most competent Work Management tools. And as always, would love any guidance from the Fibery team about this. Notifications/Actions are a big piece I am waiting on and haven’t seen a tweet or mention of them in quite a while! Thanks! ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 5, 2020, 8:26pm UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/4 "2020-10-05T20:26:10Z")
Yes, I think it would be great if triggering notifications were just another “action” that could occur on certain conditions of _any_ field, which presumably is what the automations system will allow. Improvement of the notifications system itself overall may be a separate issue. Although I could also see it being handled essentially through the idea of this approach above, all driven by automations. With just some default rules that get created from maybe the Workflow extension, e.g. as you describe “notify when date is today or later AND status is Open” or whatever would get automatically added as a rule when that extension was enabled. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 5, 2021, 1:19pm UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/5 "2021-08-05T13:19:47Z")
Implemented in latest release > [@CHANGELOG: August 5 / Export Document or Entity to Markdown, Notify People Action](https://community.fibery.io/t/changelog-august-5-export-document-or-entity-to-markdown-notify-people-action/1884): > > rolled_up_newspaper Export Document or Entity to Markdown Now you can export documents and entities into markdown. Find Export to Markdown in the right top corner. What is exported? You will get an archive with a markdown file and all images. If an entity has several rich edit fields, all the fields will be added into a single markdown file. Cases: Now you can write an article in Fibery, export it into markdown, and quickly publish it on any platform… ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [July 6, 2026, 5:19am UTC](https://community.fibery.io/t/generating-notifications-as-part-of-actions-automation/912/6 "2026-07-06T05:19:43Z")