The Celigo platform provides several ways to build integration logic, and you can combine them in the same integration. The right method depends on what you're building, who maintains it, and how much of the logic you want to reuse. This article describes each method and links to the instructions so you can start building.
Building methods
Flow builder — Use the flow builder to move and transform data between applications. A flow exports records from one or more sources, processes them, and imports them into one or more destinations. Flows run on a schedule or in real time and support branching, lookups, mappings, hooks, guardrails, and AI agent steps. Go to Build > Flows.
API Builder — Use API Builder to create custom HTTP endpoints visually, without writing code. You define an API request, add lookups, imports, tools, guardrails, or AI agents as steps, and define an API response with a response picker that branches on success and error. Go to Build > APIs. See Create and manage APIs using API builder and Build your API – Basics.
JavaScript — Use JavaScript when you need code-level control over API behavior that the visual API Builder doesn't expose. You write the endpoint logic as a script and manage it from the same Build > APIs area.
Tools — Use tools to package a unit of business logic once and invoke it from other resources. A tool is built on a visual canvas similar to the flow builder, exposes a strict JSON input and output contract, and can be published for use as a step in supported resource types. Go to Build > Tools. See Introduction to Celigo tools.
AI agents — Use AI agents when a task requires judgment rather than fixed rules. An agent uses an AI model to process each record it receives, can call the tools you approve, and runs inside the guardrails you configure. You add an agent to a flow or API as a step, and you manage agents from AI studio > AI agents. See Learn about Celigo AI agents.
Compare building methods
| Method | Primary purpose | Typical user | Reuse and governance considerations |
|---|---|---|---|
| Flow builder | Application and data workflows | Integration builders and specialists | Reusable mappings, scripts, connections, and other shared resources |
| API Builder | Visual API development | API and integration specialists | Composite operations, testing, error responses, and integration lifecycle management (ILM) |
| JavaScript | Custom coded behavior | Developers | Code review, testing, and controlled deployment |
| Tools | Packaged reusable logic | Developers and AI implementers | Reuse in supported resource types only; see Introduction to Celigo tools for the supported list |
| AI agents | AI-directed task execution | AI implementers and governed business teams | Tools, guardrails, execution logs, and governance |
Where tools can be used
Tools can be added as a step in flows, in APIs built with API Builder, and in AI agents, and can be exposed through MCP servers. A flow or integration that references a tool can't be cloned, downloaded, or included in ILM.
Promote what you build
Use integration lifecycle management to move integrations, flows, and APIs between environments as you test and release them. Resources that reference a tool are excluded from ILM.