add integration with ifttt.com
could be used to notify others when you clock in/out, arrive at job site, or whatever else someone could think of. As an input, the pass data could be location, time clocked in, job name, or hours worked for the day, week, month, last 14 days, hours for the day before. As an output, could accept tags or hash tags to clock in/out by job, return clocked time for the past day/week/month/14 days/ pay period, and could accept input by e-mail or text. Could accept input from the time widget to send accumulated time for d/w/m/14 days/pp to a specified e-mail address, or dropbox.com
Joshua
shared this idea
-
I watch IFTTT's site periodically. It looks like they are getting closer to enabling partner channels for smaller players. Though this is still way outside of our priority list, it's interesting to me personally. I'll keep on watching it to see if/when they do open up. At the very least, given the form at https://ifttt.com/platform, we'll need to solidify our API a bit more before being able to approach them anyway.
-
I could see something like that being useful. But given what you described below, I'm not sure what value ifttt.com would provide. I was not aware of that site until you posted this thread so my impression may be off, but it seems to me that the value that they provide is in the defined channels. If I understand the model correctly, I'd need to work with them to create an HoursTracker channel. This would only be necessary to wire up HoursTracker events to other channels, right? Regardless, the things you describe below look like they could all be implemented as features of HoursTrackerCloud.com without tying into ifttt.com at all.
Regarding feature creep, sure, this is way outside of our (current) core competency but I could see applicability both from a power user and employer perspective.
-
Joshua
commented
David, good point. I didn't consider that hourstracker doesn't do live syncing to the cloud, so I guess that should be a feature request first. That being said, there are a number of cases where it would be beneficial for some other web service to know and be able to perform an action based on whether you were clocked in or not. with ifttt integration, alerts could be sent to employers when employees showed up to job sites, or left unexpectedly, or even were going into overtime. While this is essentially feature creep, I can see where it would be a beneficial feature as part of the scope of hourstracker.
-
Aside from being "neat", what's the business case here? The biggest problem I see is that until we have a true data sync implemented, event-driven behavior is not really possible. Right now, we don't know anything until the user chooses to make a backup or an automatic backup occurs.
-
Joshua
commented
Oh yeah, send current time and allow clock in/out and selection of job from pebble watch. When it comes out of course.
