Hi Gliders, I did have a look and saw no answers, but I just wondered if anyone has a clever idea to trigger an action based on a kanban movement. I would love to have a situation where, when a tile is moved from one swimlane to another, I could send a notification e-mail or SMS or other actions from that category. I did find some requests for it, it kinda makes the moving tile a bit limited 
Yeah, but what I can’t figure out is how to make the move trigger a workflow. Let’s say I have a field worker, and he moves the progress of a job card from To-Do to completed. Is there a way I can trigger an email send with the updated details of the job to the client and the office
Thank you Jeff, Sorry, I think I’m confusing myself. I did get the trigger happening when I moved the card, but I was looking to trigger when it landed in its next location. For example. I Have 3 lanes: New, Contacted, Won. When I drag from New → Contacted, I wanted to trigger to send a webhook to make.com, which it does. But if I drag from New → Won, I wanted to trigger an email to the client, which it won’t, it will trigger the webhook again because it’s triggering “from” the column and not triggering when it gets “to” the column. I’ve probably got it configured incorrectly or just don’t understand the process, but it’s doing my head in 
Thanks for your advice I really appreciate it
The trigger based on the “from” column instead of the “to” column is a timing issue. The lane is being updated in the table after the workflow runs. To get around that, you could add a short wait action to allow time for the lane to update in the table. For something simple, like dealing with only one lane, you could do something like I’m doing in the following screenshot. I have a half second delay to allow the column value to update with the new lane. Then a wait for condition with a short half second delay that checks if the lane is the one you want. Finally, any actions that run after the wait for condition is successful.
But for your case, you might also need a manual workflow. Your initial workflow could start with the 0.5 second delay, followed by an action that calls your manual workflow. The manual workflow would then have different conditional branching based on the lane that was passed into it. (I don’t have a current plan that allows me to test this, so it’s just a theory that it should work.)
Ahhh, perfect. I went down the calling the manual workflow idea, and that seemed to work in the case that I had, but I didn’t think at all about the delay. Thanks so very much, so sorry it was doing my head in, it would kinda work then all fall apart haha. I fell back to locking it out and having a button on the card’s detail page that stepped it to the next lane, but apart from looking good, it kinda defeated the purpose of the Kanban. Thanks again, Jeff, I really appreciate the help