CloudWinks · Foundation apps

TheIntegratorTechnical brief

TheIntegrator is the shared service that changes information from one system into the format another system needs. Teams reuse mapping definitions instead of writing a separate conversion for every connection.

Read the business brief · PDF

1. Architecture in brief

TheIntegrator is the platform’s shared mapping and execution service. It holds mapping definitions, templates, execution records and error records. A server executor runs controlled external calls, pins destinations and writes a journal, with secrets redacted. CloudWinks supplies the application runtime; CosmosCall remains the connection catalogue and KeyKook the credential store.

2. Service boundary and intake

Applications request a mapping run by definition rather than embedding their own conversion. Definitions describe the source, destination and transformation, including common API and file formats. Each run produces an execution record and, if needed, an error record. Flutter and server callers use the same mapping service so conversion is not reinvented in each app.

3. Data handled

The model stores mapping definitions and templates, execution history and error details. Sensitive values are redacted from the journal. TheIntegrator owns the mapping and the execution record. It does not own the provider catalogue, the secret, the business record being written, or the Murphy problem report that may follow a failure.

4. Integrations and ownership

CosmosCall describes the connection; TheIntegrator converts and executes. Roady, MediaMogul, BigTalk and Conductor use this shared service for outbound work that needs mapping or a controlled call. Murphy receives execution problems. TheIntegrator owns mapping and execution, not the schedule, the message or the connection definition. The server-side QuickBooks load (with SSNs routed to the KeyKook vault), bank CSV and live bank feeds, Zibit provider calls and verified webhooks, W-2 and 941 e-file submission and status tracking, DreamDrafter signed webhooks and TheReporter Google output run through TheIntegrator; TheBoss and WorkerBee reference mappings by key.

5. Security and access

External calls use secrets resolved through KeyKook, not credentials stored in the mapping definition. Destination pinning and a journal support controlled outbound work. Execution history is redacted. A mapping definition does not itself authorize every caller to run every destination. Access follows platform authorization and company or owner boundaries.

Competitive context

AlternativeIts focusCloudWinks product focus
WorkatoTransformation maps and field mapping between systems.A shared mapping and execution service used by CloudWinks connection and messaging apps.
Microsoft Power AutomateCloud flows that include data operations between services.Mapping definitions, templates and a journalled execution record, with secrets redacted.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works