-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flow integration #1722
Comments
I'll try to put down a general schema, hope that helps from outside Deck to inside
inside Deck
from Deck to the outsideHere I see things that will become easy with the integration of CalDAV. I.e.: if the due date is near send a talk message / an email / a notification.... |
I miss the Trello Automation Stuff in general. |
@juliushaertl If you think it can be useful, I can try to keep updated my previous post. For example I could insert @fti7 request as a bullet point within the "inside Deck" section.... |
@Spartachetto I think just collecting them in the individual comments is fine. Once we get to implement something I'll try to group everything that came up a bit more in the original post. |
Another idea: time based actions. eg. if a card is for certain time (like a day) in a specific column it should be tagged with later. |
Hi folks, I`ll add another one. When I move the card into the specific column (Done in my use case), unassign me and remove Due time. If I abstract it: |
@marvinjuette I just realized that I opened a ticket that probably asks for this functionality: nextcloud/server#25914 I think it as a generic Flow functionality, so the ticket is in the server repo. |
A feature which I would like is to integrate email with Deck, so that when a specific format of email, from a subject, data are parsed in a format defined by user and added to Deck. @stefan-niedermann That being said, it would be nice to have a flow witch integrates the Mail app with the Deck configurable from the user interface and with extra options and filters. |
@cheadrian check out |
|
Although this thread has been inactive for a while, I wanted to ask, if any of the propositions have been implemented yet. And I have an Idea to add: Automaticcly assign a Card to a User, when it's added to a specific board or list. E.g. when I move a card to another list, which is mainly (but not only) deald whith by a colleage, that it's first assigned to that user, because it's the default, but then can be changed to someone else if nessecary. |
I have opened the above feature request but it looks like it is kind of duplicate. What I imagine is a configuration per stack that would allow the setup of some fields, such as: add a tag / remove a tag / remove all tags when the card is moved to that stack |
Some form of automation - moving cards, modifying labels, possibly highlighting them, etc - would really be very useful. |
This integration could convert Deck into a very powerful CRM. When a card lands on a stack, you could trigger an email, an SMS or a whatsapp. If cards could have predefined variables, such as "Name" or "Email" or "Telephne" an email could be triggered to the email address calling that person. If a card is stuck for more than X days in a pile, a message could be sent to a user... If a card stays more than X time in a pile, it could be automatically moved to a different pile. The first thing needed is the ability to detect those events and pass them to flow. |
missing more conditions esp. deck very much.... actions aka then-side is ok with webhooks or external scripts but conditionds aka if-side is laking |
Chiming in with the start of a small contribution. My plan is to first make some My eventual plan is to make these available as flow actions so that you don't have to use workflow_script. My fork is here, still very much a work in progress: https://github.com/tucker-m/deck/tree/occ-create-card |
Sorry for the noise, but wondered if Flow was still on the Deck roadmap. We're looking to make something that will email (only) people associated with a card when that card changes (to make an issue tracker). |
Possible use cases:
Anyone is free to come up with additional use cases that might be useful for automating tasks around deck, maybe we can then come up with a plan how this could be integrated with Nextcloud Flow.
@nextcloud/deck
The text was updated successfully, but these errors were encountered: