Emails as unique object type
It would be great to have the option for forwarded emails to be saved to their own unique object type in addition to the current functionality of appending them to the Daily Notes.
13 Comments
Sign in to comment
As a Mac user I'm used to drag and drop files (and also mails) from the file system or one app to another. The best implementation would be, if Capacities would have an object type email out of the box and the user could drag and drop an email from his mail app (or at least a *.eml file) to the Capacities app icon (or somewhere on the app window) to import the mail as an object. Capacities should recognize it as an object of the typ email and set the meta data (sender, recipients, date, attachments) automatically.
Info emailed into capacities comes in as a wacky table format & is quite unusable without serious manual intervention. I don't understand what the idea of formating it into a table is meant to accomplish. And, all the sentences are concatenated together with no separation between lines or paragraphs.
Just put the body text into a page object and link to images, etc.
yes! I created my own email object type so I could organize this better. I would love if the body of the email came over in a more readable way immediately instead of a text box I have to resize
The plans of adding an email object is one of the things that drew me to Capacities in the first place. The sooner this can be done the better. I receive a lot of information that I want to capture through email, be it stuff from a client, newsletter, or technical information from a partner. Right now I find my self jumping between Gmail and Capacities and other tools to find stuff. I'm trying to get down to one source of "knowledge".
An email object would be great, but I would want to be able to add custom properties too e.g. Project or Area, as well as connecting with a person object.
New user, I agree that some form of automation would be nice however that presents itself. I would like something that would receive the email, separate any attachments and either have a default object or a user selected object for the email.
Even better would be if they could be configured to any existing object type - instead of hardcoded in as an "Email" object. This would be more in the spirit of Capacities in my opinion; leaving the control/configuration in the hands of the user.
As an example, I have an Activity object type. It would be sick to configure my emails to save to that object type and pre-fill it's Type property (a text property I created in it) with "Email".
This could be done in tangent with a system-configured default email object type. Essentially, Capacities could have a default build like it does for other objects, but not cage the user into using a specific system object type.
This would be fantastic! properly formatted in a designated object type would create so much less hassle.
Yes please! Plopping them in as just text is only somewhat helpful.
This is an amazing idea. I'm sure many of us have created our own hacky version of an 'Email' object to turn a received email into. Here's mine, and I'm sure the Capacities team could do a far superior job.
Please add!
seems like a no brainer for organization.
Just typing a comment in additon to voting because email object would be amazing.