SurveyCTO submissions, pulled into Karagem every hour.
Karagem connects to SurveyCTO directly. You give it your server address and account, name a form by its ID, and from then on its submissions are pulled into a Karagem survey — once when you ask, and every hour if you switch that on. Nothing about how your enumerators collect changes.
In the productNative connector: server login, forms by ID, on-demand or hourly sync.
How the connector works
SurveyCTO exposes each form’s data over its API in a wide format — one row per submission, repeat groups flattened. Karagem reads that, infers the questions from the columns the first time (numbers, dates, GPS points and text), creates the survey, and imports every submission with its SurveyCTO KEY as the external id, so nothing is ever imported twice.
There is one honest limitation: SurveyCTO does not publish a “list my forms” call, so you add each form by its ID rather than picking from a menu. The ID is on the form’s settings page. Once added, the form appears in the connection like any Kobo or ODK form, with the same hourly switch.
What happens after the data lands
Imported responses are ordinary Karagem responses. They count toward indicators whose data source is the survey, they pass through the approvals queue if the survey requires it, the daily quality scan checks them for duplicates and outliers, and they appear in donor tables in the format the award specifies.
Because the sync is hourly, early warning works on it too: a forecast is only as current as its last input, and an hour is close enough to live for anything a programme decides on.