Skip to content

Celigo iPaaS

Celigo integration, support and account audits.

Accentra helps Australian businesses build, support and take control of Celigo integrations. Connect ERP and commerce, investigate failing flows or audit an inherited account, with reviewable changes and documentation your team can use.

From business rule to operating flow

The detail makes the difference.

Understand the path, make failure visible and leave the business with a clear owner.

Discuss your integration

Understand what you own

Celigo account audits for Australian businesses

An audit is useful when flows keep failing, the original developer has left, or nobody can explain the dependencies in your account. We review the agreed scope before proposing production changes. An account audit and an implementation project are separate pieces of work.

What we examine

Inventory integrations, flows, connections and scripts; trace branches and record mappings; review schedules, access permissions and recent errors. Compare the configured behaviour with the business rules for orders, stock, customers and finance. Include downstream dependencies that would be affected by a change.

What you take away

An agreed account inventory, dependency map, prioritised findings and a proposed remediation plan. Separate confirmed faults from risks that need testing. Record the business impact, suggested owner and validation needed for each action, so the report can guide the next decision.

Bring the systems involved, examples of missing or incorrect records, and the concerns your team cannot resolve. We agree the access required for the review and handle credentials through an appropriate secure channel.

What a useful finding looks like

Illustrative finding: a timed-out order request has no documented check for whether the destination already accepted it. This is a risk to validate, not proof that duplicates have occurred.

Evidence and next action: inspect the mapping and destination key, reproduce an uncertain response with synthetic records, assign a recovery owner and record the acceptance check. The report should distinguish the observed configuration, the possible business impact and what still needs testing.

Use our Celigo account audit checklist to prepare the scope and assess the deliverables.

Discuss a Celigo account audit

Celigo support that follows the record through

Start with the affected record and the business impact. Trace its export, transformations, lookups and destination response. Distinguish a temporary API failure from a mapping, permissions or data-quality fault before retrying; repeating an invalid request will not repair it.

For ongoing support, agree the covered integrations, support hours, severity levels, response commitments and escalation contacts. Monitor error backlogs and recurring failures alongside flow completion. After a repair, check for duplicate transactions and reconcile the recovered records with the destination system.

Support may include mapping corrections, script maintenance, connector changes and handover documentation within the agreed scope. After-hours response is arranged explicitly; an automated alert alone is not a 24-hour support agreement.

Discuss Celigo support
Build surface

What we actually build on Celigo.

Flows, exports and imports

The core build. Scheduled and real-time flows, delta exports with checkpointing, webhook triggers, multi-branch routers, and imports with lookups and upsert logic. This is most of the work on most projects.

JavaScript hooks

preSavePage, preMap, postMap, postSubmit, postResponseMap, preSend and handleRequest. Written as reviewable source, not pasted into a text box and forgotten.

Lookup caches

Key-value stores for cross-reference resolution and repeated lookups. Agree cache freshness, key ownership and recovery behaviour before relying on cached data for a business decision.

API Builder

Custom HTTP endpoints that let external systems query or push data through your integrations synchronously, with a real response instead of a queued job.

B2B and EDI

Trading partner onboarding, EDI profiles, file definitions, X12 and EDIFACT parsing, and functional-acknowledgement handling for partners who still exchange documents this way.

AI agents, tools and MCP servers

Celigo's newer surface: agent imports for classification and extraction, guardrails for PII and moderation, reusable tools, and MCP servers exposing your integrations to AI clients.

How we work

Treated as engineering, not as clicking.

The common failure mode with iPaaS work is not a bad flow. It is an account nobody can safely change two years later, because every decision lives in a UI with no history and no owner. Four practices prevent that.

Flow config lives in Git

Every flow, export, import and script is pulled to disk and committed. You get a diff for each change, an owner, and a way back. Not a screenshot of a UI panel from six months ago.

Linted before it reaches production

celigo account lint runs static analysis across every integration, flow and script, catching broken references, missing required fields and common script errors. It runs in CI before a promotion, not after a failure.

Driven from the CLI, not only the UI

Celigo shipped a first-party CLI in April 2026. It makes bulk edits, dependency graphs, account-wide search and scripted promotions possible. Most integration work is still done entirely by hand in a browser.

Documented flow by flow

What each flow moves, on what schedule, through which branches, with which scripts, and what breaks it. Written down where the next person will find it, including when the next person is you in a year.

Inherited a Celigo account you don't fully understand?

Start with an agreed audit scope: flows walked branch by branch, dependencies mapped and the error backlog reviewed. Establish what the account contains before proposing changes.

Straight answers

Questions worth asking any Celigo partner.

Are you a certified Celigo partner?

We work with Celigo as our primary integration platform, with hands-on delivery experience right across its build surface: flows, hooks, lookup caches, API Builder, EDI, and the newer AI and MCP resources. If formal partner tier matters for your procurement process, ask us and we'll tell you exactly where we stand rather than leaving it implied.

How is Celigo licensed, and what does it cost?

Confirm the current platform edition, included capabilities and commercial terms with Celigo. Account scope, connected systems, flows and the environments you need should be clear before comparing proposals. Our implementation, audit or support scope is separate from the platform licence, so the proposal should show both responsibilities and costs explicitly.

How does Celigo compare to Workato, Boomi, Jitterbit or Patchworks?

Compare the platforms against the same workflows, connector operations, custom fields, recovery scenarios and operating responsibilities. Demonstrate the difficult requirements, check the proposed edition and obtain current scoped quotations. A platform name or a long connector list does not establish that the complete business process is covered. Include a native connector when it can meet the requirement.

Can you take over an existing Celigo account someone else built?

Yes. We start with an agreed audit scope: integrations, flows and scripts inventoried, dependencies mapped, error backlogs reviewed, and undocumented flows walked branch by branch. You get a written picture of the account and a prioritised remediation plan before production changes are proposed.

What happens when an integration breaks at 2am?

The response depends on the support agreement. We agree monitoring, support hours, escalation and recovery responsibilities explicitly. Celigo provides error investigation and retry tools, but available history and retention depend on the account and error type. Preserve evidence promptly, diagnose the failure and confirm the destination state before replaying a transaction. After-hours human response is not implied by an automated alert.

When is Celigo the wrong choice?

When you have exactly one simple integration and a native connector already does it, an iPaaS is overhead you do not need. When your requirement is high-volume, low-latency event streaming rather than business record synchronisation, purpose-built infrastructure fits better. And when nobody on your side will own the integration after go-live, no platform saves you. That is an operating model problem, not a tooling one.

Australian commerce

Four things that break integrations built offshore.

None of these are exotic. They are the default conditions of running commerce in Australia, and they are where integrations built to a US or European model quietly produce wrong numbers.

GST is in the price, not added at checkout

Agree price-display and tax mappings with your finance team or tax adviser. Test the configured treatment of discounts, shipping, refunds and rounding across commerce and ERP before accepting the reconciliation.

Multi-warehouse and click & collect

Stock that exists in one location, is reserved in another, and is collected from a third. Getting availability right means modelling location-level inventory, not a single quantity field, and deciding what the webstore is allowed to promise.

Australian carriers and 3PLs

Australia Post and eParcel, StarTrack, Shippit, StarShipIT, Aramex, and 3PL warehouse systems that each have their own idea of what a consignment looks like and when tracking becomes available.

Local payments and marketplaces

Afterpay, Zip and PayTo settle differently from card payments, which changes how the finance reconciliation flow has to work. Amazon AU, eBay AU and The Iconic each impose their own fulfilment and messaging rules.

Celigo is not a plugin you install. It is an integration platform with a data model, an execution order, a failure model and an operational surface, and integrations built without understanding those go wrong in ways that are expensive and slow to find.

This page is longer and more technical than most agency pages, on purpose. If you are choosing an integration partner, the useful signal is not how many logos they can show you. It is whether they can describe how the platform actually behaves. So here is ours.

How the platform composes

Five primitives, one build order.

Everything in Celigo is assembled from connections, exports, imports, flows and integrations, with JavaScript hooks running inside flow execution. The higher-level resources (tools, APIs, AI agents and MCP servers) all package those same primitives behind a stable contract.

Build order
  1. IntegrationContainer. Groups flows, settings and connections.
  2. FlowThe unit of execution. Chains sources to destinations.Script hooks attach here
  3. Export + ImportSource step, then destination step.
  4. ConnectionCredentials and config for one external system.
Five primitives compose every integration on the platform. You read this top down, but you build it bottom up: a flow cannot exist before the export and import it chains, and neither can exist before the connection they authenticate through. Getting that order wrong is the most common reason a first Celigo build stalls.
What a real flow looks like

The steps are hiding inside the branches.

This is the single most useful structural fact about Celigo, and the one that most often makes an inherited account look simpler than it is. If someone hands you an integration audit that counts one step per flow, they read the top level and stopped.

Top-level read reports1 STEPActual8 STEPS / 3 BRANCHES
ExportScheduled
Router, fans out to 3 branches
  • Branch 0 / new orders
    1. 1.lookup: customer
    2. 2.map
    3. 3.import: sales order
  • Branch 1 / amendments
    1. 1.lookup: existing SO
    2. 2.script: preMap
    3. 3.import: update
  • Branch 2 / unmatched
    1. 1.script: classify
    2. 2.import: exception queue
The thing that catches everyone out. Celigo nests almost every step inside router branches, at routers[].branches[].pageProcessors[], and leaves the top level pageProcessors list empty. Read only the top level, as most documentation tools and most people do, and a flow like this one reports one step. The real flow has eight, across three branches, each with its own mappings, scripts and failure modes. Every audit we run walks the branches explicitly, because that is where the integration actually lives.
Where the code runs

Hook points, in execution order.

  1. preSavePageAfter the export reads a page

    Filter or reshape records before they enter the flow.

  2. preMapBefore field mapping

    Enrich or look up values the mapper will need.

  3. postMapAfter field mapping

    Correct the mapped payload before it is submitted.

  4. postSubmitAfter the destination responds

    React to the write: chain, log or compensate.

  5. postResponseMapAfter response mapping

    Reshape what the flow carries forward.

Where your JavaScript runs, in the order it runs. Choosing the wrong hook point produces integrations that pass testing and fail in production. Enriching data in postMap when the mapper needed it in preMap is the classic version. There is also preSend for request level changes and handleRequest for API and tool endpoints.
The failure path

What happens when a record fails.

  1. Record submittedSuccess → CompleteIf the submission fails ↓
  2. Open error

    Review the error details and retry data.

    Retry if eligible; otherwise assign an owner.
  3. Retry

    Automatic retries for eligible intermittent errors, when enabled.

    • Replay succeedsResolved
    • Still failing or needs a correctionOwner investigates

      Correct the cause, then retry the record.

      ↑ Return to retry after the fix
What happens to a record that fails. Most integrations are judged on this path rather than the happy one. A flow that moves 10,000 orders and silently drops four is worse than one that stops and tells you. Celigo provides error details and retry data to investigate and replay failed records. Automatic retries apply to eligible intermittent errors when enabled; failures that need a correction can go directly to an owner.
Related:

Let’s connect

Ready for a more connected business?

Tell us where you are and where you want to go. We'll help you work out the next step.

Book a free consultation