Learn more about Flows here.

​
Managing Flows with Lume

With Lume, you can build and manage multiple flows, potentially even hundreds or thousands. As an API, Lume can be embedded anywhere in your code, fitting seamlessly into your flow management architecture.

​
Key Aspects: Flow Names and Tags

Flow names are crucial for tracking and reusing deployed flows. Use these names to route specific data to the appropriate flows. Additionally, you can add tags to your flows to better organize and filter them based on different criteria like environment, team, or purpose.

Example:

If you are normalizing data from multiple data feeds (Feed A, Feed B, and Feed C) into one internal schema, you could create three flows with the following names:

  • FeedA_to_internal
  • FeedB_to_internal
  • FeedC_to_internal

And add tags like:

  • environment:production
  • team:data-integration
  • type:normalization

When data comes in from Feed A, route it to the FeedA_to_internal flow.

Refer to Use Flow to learn more.

​
Best Practices for Naming and Tagging Flows

  • Organize Your Flows: Use flow names and tags to organize your flows. For example, create different flows per customer, per integration, or per customer system.
  • Code-Retrievable Names: Ensure names are retrievable via code. Sometimes, using a hash can work well if you want to embed the flows.
  • Consistent Tagging: Develop a consistent tagging strategy to make flows easily filterable and manageable at scale.

​
Leveraging Existing Flows

  • Reuse for Consistency: Leverage existing flows if you want to use the same mapper on new data to guarantee consistent output.
  • Create New Flows for New Mappers: Generate new flows if you need to create new mappers for different data sets.

For more detailed guidance, refer to our Getting Started documentation.

QuickstartEditing Target Schema