Input
A request, file, email, message or scheduled time starts the process.
How It Works
From event to execution without losing control.
Selfint works as a process engine. It receives an input signal, executes a workflow, transforms data, calls external services when needed and records the full journey.
Base flow
Decision
The workflow defines which steps should run, in what order and under which rules.
Transformation
Data can be mapped, validated, enriched or reorganised before delivery.
Delivery
Selfint sends the result to another system, generates files, publishes messages or triggers the next step.
Tracking
Everything is recorded: state, source, timing, errors and retry options.
How processes enter
- API and webhook: real-time integration with external applications.
- Schedule: periodic tasks.
- Kafka and queues: message-driven volume and decoupling.
- Email poll: monitor mailboxes and react automatically.
- AMQP, MQTT and Pub/Sub: additional message-based trigger models.
What happens in the middle
- Workflows can be created, paused, resumed, duplicated, versioned and rolled back.
- Mappings and OpenAPI import help adapt data between systems.
- AI can be used inside workflows or to suggest a draft workflow design.
- Connections and credentials are centralised and testable.