Orchestration Layer: Embedded Workflow Builder & Visual Integration Editor for B2B SaaS
Create new end-user publishable integration templates & workflows visually in Cyclr's workflow builder or via API
What is the Orchestration Layer?
The Orchestration Layer is where you create the connections/instructions between your connector and those of third-party applications.
It adds the ability to manage data formatting between separate services, where requests and responses need to be split, merged or routed.
By adding this abstraction layer you provide your API with a level of intelligence for communication between services, while handling vital authentication tasks.
How does Cyclr's visual drag-and-drop workflow editor work?
Cyclr provides a visual workflow builder that allows B2B SaaS product teams and customer-facing teams to design, test and deploy native integrations without writing custom API code for every endpoint.
- Trigger and Action Mapping: Users select an event trigger (such as a new CRM contact or updated invoice) and map subsequent actions across third-party applications using prebuilt or custom connectors.
- Low-Code Logic and Transformation: Native step functions handle data transformation, filtering, conditional branching, loops and pagination directly within the visual interface.
- Reusable Integration Templates: Product teams can publish standardized integration templates to accelerate customer deployment across segregated Accounts.
- Embedded UX Components: SaaS vendors can embed simplified integration management directly into their own UI, allowing end-users to activate and configure workflows inside the host product.
Every workflow built in the visual editor runs on Cyclr’s multi-tenant infrastructure, governed by a central Console that enforces tenant isolation, credential security and operational monitoring.
Data Orchestration Tools
Set-up, test and publish integrations with ease
Field Mapping"> Field Mapping
Integrations can be as simple as A to B or as complex/multi-step. With Field Mapping you can map data from one app to another which means it can easily move between applications no matter how complex.
Testing"> Testing
Testing tools are available to use before integration publishing. These tools will scrutineer the data flows between apps. You can then access transaction logs to help understand any issues.
Templating"> Templating
Integrations can be custom one-off integrations or they can be re-usable templates that you can publish natively from within your application for your end-users to consume.
Logic Tools
Tools to help you move, split and control your data
Decision
Branch execution of your workflow based on data retrieved, using a full range of logical conditions including: equals, not equals, greater than, less than, in, or contains.
Delay
Pause a workflow for a defined number of minutes, hours, days, or longer. Use data from previous steps to dynamically control the delay.
Wait Until
Pause a workflow until a fixed point in time, either hard-coded or dynamically defined based on data retrieved in a previous step.
Annotate
Annotate workflows to create notes or reminders for yourself or for fellow colleagues who may be picking up and editing a workflow.
Utility Connectors
Enhance workflows and APIs with clever, value-add, Utility connectors
Universal Connectors
Universal connectors give you the ability to connect any data source to any of the application connectors in our library.
Database
Store values between integration run-times to enable smarter, more dynamic integration workflows.
Validation
Validate and filter data as it passes through your integrations – so you only work with the data you need.
MCP Triggers
Trigger workflows via MCP in your users’ LLM of choice, enabling enhanced processing & governance.
Scripting
Add JavaScript anywhere; on the Connector or Method level, so you can customize your processing.
Utilities
Additional Utility tools, including storage, Regex, validators, workflow linking and more.
Or Orchestrate Data Directly Through Our API
Our GUI interface is powerful, but you can step around it should you choose. Our orchestration API enables developers to access any data source within our connector library without the need to pre-build an integration template.
Directly pull data into your SaaS application for processing or display.
Data on Demand
Combine These Tools with Connectors to Create Integration Templates
Your templates can be simple point-to-point integrations or more complex workflows that combine multiple applications and logic tools.
These are quickly and easily created in your management console, allowing you to publish them directly into your application for your users to activate.
Integration templates are cataloged and searchable. Tag each template for easier management and deployment.
Tools to Manage Integration Performance at Scale
As your integration templates are installed into an increasing number of your end-user’s accounts, you’ll want to be able to monitor performance and uptake.
Our Performance Layer is a set of reporting and monitoring tools to assist you in managing integrations and user accounts at scale.
What are Integration Management tools?
Frequently Asked Question About Cyclr's Embedded Workflow Builder
How does Cyclr maintain tenant isolation when running customer workflows? ↓
Cyclr uses a multi-tenant architecture where a single central Console governs segregated customer Accounts. Each Account maintains isolated credentials, API tokens, execution logs and environment configurations, preventing cross-tenant data exposure.
Can non-technical teams create and maintain integrations in Cyclr? ↓
Yes. Cyclr’s drag-and-drop workflow builder enables product managers, solution engineers and customer success teams to construct, test and maintain integrations visually, reducing engineering backlog pressure.
How are MCP-triggered workflows secured in Cyclr? ↓
MCP-triggered workflows run through managed MCP PaaS servers equipped with strict authentication, authorization, rate limiting and scoped permissions. AI agents can only invoke specifically approved tools and workflows defined in the Cyclr Console.
How much engineering time does an embedded iPaaS save compared to building in-house? ↓
Building and maintaining native integrations in-house requires dedicated engineering resources for API research, authentication handling, data mapping, rate-limit management and ongoing maintenance whenever third-party APIs update. A Native Embedded iPaaS reduces initial development time by up to 80% through prebuilt connectors, reusable workflow templates and visual data mappers. It also offloads long-term API maintenance, allowing core engineering teams to focus on core product features.
Can existing in-house integrations be migrated to Cyclr without customer disruption? ↓
Yes. SaaS companies can migrate existing custom integrations to Cyclr progressively. By recreating workflow logic in Cyclr’s visual editor and re-pointing authentication endpoints, teams can transition active accounts without breaking active customer connections or requiring end-users to re-authenticate.
How does Cyclr's orchestration layer power embedded workflows for B2B SaaS? ↓
Cyclr’s orchestration layer serves as the engine for all embedded workflows. When an end-user configures an integration using Cyclr’s embedded visual editor or prebuilt templates, the orchestration layer receives the event, normalizes the payload, executes the required transformation logic and routes data securely through third-party API connectors.
By separating visual workflow management from backend execution, Cyclr delivers headless enablement, allowing workflows to run seamlessly via embedded UI components, direct API calls or MCP interfaces.
Why do SaaS companies need an integration orchestration layer instead of simple point-to-point webhooks? ↓
Point-to-point webhooks handle simple, single-step data passing between two systems. An integration orchestration layer handles complex enterprise workflow requirements, including:
- Conditional Logic & Branching: Decision trees based on real-time payload values.
- Data Normalization & Mapping: Transforming field structures between disparate third-party APIs.
- State Management & Retries: Queueing transactions and automatically retrying requests during target API downtime.
- Multi-Tenant Governance: Enforcing tenant isolation, centralized credential management and operational auditing across all customer Accounts from a single Console.
How do reusable integration templates connect embedded workflows to the orchestration layer? ↓
Reusable integration templates are pre-packaged workflow configurations built inside the orchestration layer. Product teams design standardized workflow logic once in the Cyclr Console and publish it as an integration template. Customers can then activate and customize these embedded workflows inside your SaaS product with minimal configuration, ensuring rapid delivery without multiplying engineering maintenance.