# Action trigger based on movement kanban

**URL:** https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225
**Category:** Feature Requests
**Created:** [March 29, 2022, 9:21pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225 "2022-03-29T21:21:21Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Yasin\_Hassanien](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/yasin_hassanien/32/9042_2.png) [@Yasin\_Hassanien](https://community.glideapps.com/u/Yasin_Hassanien)
#### Post date: [March 29, 2022, 9:21pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/1 "2022-03-29T21:21:22Z")

</div>

An action to trigger based ona movement of a card in Kanban pages

---

<div class="post-metadata">

### Author: ![Daniil\_Buriev](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/daniil_buriev/32/36933_2.png) [@Daniil\_Buriev](https://community.glideapps.com/u/Daniil_Buriev)
#### Post date: [March 30, 2022, 12:00am UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/2 "2022-03-30T00:00:47Z")

</div>

Indeed

---

<div class="post-metadata">

### Author: ![Claus\_Nissum\_Holm](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/claus_nissum_holm/32/35739_2.png) [@Claus\_Nissum\_Holm](https://community.glideapps.com/u/Claus_Nissum_Holm)
#### Post date: [December 12, 2022, 2:54pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/3 "2022-12-12T14:54:35Z")

</div>

Yes please, would be great.

---

<div class="post-metadata">

### Author: ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [December 12, 2022, 11:27pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/4 "2022-12-12T23:27:56Z")

</div>

Yes please! Voted!

Also need a way to prevent a subset of users from dragging and dropping cards (read only view).

---

<div class="post-metadata">

### Author: ![Jonathan\_Pierce](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jonathan_pierce/32/40498_2.png) [@Jonathan\_Pierce](https://community.glideapps.com/u/Jonathan_Pierce)
#### Post date: [May 1, 2023, 6:50pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/5 "2023-05-01T18:50:56Z")

</div>

Any thoughts on a work around option to achieve this?

---

<div class="post-metadata">

### Author: ![frojas](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/frojas/32/47720_2.png) [@frojas](https://community.glideapps.com/u/frojas)
#### Post date: [September 18, 2023, 9:11am UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/6 "2023-09-18T09:11:17Z")

</div>

I am also looking to achieve this and have not found a way to do so… has anyone here figured it out?

---

<div class="post-metadata">

### Author: ![ScottLLC](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/scottllc/32/60457_2.png) [@ScottLLC](https://community.glideapps.com/u/ScottLLC)
#### Post date: [January 29, 2024, 9:19pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/7 "2024-01-29T21:19:56Z")

</div>

Been a while so following up on this. Any solutions for notifications when a card is moved from one group to another? I’d really like to trigger notifications/emails when a card moves from one column to the next. Any ideas?

---

<div class="post-metadata">

### Author: ![DanielNice](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/danielnice/32/63330_2.png) [@DanielNice](https://community.glideapps.com/u/DanielNice)
#### Post date: [February 13, 2024, 4:52pm UTC](https://community.glideapps.com/t/action-trigger-based-on-movement-kanban/40225/8 "2024-02-13T16:52:38Z")

</div>

Agreed this is needed and I ahve not found a work around as of yet ☹
