Flow integration

[juliushaertl]

Possible use cases:

• when I tag a card with later I want the card moved into the e.g. ideas column while cards with action required are moved to priority. In best case the user can setup thoose rules by himself. (#1703)
• If a card is updated or created, trigger a webhook (e.g. to notify in external chat software) #3341

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

[Spartachetto]

I'll try to put down a general schema, hope that helps

from outside Deck to inside

• when I tag a file with x a card has to be created with the file as an attachment
• when I tag a note with x a card has to be created with the note content in it
• when I receive an email with y in the title (or from a specific address) a card has to be created. In addition if the email has attachments, these have to become card attachments. In addition if the email contains calendar info on a meeting these have to become deadlines of the card. In addition I can have the possibility to assign the card to the user z (this is also linked to https://github.com/nextcloud/mail/issues/2823 )

inside Deck

• if I empty a column in a board a card in another board has to be modified
• when I tag a card with later I want the card moved into the e.g. ideas column while cards with action required are moved to priority. In best case the user can setup thoose rules by himself. ( #1703 )

from Deck to the outside

Here 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....

[fti7]

I miss the Trello Automation Stuff in general. Easy Example what i use daily: Tag Card automatically with Tag X when there is a specified Word is in the Card Title.

[Spartachetto]

@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....

[juliushaertl]

@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.

[marvinjuette]

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.

[davidkarban]

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: When I move the card to another column, modify its properties.

[Spartachetto]

@marvinjuette I just realized that I opened a ticket that probably asks for this functionality: https://github.com/nextcloud/server/issues/25914

I think it as a generic Flow functionality, so the ticket is in the server repo. I am putting the link also as a possible useful reference to juliushaertl.... Hope that helps!

[cheadrian]

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 Seems to be a solution for what I've looking, but it lacks some feature I've looking for. I've managed to make it run on shared webhost.

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.

[stefan-niedermann]

@cheadrian check out mail2deck

[juliushaertl]

• If a card is updated or created, trigger a webhook (e.g. to notify in external chat software) https://github.com/nextcloud/deck/issues/3341

[stefankrischer]

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.

[abacao]

I have opened the above feature request but it looks like it is kind of duplicate. I will leave here my ideias and close the FR

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 add a assign user / removes / remove all (this can almost solve and issue of vertical swimlanes per assignee) adds / remove a card color background giving the visual help of priority (red, yellow, green) adds some relative time to the cards due date (+3d / +1w / +1m....)

[l-mb]

Some form of automation - moving cards, modifying labels, possibly highlighting them, etc - would really be very useful.

[gwnmikedus]

This would be really nice. Currently it is not possible to make cards send data through api to n8n/taiga, am I correct? I thought it was after scanning the docs quickly. In the Webhooks flow integration there is only files to choose from, no other kind of items.

Any way to make external apps work with Deck and the other way around?

[jlguerrerosanz]

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.

[proserver1]

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

[tucker-m]

Chiming in with the start of a small contribution. My plan is to first make some occ commands for deck (like occ deck:create-card and occ deck:move-card), so that some of the ideas in this thread could be done with the workflow_script app. You would still have to write some kind of bash script that calls the occ commands, but at least it would be something.

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