What is IFTTT and what are its top alternatives?
Top Alternatives to IFTTT
Zapier is for busy people who know their time is better spent selling, marketing, or coding. Instead of wasting valuable time coming up with complicated systems - you can use Zapier to automate the web services you and your team are already using on a daily basis. ...
It manages all your social media in one place. From finding prospects to serving customers, it helps you do more with your social media. The system's user interface takes the form of a dashboard, and supports social network integrations. ...
It is a flexible and effective tool for managing tasks, processes and employees. Made for businesses with a mobile workforce, it connects your office employees with your field service representatives in real time. ...
It is a cloud-based voice service and the brain behind tens of millions of devices including the Echo family of devices, FireTV, Fire Tablet, and third-party devices. You can build voice experiences, or skills, that make everyday tasks faster, easier, and more delightful for customers. ...
Flow is an online collaboration platform that makes it easy for people to create, organize, discuss, and accomplish tasks with anyone, anytime, anywhere. By merging a sleek, intuitive interface with powerful functionality, we're out to revolutionize the way the world's productive teams get things done. ...
Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. ...
It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. ...
It lets you create and manage UI tests that check specific functionality in your website or application. We execute these automated browser tests continuously from the cloud and alert you if anything breaks. ...
IFTTT alternatives & related posts
related Zapier posts
Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.
I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.
For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.
Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.
Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.
Future improvements / technology decisions included:
Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic
As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.
One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.
Achieving #MarketingAutomation using AutopilotHQ
Some of the key aspects evaluated here: - Ability to integrate with Segment or Zapier - Being multi-channel (Not just Email automation) - Dozens of integrations and capabilities: SFDC, In app messages, SMS, Push Notifications, Direct Mail, Segment Events... - Allowing teams to operate outside of engineering dependencies - Segmentation against user attributes / user traits - Static or Dynamic segments - Concept of user journeys - And more
Combined with Segment and its own sets of integrations and capabilities, AutopilotHQ ended up being a very powerful tool for Product Marketing to use at SmartZip.
Couple of years later, there certainly were some overlap with the features offered by Intercom 's engagement module , but our team kept on using this tool given the greater range of functionality / capabilities.