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, instead of duplicating the same configuration in each YAML file.
What are Integration Services?
If the same configuration or business logic appears in multiple flows, define it as an Integration Service. You define the service once, and your flows reference it.
Why use Integration Services?
- Reusability - Write the logic once and use it in any flow.
- Centralized configuration - When a database password changes, you update only the service, not every flow that uses it.
- Consistency - All flows use the same connection and configuration settings.
When to use them
Integration Services make sense when you have:
- A database connection that multiple flows use
- An internal API client that requires specific authentication headers
- Business logic that should be defined in one place
Creating Integration Services
Documentation for creating services is coming soon. The feature is under active development.
Managing services
The Integration Services dashboard shows:
- The service name and version
- A brief description of the service
- Which flows currently depend on it
Next steps
- Integration Overview - Learn about integrations
- Using Variables - Manage service configuration with variables