In our observation - our users need to do complex CRUD operations not just from the frontend (web//mobile) but also basis of events happening in other systems or on a scheduled time. Say for instance you got a new win in Hubspot and you got to let your customer success DB updated and a few internal APIs called. The reason you use platforms like DronaHQ is that we make it super simple to write workflows involving CRUD & REST. And for such use cases - we don't want our users to do the hard work of figuring workarounds or write code. So we launch automation 2.0 to ensure our users are able to leverage our powerful workflow tool and respond to events happening outside our ecosystem. Here is DronaHQ's Automation 2.0. has to offer: Automation now has its own process builder to help build processes visually with drag and drop. With this release - automation now becomes capable to serve its customers all by itself. At a high level - given this engine is built on top of the DronaHQ workflow/BPM engine - it inherits a very powerful builder capable to write complex automation rules. For example, in given automation, you may add a branching logic anywhere in the flow as against Zapier's constraint of adding a branch in a working zap only after the last block. Here are some examples of use cases where DronaHQ Automation 2.0 can be put to use: 1) Send personalized newsletters to all your leads/customers/signups 2) On a new subscription from a customer, notify your team and allocate a customer success rep basis the region of the customer
