Allow emailing into a specific project
It would be useful to be able to email into a project- specifically if we have automated reports to share with clients (Google Analytics reports, regular SEO reports etc), we'd like to send these into Freedcamp rather than via email, as it keeps it all within one place
Hi All,
It is done. You can create tasks, discussions, issues and upload files by emailing them in.
You can provide unique emails to people not having Freedcamp account to do the same (use it with caution).
This feature is part of Lite/Business and Enterprise plans in Freedcamp.
Cheers,
Igor
-
Anonymous commented
Hi,
I think this is a huge feature that's missing. Even if it were applicable in issue tracker, that means a client query can just be forwarded straight into freedcamp and an issue created. There should be standard email address with predefined syntax for the subject line. Like evernote or freshdesk "@projectname" etc.
-
James Buller commented
Hi
I'd like to use Gmail filters or IFTTT.com to automatically pipe certain emails into Freedcamp and have them create new or update ToDos.
It would be fab to also automatically set the due date ie response time because I'm thinking of dealing with enquiries.
Basecamp provides a unique address per person per project. All emails sent in either create a new thread or update an existing one (I guess by subject).
It would be nice to do it with a human readable/memorable address. It would also be great to be able to choose what kind of entiy it created in Freedcamp in some way.
James
-
dotcominfo commented
I think this is a great idea. To compare, Basecamp assigns a unique email address to every project you create, which you can use to forward emails to basecamp with. The core functionality of this is to create tasks (to-do's) in Basecamp based on the email being forwarded.
The have some syntax tags you can use to format things like due dates, task titles, etc. but it's a pretty simple setup. This would be a very valuable add-on for Freedcamp.
-
Igor commented
In this case we will have to add to handle a task to be created by a non existent Freedcamp account. We will extract their details from email FROM somehow.
-
Igor commented
"Why adding a task via email would be helpful is that there are some team members that would only send tasks every now and then and so we don't want them to have to login to freedcamp when they have a request for our team. All we would need to tell a lot of people in our company is to use a certain email address whenever they need to send a task for our team so they don't worry about setting up an account at freedcamp."
-
Joel commented
I am probably overlooking some aspects but perhaps you could use the gmail model for email, on gmail lets say your address is xyz@gmail.com. You can receive emails to xyz@gmail.com, or xyz+2015@gmail.com or anything after the + (I use this for testing register a lot and it works well)
In freedcamp, you could provide one email address for company, then combine the company+project1@freedcamp.com
company+project2@freedcamp.com
etc.Then I can give email address of company+project1@freedcamp.com to my client for project 1, company+project2@freedcamp.com to client for project 2, etc.
When the email is received, it goes to the correct project as discussion. IF the email sub project is not recognized, it would need to go into some kinda bucket and admin would need to resolve it I guess.
-
Igor commented
Hi Pat,
I see only one option which is easy to use - we give you one and only one email to remember. We also add parsing of attachments into incoming emails (we do not have it now). All emails arrive to a drop box where you decide what to do with it - add to existing TODO/Discussion as a comment or create a new one. We will have to eventually add support to create an Issue in Issue Tracker application or a Wiki, I guess.
Igor
Freedcamp -
Pat Eyc commented
I want to add some thoughts too; you could add an unique link to every group/to/project combination and this could be either an email address (like ad145141s4@basecamp.com) where the ad145141s4 is the link to parse it....
The reason I ask is: suppose a client sends me an email with attachments and lot's of bla bla bla- I want to add it as a discussion or to do or.... so you both have to parse the attachments and email content -
It is not hard to do routing. But how would you generally handle a bunch of emails associated with different projects (say you have 20 projects), TODOs (say you have 20 TODos in each project, Discussions (say you have 20 in each project) and Files.
Let's say you want email a file to a project 15. We will have to provide you a unique email address for it or you will have to type subject - Project 15 - files. But if you make a typo and type 'Poject15 - files' it will not be parsed properly.
I assumed you used this feature elsewhere. How to you handled your part where you have to remember/save somewhere correct entry points by email to your projects? Do you like routing to be based on typing correct subjects or a bunch of unique email addresses. However I doubt someone will maintain a contact list of 20 emails for each TODO for each project.
May be we should allow post to project - some place where you can decide what goes where inside Freedcamp?
Thanks
Igor -
Joseph Theuerkauf commented
While i can't speak for the original requester, my impression of this would be that using Subject or Body template strings, one could send email to a Freedcamp email account (perhaps with some in-message authorization code or Freedcamp whitelist per-account to avoid spam). Based on the values in the templates, the email content (body, attachments, etc.) could be routed to particular projects, TO-DO items, etc.
For example, based on the original request, it seems like a good way for attached reports to automatically land in a Project's Files area for group review.