Weik.io

Integration Services

Define and manage reusable services for integration flows

Integration Services let you build custom logic or connections once and reuse them across multiple integration flows. Stop copy-pasting the same database connection setup into five different YAML files.

What are Integration Services?

If you find yourself writing the same configuration or business logic in multiple flows, it belongs in an Integration Service. You define the service once, and your flows just reference it.

Why use Integration Services?

  • Reusability - Write it once, use it everywhere.
  • Centralized Configuration - When a database password changes, you only update the service, not every flow that uses it.
  • Consistency - You don’t have to wonder if flow A is using the exact same connection pool settings as flow B.

When to use them

Integration Services make sense when you have:

  • A database connection that multiple flows need to talk to
  • An internal API client that requires specific authentication headers
  • A chunk of weird legacy business logic that you really only want to write once

Creating Integration Services

Documentation for creating services is coming soon. The feature is under active development.

Managing Services

The Integration Services dashboard shows you:

  • The service name and version
  • A brief description of what it actually does
  • Which flows are currently depending on it

What’s Next