Celigo · iPaaS · Integration

Celigo Integration: How It Works, What It Costs and When to Use It

Celigo connects CRM, ERP, ecommerce, EDI and data platforms without hand-coded middleware. This guide explains how a Celigo integration is built, the difference between Integration Apps and templates, what the 2026 AI features actually do, how pricing works, and when Celigo is the right platform for your business.

Key Takeaways

  • Celigo is an integration platform as a service (iPaaS). Its builder, integrator.io, moves data between applications through flows made of exports, lookups, mappings and imports.
  • Start from a prebuilt Integration App or template where one exists, such as Salesforce–NetSuite or Shopify–NetSuite, and build custom flows only for the gaps.
  • Celigo is priced by endpoints and flows across Standard, Professional and Enterprise editions, not by tasks or data volume. List prices are not published.
  • The 2026 platform adds AI error handling, the Celigo Ora natural-language assistant (in beta), AI agents and MCP management on every edition.
  • Most failed Celigo projects are design problems: no system of record, no error owner and no sandbox. Fix those before you build.

A Celigo integration connects the systems a business runs on, such as Salesforce, NetSuite, Shopify, HubSpot or a data warehouse, so that orders, customers, invoices and inventory move between them automatically. Done well, sales sees what finance sees, orders reach the ERP without retyping, and errors are fixed before customers notice. Done badly, it creates duplicate records and a queue of failed jobs nobody owns.

This guide is for operations, finance, revenue operations and IT leaders at growing and mid-market companies who are evaluating Celigo or inheriting an account someone else built. It replaces our 2024 overview with how the platform works today, what changed in 2026, and the decisions that matter more than the connector.

Section 01 · Definition

What Is Celigo Integration?

Celigo integration is the use of Celigo's cloud integration platform to connect business applications and automate the work between them. You configure flows in Celigo's builder, integrator.io, that pull records from one system, transform them and write them to another, on a schedule or in real time, with monitoring and error handling built in.

Celigo now describes itself as an intelligent automation platform that runs application integrations, APIs, EDI, data ingestion and AI agents on one foundation. In March 2026, Celigo announced it had been named a Visionary in the 2026 Gartner® Magic Quadrant™ for iPaaS for the third consecutive year.

Application integration

Flows that keep CRM, ERP, ecommerce, billing and support systems in step, such as opportunities becoming sales orders.

API management

Build, secure and publish APIs on the same platform. Celigo says it handles REST, SOAP, GraphQL and WebSocket APIs.

B2B and EDI

B2B Manager handles trading-partner documents such as purchase orders, invoices and advance ship notices alongside your other flows.

Data ingestion and AI

Move business data into a warehouse, push it back into the apps that act on it, and run governed AI agents across those systems.

Section 02 · Architecture

How Does a Celigo Integration Work?

Every Celigo integration is built from the same few building blocks: connections, exports, lookups, imports and flows, grouped into an integration. An export reads records from a source, mappings reshape them, and an import writes them to a destination. A flow chains these steps and runs on a schedule or when an event arrives.

Celigo platform architecture diagram showing integrations, connectivity, business process automations, developer workspace, monitor and operate, marketplace, governance, security and scalable infrastructure
Celigo's platform architecture as published in 2024. The 2026 platform adds data ingestion, AI agents, MCP management and the Ora assistant on top of these layers.
Building blockWhat it doesDetail worth knowing
ConnectionStores the credentials and settings for one application or endpointPrebuilt connectors, universal HTTP, database, file (SFTP) and on-premise connections
ExportReads records from a source systemModes: All, Delta (only records changed since the last run), Once, or Limit (1–100 records)
LookupFetches extra data mid-flow, such as a customer ID from the destinationLookup caches hold reference data in memory for reuse across flows
MappingTranslates source fields into destination fieldsAuto-map suggestions, handlebars expressions, conditional mapping and Mapper 2.0 for complex JSON
ImportCreates or updates records in the destinationEach page of records is capped at 5 MB; the default page size is 20 records
Flow and branchingChains the steps and can split records into branches by rule or JavaScriptFlows run independently, so a slowdown in one system does not block the others
Hooks and scriptsCustom JavaScript at defined points in a flowUsed for logic that mapping alone cannot express, such as reshaping a page before it is saved

These details come from Celigo's own documentation on data flows and integrations. For systems inside your private network, such as an on-premise database, Celigo provides an on-premise agent that opens a secure outbound tunnel to integrator.io, so nothing has to be exposed to the internet.

Section 03 · Build Options

Celigo Integration Apps vs Templates vs Custom Flows: Which Should You Use?

Use an Integration App when Celigo offers one for your exact pair of systems and process, a template when you want a head start you can change freely, and custom flows for everything else. Integration Apps are prebuilt and fully managed by Celigo; templates are starting points that become yours to maintain once installed.

OptionWhat you getBest forTrade-off
Integration AppA licensed, full-package integration between two applications with built-in business logic and settingsCommon, high-volume processes such as Salesforce–NetSuite lead-to-cashLeast upkeep but you work within its settings
Quickstart templatePrebuilt flows, connections, exports and imports installed from the MarketplaceStandard processes you expect to adapt, such as Shopify–NetSuite order syncFast start, then you own the changes
Custom flowsFlows you design in integrator.io from connectors, mappings and hooksUnique processes, internal systems, multi-system orchestrationMost flexible, and most design effort

You can browse both in the Celigo Integration Marketplace. Inside integrator.io, the Marketplace filters by Integration apps, Templates and AI Agents. Celigo's guide to prebuilt Integration Apps explains when each one makes sense.

Section 04 · Use Cases

What Can You Connect With Celigo?

Celigo is strongest where front-office and back-office systems meet: CRM to ERP, ecommerce to ERP, trading partners to ERP, and every system to the data warehouse. These are the processes where retyping causes the most errors and where prebuilt flows already exist.

Salesforce and NetSuite: lead-to-cash

Integration App

Best for: companies that sell in Salesforce and bill, fulfil and recognise revenue in NetSuite.

The Salesforce–NetSuite Integration App syncs opportunities to NetSuite sales orders or projects, keeps accounts, customers and contacts aligned, creates a fulfillment record in Salesforce when NetSuite ships an order, and shows NetSuite invoices, payments and refunds inside Salesforce. It supports NetSuite OneWorld, multi-subsidiary and multi-currency setups.

Our Salesforce and NetSuite integration guide covers the setup in depth.

Shopify, Amazon and NetSuite: order-to-cash

Template

Best for: ecommerce and direct-to-consumer brands.

The Shopify–NetSuite template includes flows for orders to sales orders, fulfillments to item shipments, refunds to cash refunds or credit memos, and NetSuite items to Shopify products. Similar prebuilt integrations exist for Amazon and other marketplaces.

If your sales team also works in Salesforce, see our Salesforce and Shopify integration through Celigo.

EDI with retailers, distributors and 3PLs

B2B Manager

Best for: manufacturers and distributors selling through retail.

Celigo B2B Manager exchanges EDI documents with trading partners and maps them into your ERP on the same platform. Celigo lists prebuilt connections for major retailers such as Target, Walmart and Costco, and gives you access to the raw X12 or EDIFACT data for audits.

Our guide to automating order-to-cash in manufacturing with Celigo walks through a typical flow.

Data warehouse and Salesforce Data Cloud

Data Ingestion

Best for: teams that need reporting across CRM, ERP and commerce data, or that feed customer data into Salesforce Data Cloud.

Celigo's data ingestion moves records from business apps into a warehouse such as Snowflake or Google BigQuery and sends the results back to operational apps. The August 2026 release also lets the HTTP connector load data into Salesforce Data Cloud through its Ingestion API.

Section 05 · AI

What Does Celigo AI Do in 2026?

Celigo's AI works in three places: it classifies and resolves integration errors, it lets people build and troubleshoot flows in plain language through Celigo Ora, and it runs governed AI agents inside flows. All three are available on every Celigo edition, and every change Ora proposes waits for your approval.

AI error management

A machine-learning engine classifies errors and retries the ones it can fix. Celigo reports that it automatically corrects over 95% of errors each month; the rest go to dashboards and email alerts.

Celigo Ora

Ora builds and edits flows, APIs and agents from a description, maps the dependencies in your account, and traces an error to its root cause. Celigo lists it as in beta.

AI agents

Agent Builder runs an LLM step inside a flow, with your own model key or Celigo's, plus guardrails, approvals and an audit trail for each action.

MCP management

Celigo can expose approved tools to AI assistants through MCP servers, with per-user access, central sign-in and a request log for audits.

Two cautions. The error-resolution figure is Celigo's own claim, so measure it on your account in the first month. And AI agents still need the same design discipline as any flow: a defined input, a defined output, and a person who owns the exceptions. The May 2026 release notes and the current release notes track what has shipped.

Section 06 · Pricing

How Much Does Celigo Cost?

Celigo does not publish list prices. It charges a flat rate based on the number of endpoints (connected applications) and flows you use, across three editions: Standard, Professional and Enterprise. There are no per-task, per-transaction or data-volume charges and no overage fees, so busy seasons do not raise the bill.

EditionPositioned forNotable inclusions
StandardYour most critical integrationsMFA and role-based access, SSO as an add-on, standard support SLAs
ProfessionalIntegrations across departmentsAPI Builder, Lookup Cache, SSO with auditability, a sandbox, enhanced support
EnterpriseAutomation across the whole businessUnlimited endpoints, maximum performance, compliance-grade governance, fastest SLAs

Source: Celigo pricing. Celigo also offers a 30-day free trial. When you budget, count three things: the endpoints you need now and in a year, the flows per process (a two-way sync is usually several flows), and whether you need a sandbox, which starts at Professional.

Section 07 · Verdict

When Is Celigo the Right Fit?

Celigo fits best when your integrations centre on business applications such as an ERP, CRM and ecommerce stack, and you want operations teams to share the work with IT. It is a weaker fit for a two-step automation that a simpler tool handles, or for an API-led architecture across many internal systems.

Celigo is a strong fit if NetSuite, Salesforce, Shopify or Amazon sit at the heart of your process and a prebuilt app or template already exists for it. It also fits when you process high order volumes with seasonal peaks and want predictable pricing, when you need EDI with retailers alongside your other integrations, and when business users should monitor and fix errors without filing IT tickets.

Celigo is probably not the right fit if you only need a few simple triggers, such as a web form posting to a CRM, where a lighter tool like Zapier costs less. The same goes for building a reusable API layer over many internal systems, which an API-led platform such as MuleSoft is designed for, or for a company that already runs governed workflow automation on another iPaaS such as Workato.

Twopir Consulting implements Celigo, MuleSoft, Workato, Zapier and n8n, so the recommendation follows the process, not the tool we happen to sell.

Section 08 · Implementation

How Do You Implement a Celigo Integration?

Design the data ownership first, build in a sandbox, test with real failure cases, then cut over with a rollback plan. Celigo is a cloud platform, so there is nothing to install except the optional on-premise agent; the effort goes into mapping, rules and testing. A focused build of one or two core flows between two systems typically takes four to six weeks from discovery to go-live.

  1. 1

    Discovery and architecture. List every system, record and trigger. For each object, name the system of record and the conflict winner, and document the exceptions, such as a customer with no tax ID or an order with a discontinued item.

  2. 2

    Choose the build path. Use an Integration App or template where one fits, and plan custom flows and JavaScript hooks only for the gaps. Count endpoints and flows so the edition matches.

  3. 3

    Build in a sandbox. Use a separate environment and Celigo's integration lifecycle management to clone an integration, merge tested changes through a pull request, and roll back to an automatic snapshot if needed.

  4. 4

    Use delta exports and filters. Export only records changed since the last run, and filter history so the first run doesn't flood the destination.

  5. 5

    Test the failures, not just the happy path. Send a record the destination will reject, a duplicate and an oversized order, and confirm each one lands in the error queue with a clear owner.

  6. 6

    Cut over with a rollback path. Backfill historical data, switch off the legacy connector, and agree sign-off criteria before go-live.

  7. 7

    Hand over and operate. Document every flow, set alert recipients, and review the error dashboard weekly for the first month.

This is the sequence our Celigo iPaaS implementation services follow: audit, architect, build and operate.

Section 09 · Pitfalls

What Are the Most Common Celigo Integration Mistakes?

Most Celigo problems are not platform problems. They come from unclear ownership of records, errors nobody is assigned to, and changes made directly in production. Each one is cheaper to prevent than to clean up.

1. Two systems editing the same field. Without a named system of record, two-way syncs overwrite each other and create duplicates. Decide ownership per object before the first flow.
2. Nobody owns the error queue. Auto-resolution handles routine retries, but data errors such as a missing customer still need a person. Assign an owner and an alert route for every flow.
3. Editing production directly. On legacy production and sandbox licenses the two environments share resources, so a "test" change can affect live flows. Confirm your license type and use cloning and pull requests.
4. Customising an Integration App beyond its settings. Push the app past what it was designed for and you lose the benefit of a managed product. Use a custom flow alongside it for unusual logic.
5. Ignoring page size limits. Lookups that add fields to every record can push a page past 5 MB. Keep payloads lean and reshape data early in the flow.

If you have inherited a Celigo account with a long error list, an integration and CRM audit is usually the fastest way to decide what to fix, rebuild or retire.

Section 10 · Bottom Line

The Bottom Line

A Celigo integration earns its keep when it replaces retyping between your CRM, ERP and commerce systems with flows that run reliably and tell you when something goes wrong. The platform is mature, the prebuilt apps cover the common processes, and the 2026 AI features reduce the routine error work. The outcome still depends on the design decisions you make before you build.

  1. 1

    Start from an Integration App or template where one exists.

  2. 2

    Name a system of record and an error owner for every flow.

  3. 3

    Size the edition by endpoints, flows and whether you need a sandbox.

  4. 4

    Build and test in a sandbox, and test the failure cases.

  5. 5

    Measure Celigo's AI error handling on your own account before relying on it.

Ready to Start

Plan Your Celigo Integration With an Expert

On a discovery call, a Twopir integration consultant will review the systems you want to connect, the records each one should own, and whether an Integration App, a template or custom flows fit best, whether you are starting fresh or fixing an existing Celigo account.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Celigo is used to connect business applications and automate the processes between them. Common examples are syncing Salesforce opportunities to NetSuite sales orders, sending Shopify or Amazon orders to an ERP, exchanging EDI documents with retailers, and loading business data into a warehouse for reporting.

Yes. Celigo is an integration platform as a service: a cloud platform for building, running and monitoring integrations. Gartner named Celigo a Visionary in its 2026 Magic Quadrant for iPaaS. Celigo now calls its product an intelligent automation platform because it also covers APIs, EDI, data ingestion and AI agents.

An Integration App is a licensed, fully managed integration between two applications, with built-in business logic that Celigo maintains. A template is a set of prebuilt flows, connections, exports and imports that you install from the Marketplace and then change freely, which means you also maintain it.

Celigo charges a flat rate based on endpoints and flows, across Standard, Professional and Enterprise editions. It does not charge per task, per transaction or by data volume, and it has no overage fees. List prices are not published, so you get a quote, and a 30-day free trial is available.

Yes. Celigo has a Salesforce connector and prebuilt integrations between Salesforce and NetSuite, Shopify, Amazon, HubSpot, Snowflake and other apps. Its Salesforce–NetSuite Integration App covers opportunities to sales orders, customer records, fulfillments and financial history, and its HTTP connector can load data into Salesforce Data Cloud.

A focused build of one or two core flows between two systems typically takes four to six weeks from discovery to go-live. Multi-system programs, EDI onboarding or migrations from a legacy connector take longer, because most of the time goes into data ownership decisions, mapping and testing failure cases.

Celigo Ora is the natural-language assistant built into the Celigo platform, listed by Celigo as in beta. You describe what you need and Ora builds or edits flows, APIs and agents, explains errors and traces them to the root cause. Nothing it proposes takes effect until you approve it.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Celigo integrations between Salesforce, NetSuite, ecommerce and EDI partners.