Originally Published: July 16, 2016 when Zapier had 500+ Applications!
We began planning our public API implementation in late 2015. We had numerous requests for full Read/Write API access to the data model and were responding to stated customer needs.
By early 2016 we had the first version of the API tested and preview-ready. But an interesting thing happened -- we started hearing that people wanted a "simplicity layer" on top of the programmer-level API. What form would that take, exactly?
We started hearing that people wanted a "simplicity layer" on top of the programmer-level API
Well boy howdy, were we ever glad to find Zapier! Here's the thing, Zapier provides a "point solution"-oriented approach that addresses specific needs that real people in the real word have identified—needs that were outside our direct experience.
The core trigger-action model implemented by Zapier is super easy for non-technical users, and the promise of building a simplicity layer was compelling and real. With Zapier's codeless integrations ("Zaps"), extending Lucid Meetings with workflow automation became easy as pie.