Every localization operation has rules that are specific to it: a customer who sends incomplete briefings, deadlines that must never fall on a weekend, or an in-house team whose capacity decides who gets which job. BeLazy's user interface-based configuration covers what most companies have in common. The Orchestration Hub is the place where you go the extra mile.
Orchestration in BeLazy is not one tool. It is a set of well-defined points where you can customize and connect, each running in a place you already use and trust: BeLazy itself, your Google Drive, or your content management system. In most cases you do not need a separate orchestration platform at all.
The principles behind it
- Configuration first. Mapping, exception rules, bundling, auto-approval and instructions handle the work every customer needs, without code. Before you write anything, check whether a rule can do it. See Metadata and exception-based configuration.
- APIs that hide the systems behind them. BeLazy's APIs work the same way whether your BMS is Plunet, XTRF, Protemos or Google Sheets, and whatever TMS or portal the work came from. Your code talks to BeLazy, and not to each system separately.
- Code runs where you already are. Code that runs inside tools your organization has already approved does not need a new round of security, IT and procurement review. A separate orchestration platform would.
- Let AI write the script, not do the task. If an AI performs a task, the result can differ every time. If an AI writes a script that performs the task, the script does the same thing every time, and you can read and test it. LLMs such as Claude, Gemini or ChatGPT write reliable scripts for BeLazy when you give them the BeLazy API definition and a clear description of what you want.
The building blocks
- Configuration in each connection: the rules that apply to every project automatically.
- APIs: the Project Ingestion (workspace) API to create projects, the Update Opportunity API to correct or enrich incoming work, the BMS Extension APIs to act on projects after creation, and the AI Hub APIs for automated workflow steps.
- Events: the same events can send webhooks, trigger notifications, and run JavaScript on individual items inside BeLazy.
- Google Sheets and Apps Script: all project data in a spreadsheet you own, and scripts that can combine it with data BeLazy does not have, such as calendars or capacity. See Google Sheets - built-in project management and reporting.
- CMS extensions: plug-ins, webhooks or editor extensions in your CMS or PIM that call BeLazy directly, so content never has to leave the system it lives in.
- External orchestrators such as Make.com or n8n, and serverless functions, for the cases the options above do not cover. See iPaaS orchestrators and AI execution.
Which option for which need
| What you want to do | Where it runs best |
|---|---|
| Correct or complete what a customer sent before you accept it | Update Opportunity API, triggered by the Ready opportunities webhook |
| Act in Plunet, XTRF or Protemos after the project is created: assign vendors, move the last deadline earlier, change price lines, fill custom fields | BMS Extension APIs, triggered by an event |
| Assign vendors based on capacity, calendars or work type | Google Apps Script on the BeLazy spreadsheet |
| Start work from a spreadsheet entry, a Slack message or an email | Google Apps Script, or the built-in features |
| Send content from a CMS or PIM for translation | A CMS extension calling the Project Ingestion API, or the iLangL and Crowdin connectors |
| Check a system that has no events, around the clock | A time-driven Google Apps Script (as often as every minute), or a scheduled Power Automate flow on Microsoft |
| Very high-frequency or must-never-miss polling | A serverless function or an iPaaS orchestrator |
| Reporting and dashboards | Google Sheets with Looker Studio, Power BI, Tableau or similar |
Tip: Not everything has to run invisibly. For some steps it is better if a person decides when the automation runs, for example by running a script from the spreadsheet menu. This is partial automation, and it is often the safer first step before full, around-the-clock automation.