11 ms·
Cool project. One aspect of these integration systems is that the volume and velocity of integration development is one of the main ways they show value. Zapier
by reilly3000 7y ago
Cool project. One aspect of these integration systems is that the volume and velocity of integration development is one of the main ways they show value. Zapier claims 1500+ integrations, and they have many competitor with similar counts of integrations. Somehow, they always seem to not have that thing I need.
I wonder why, in this era of Swagger / OpenAPI / Postman Collections / API Gateways ... why this is so difficult? I feel like there was a promise that integration would become more magical at a rapid clip, but as it stands it just seems like there are more options but no less headaches.
- toomuchtodo 7y agoA lot of APIs don’t support the tooling you mentioned, have all sorts of rough edges (return improper http codes, or don't return them at all), or act...quirky at scale (based on my experience at an automation workflow org). Of course, as APIs improve (OpenAPI, etc), the barrier to entry for all workflow tools declines (which is a good thing!). You're then just serializing and deserializing JSON (or a mutation thereof) between two or more steps. Just as Google makes their Terraform provider a first class citizen by autogenerating the Terraform provider based off of their APIs (Hashiconf 2018 SF talk), so could integration partners for workflow automators. Just takes time for the ecosystem to mature.
- infectoid 7y agoDoes Datafire meet some of your requirements? https://github.com/DataFire/DataFire https://github.com/DataFire/DataFire I've used it before and it's not too bad.
- reilly3000 7y agoThanks for sharing, that is definitely compelling. I like that their integrations cover lots of API methods, whereas a lot of simpler services only cover a few.