Read the technical brief → · PDF
1. What it does and why it matters
CosmosCall keeps a catalogue of service providers, connection details and information formats. It describes how requests and responses map between systems and includes connection-test information. This gives integrations a common structure and makes repeated connection work easier to manage. Each connection to an outside service, such as Google, uses a KeyKook connected account that belongs to a person or a company, and other people and companies cannot see it. CosmosCall points to that account, and secrets live only in KeyKook.
2. How the apps work together
Roady uses mapping and calls for location services; MediaMogul uses the connection model for its own integrations. KeyKook supplies protected credentials. TheIntegrator is the shared conversion/execution service, keeping information transformation separate from the catalogue of outside connections.
3. Using it with outside applications
CosmosCall’s external error-reporting design lets another application make a call that becomes a Murphy error report. The outside app uses the connection service without adopting unrelated CloudWinks business apps. CosmosCall describes the connection, TheIntegrator adapts the information and Murphy keeps the problem record.
4. Other choices and the CloudWinks fit
| Alternative | Its focus | CloudWinks product focus |
|---|---|---|
| Postman | API cataloguing, design, testing and monitoring. | Connection definitions tied to CloudWinks applications and shared services. |
| n8n Webhook | Incoming events that start configured workflows. | A focused connection model with shared mapping and business-app context. |
5. Building a competitive edge
Give teams a reusable, business-aware connection model rather than a collection of one-off scripts. Make the path from an outside event to its business outcome easy to follow. Prioritize well-defined integrations and useful diagnostics over the size of the connection catalogue.
← More Foundation apps apps · All application briefs · How the framework works