KoboToolbox Integration


“KoboToolbox is a suite of tools for field data collection for use in challenging environments. Our software is free and open source. Most of our users are people working in humanitarian crises, as well as aid professionals and researchers working in developing countries. Our teams of developers and researchers are based in Cambridge, MA and many other places around the world.””


How KoboToolBox can be used with Corteza

One of the key features of KoboToolBox is the ability to create custom forms to suit your data collection needs. These forms can be accessed either Online or Offline allowing for their use in environments where internet connection is not possible.

Due to Corteza being a Web Based application an active internet connection is required to use Corteza. This allows Corteza to remain lightweight and usable on machines regardless of their processing power. This also means that Corteza may not be an adequate solution for use in the field.

This means that KoboToolBox and Corteza have synergistic properties where KoboToolBox can be used to collect the required data and once an internet connection is reestablished the data can easily be pushed to Corteza for  effective processing and management.

Read more

Corteza Gateway

Corteza, the leading open-source low-code development platform just had the first release of its routing and processing gateway for HTTP requests and I’m here to tell you all about it.

As an ongoing effort, the plan for this routing subsystem has always been

  • to minimize the effort in adding dynamic routes with any validation
  • to be able to connect the routing possibilities with most of the Corteza subsystem
  • to take the developer-first approach in modular architecture and data flow transparency

During our development processes and via a wide range of our client’s proposals and business requirements, we quickly noticed we outgrew the possibilities Corteza offered via it’s sink feature.

Sink allowed a Corteza developer to detect incoming HTTP requests on a fixed route via a generated signature wrapped in query parameters and provide the request to the automation scripts.

But having only one route with limited capabilities to validate query parameters, headers and have an overview of the amount of incoming data fell short.

Read more