Register now for API Summit 2025!

What the Flow Editor offers

The Konnect Flow Editor represents API workflows as visual diagrams. Each processing step appears as a component on a canvas. Lines connect components to show how data moves through the system. Instead of defining workflows through configuration syntax, you build them by arranging visual elements and drawing connections.

For teams that work visually, or for situations where you want to quickly sketch out an orchestration pattern, the Flow Editor provides an intuitive interface that:

• Accelerates onboarding: Many teams find visual tools to accelerate the initial learning curve. New team members can examine a workflow diagram and understand the overall architecture quickly. They can start designing workflows immediately and let the editor handle the technical formatting.
• Enables natural collaborative design: When cross-functional teams discuss API architecture together, visual representations provide intuitive common ground. Product managers, architects, and engineers can gather around the same diagram, pointing to specific components and discussing logic. The visual format makes these conversations flow naturally.
• Drives efficient prototyping: When exploring different orchestration approaches, many teams appreciate the speed of visual design. Arrange components on a canvas, try different connection patterns, see the overall structure change in real-time. Once you've settled on an approach, refine the details, and then manage via configuration files once implemented.

The right tool for your team

Different teams have different preferences, and those preferences are valid. Some engineers strongly prefer working directly with configuration files — they find it more precise, more efficient, and better integrated with their development workflows. Others prefer visual tools that let them see and manipulate workflows graphically.

The Datakit Flow Editor provides choice. Teams that work visually have a first-class tool designed for their preferred approach. Teams that prefer configuration files continue to have full access to that method. Many organizations find value in supporting both, letting different teams or different situations use the approach that works best.

The question isn't which approach is better — it's which approach works best for your team's needs, preferences, and workflows. The Flow Editor ensures that teams preferring visual tools have an excellent option available.

Getting started

Organizations typically adopt the Flow Editor in one of several ways:

• For new teams: Start with the visual editor to learn Datakit concepts quickly, then choose whether to continue visually or transition to configuration files based on team preference.
• For existing implementations: Import current configurations to create visual representations, useful for documentation, review, and understanding complex workflows.
• For specific use cases: Use the visual editor for particular scenarios—prototyping, cross-team communication, troubleshooting—while maintaining configuration-based workflows for other purposes.
• As a team preference: Some teams simply prefer visual tools. The Flow Editor provides a complete, production-ready workflow development environment for those teams.

There's no prescribed path. Different organizations find different approaches valuable based on their team composition, processes, and preferences.

Learn more at API Summit 2025

Whether you're new to Datakit and looking for an accessible entry point, managing complex workflows that benefit from visual representation, facilitating cross-team collaboration, or simply prefer working with visual tools, the Flow Editor provides a capable, production-ready option.

If you want to learn more, make sure to register for API Summit — either in person in New York or virtually. We hope to see you there!