Stringify, the IFTTT-like service that helped users build in-depth automated tasks, announced today that it’s shutting down. Stringify’s apps will be removed from stores today, with the service being fully deactivated at the end of June.

In an email sent to existing users, Stringify says it will continue to support the service until the end of June, at which time it will shut down, and all user data will be deleted. Here’s the full email:

Dear Shut Down, After nearly five years of transforming how people automate their connected lives, I’m sorry to inform you that we are beginning the process of deactivating the Stringify app. This isn’t a decision we made lightly, but as our focus increasingly shifts to developing new connected-home experiences at Comcast, we made a strategic decision to step back from developing the app. You don’t need to take any action right away. While we will be removing Stringify from app stores today, we will continue to operate and support the service for existing users through the month of June. When we deactivate the app, we will also delete all of your user data. We know that Stringify plays a big part in our users’ daily lives, and we want to make sure everyone has plenty of time to adjust. To that end, I’d also like to offer a couple of recommendations of potential technology alternatives. While I’d encourage you to do your own research, our team thinks these solutions each offer unique value. IFTTT – A great free-to-use service that offers a lot of the same functions and capabilities as Stringify.

Yonomi – Another free-to-use service that supports many connected devices and experiences.

WebCore – For users of Samsung SmartThings platform. Some folks on our team have been using and enjoying it. Thanks again for being part of Stringify. It’s been a true pleasure to work with our tremendous community of users. Please don’t hesitate to email us at support@stringify.com if you have any questions or concerns. Sincerely Mike Yurochko

As an aside, it looks like someone forgot to fill in the $UserName data before pushing that message out the door. Oof.