Introduction

Before taking a dig in about how corezoid works, let's talk about what corezoid is actually. So talking in layman's language, Corezoid is an engine that lets you run your processes or algorithms on their server. It helps you with their User Interface for building your processes as you are building flowcharts.

As we start building our processes, Corezoid helps us begin with start and end nodes. Nodes are engine processors where you can find your responses from individual processes which corezoid supports.

Starting with the starting node, it's nothing but where your logic starts you move on from node to node. As we move towards the node, corezoid gives every response value at the end nodes. Corezoid also has nodes based on code-logic, conditional statements and provides API that we usually perform in our backend architecture.

After your process is complete and you have your responses. It is time to expose the process to the outside environment. Corezoid supports three APIs from which API-V2 and SyncAPI widely used. Corezoid API-V2 and Sync-API have a difference which is V2 does not returns custom response to the outside environment where as Sync-API is used for return custom responses to the outside environment.

Corezoid can be an effective engine when it comes to User Interface. As there are inbuilt processes and is widely used in MNCs for their processes and can be supervised and also a human-takeover is easily possible in the engine as compared to our native engines.