I did a backend script that add cards to Deck from email.
This is happening from outside, using the API.
I think it’s a good idea to implement this into Deck app, but i don’t know exactly how to do that, or to do something else so that users can use this feature.
Opinions, suggestions?
Thanks!
Check-out the Github repository of the Deck app, follow the contribution guidelines and create a pull request.
CC: @juliushaertl Can you provide some more advice please.
I was thinking of doing this, but the problem is that i wrote the code outside of the deck app (i did not modify the deck app, i made a php file that needs to be run to add a new card)
@j-ed, you know what i mean?
Since it is an external script I would prefer to have it in a separate repository. I would suggest you create one as you are the author and maintainer of the script and we can add a nice hint about it to the deck documentation and readme file. Does that make sense?
Sounds great!
Sounds like something i really need 
Where can i find it?
There has been some progress here:
I modified the work from
providing a python based in docker deployed version, with some new features
Try it if you want!
here the links
[https://hub.docker.com/r/christiansicari/nextcloud-mail2deck](https://docker hub)
https://gitlab.com/christiansicari/nextcloud-mail2deck
Hi.
This is quite old and since the creation of the repo I cannot see any further development, even there are some issue requests.
Any status on the mail2deck project?
Background:
I am currently on the go to replace WHUPS from the Horde Groupware with a new ticket system. I do not need a full blown ITIL-driven application, DECK would full fill my needs, if a stable interfacing for creating cards on any controlled external process would be possible.
Anything that can be thrown in a postfix pipe would suit my needs.
Br
Carsten