Skip to main content
Krosyn is launching soon. Join the waitlist for early access.Join waitlist
Krosyn

Documentation

Learn how to use Krosyn to connect your applications.

Getting Started

Welcome to Krosyn, a middleware platform for building data connectors between your applications and external services.

What is Krosyn?

Krosyn lets you create connectors that receive incoming data (via API), optionally enrich it with external lookups, transform it using a built-in expression language, and send the result to a target API. Everything is configured through the web UI with no coding required.

Each connector follows a three-step pipeline: Trigger, Process, and Perform. This pattern covers the majority of integration use cases, from webhook forwarding to CRM syncing to notification routing.

Quick Start

Follow these steps to set up your first connector:

  1. Create an account and set up your organization. You can start on the Free plan with up to 2 connectors.
  2. Create a connector from the Connectors page. Give it a name and paste an example JSON payload that represents the data you will send to it.
  3. Configure the endpoint. Each connector gets a unique trigger URL with authentication tokens (bearer token and/or secret token). You will use this URL to send data to the connector.
  4. Set up the steps. Configure the Trigger condition (when should it run?), the Process step (enrich data from an external API), and the Perform step (what API to call with the transformed data).
  5. Enable the connector. New connectors start as disabled. Toggle the status to enabled on the connector detail page before sending test requests.
  6. Test it. Send a POST request to your trigger URL with a JSON payload. Check the Events page to see the execution result, including request/response details and timing.

Key Features

Expression Language

A powerful DSL with 55+ functions for string manipulation, math, comparisons, array operations, date/time, and more. Reference incoming data with $payload.field syntax.

Secrets Vault

Store API keys and credentials securely. Secrets are encrypted at rest and can be referenced in expressions using $secret.NAME. They are automatically redacted from event logs.

Retry & Circuit Breaker

Failed requests are automatically retried with exponential backoff. If a target endpoint keeps failing, the circuit breaker temporarily blocks requests to prevent cascading failures.

Full Observability

Every execution is logged as an event with status, timing, full request/response details, and error messages. Debug connector issues by inspecting what was sent and received.

Next Steps