iPaaS orchestrators such as Make.com, n8n and ActivePieces connect many systems through visual scenarios. They work well with BeLazy, and many BeLazy customers use them. In most cases, however, you no longer need one: BeLazy's configuration, its APIs, Google Apps Script and CMS extensions cover the typical needs inside tools you already use. This article explains when an orchestrator is still the right choice. For the full picture, see The Orchestration Hub: choosing where your automation runs. 

When an orchestrator is the right choice

  • You already run scenarios in Make.com or n8n, and your team knows how to maintain them.
  • The scenario connects many SaaS tools that have ready-made apps in the orchestrator, and the logic is simple and deterministic: if this happens, always do that.
  • You need very high-frequency or must-never-miss polling of a system that sends no events.
  • Your organization has already approved the orchestrator, so using it adds no new security or procurement review.

When another option is better

Our experience is that visual scenarios work well up to about ten steps. Beyond that, conditions multiply: a workflow step cannot be closed until a vendor is assigned, dates are set and a file is uploaded, and every precondition needs its own branch and its own error handling. Scenarios also depend on app versions, which some orchestrators update automatically and others leave to you.

For these cases, code is usually easier to maintain, and an LLM can write it for you. Use:

  • the Update Opportunity API to correct or enrich incoming work,
  • the BMS Extension APIs to act on projects after they are created in Plunet, XTRF or Protemos,
  • Google Apps Script on the BeLazy spreadsheet for anything that needs data from several projects or from other sources, such as capacity-based assignment or around-the-clock polling,
  • a CMS extension calling the Project Ingestion API to send content for translation.


Connecting an orchestrator to BeLazy

Make.com has a native BeLazy app. n8n and ActivePieces have no native app, but they can read the BeLazy API definition and call the APIs directly. In every case you need an API token from Api access tokens in the profile menu.

To start a scenario when something happens in BeLazy, set up a webhook in the profile menu under Webhooks and use the orchestrator's webhook URL as its target.

If you do not want to run an orchestrator yourself, BeLazy can host Make.com scenarios for you. Contact us for details.

AI agents

AI agents such as Claude can also call the BeLazy APIs directly, because the APIs are simple and fully described in the API definition. Agents are useful for one-off tasks and investigations, and can write a script rather than perform routine tasks itself: a script gives the same result on every run, and you can read and test it.