Two integration platforms. One has a catalogue of prebuilt apps; the other builds what you need from an API’s own documentation. This page compares what each actually requires of your team, across forty-six jobs.
Each line opens the row it came from, with the scenario and the documentation behind it. Read them sceptically: that is what the rest of this page is for.
Why the promises tell you nothing, in one analogy:
Two cars, both advertised as self-driving. One parks itself in your driveway. The other drives Philadelphia to Denver while you sleep. Same words on the brochure. Not the same product.
Same two words on both brochures. Two completely different products.
Integration platforms are harder: there is no test drive. Every vendor writes the same words: deep, autonomous, AI-powered, enterprise-grade. Words are free. You find out what you bought in month nine, when a customer reports a failed sync and you need to know exactly what happened. Or in year two, when the engineer who built it is gone.
So this is not a page of claims. It is a page of jobs. A real thing that has to happen. What happens on APIANT, step by step. What the same job requires on Boomi, in its own documentation's words.
Apply the same scepticism to us. Read the architecture, not the adjectives. And take three questions with you into every vendor conversation you have after this one:
After the AI has done the work, is there a representation a non-developer can open, read, and judge? Building something and being able to look at it afterwards are two different capabilities.
Jump to Capability 01, where it bites hardest → TEST 02Never accept a depth claim. Test it against the specific API you need: the private endpoint no catalog lists, the forty custom fields, the rate limit, the pagination quirk.
Jump to Capability 03, the uncatalogued endpoint → TEST 03Every AI gets something wrong eventually. The question is what, in the architecture, is positioned to catch a wrong result before your customer sees it.
Jump to Capability 18, the answer to it →These three tests run on every one of the forty-six capabilities on this page. By the third section you will be asking them yourself.
Integration work is where your roadmap goes to wait. Deals stall on a connector that does not exist yet, engineers get pulled off product to fix a sync, and a single "it didn't work for one customer last Tuesday" can absorb a week of senior time. Whichever platform you choose, you will live inside its architecture for years. This page shows you what each one actually requires of your team, job by job.
A note on method. Every vendor in this category claims depth, autonomy, and reliability, and you have no way to adjudicate competing claims. So this page does something else: it takes concrete jobs and shows what each platform's architecture requires to get them done. APIANT's side is a walkthrough of shipping capabilities. Boomi's side is derived from Boomi's own documentation, help centre and pricing page, quoted where a quote beats a paraphrase. Where their design handles a job well, we say so.
How to read this page. Every row is one capability. Bright text is what you get on APIANT; muted text after the dot is what the same job costs on Boomi. Skim the forty-six takeaways and open any row that matters. Inside each: the problem that forced the capability to exist, a concrete scenario, how it goes on APIANT, and what the same outcome requires on Boomi. Skim the bold lines first. The argument is the pile, not any single row.
Both models open and read, and Boomi's where-used is queryable through the UI and the API; the difference is perimeter, where their review agent "cannot review processes that include a cycle or loop".
Everything on this page traces back to one design decision made years before AI could build integrations: what is an integration made of? On APIANT the answer is structured data, all the way down. That choice looked like an implementation detail for a decade. It is now the whole ballgame.
Both let an AI build the integration. The difference is what the AI hands you afterwards.
Quarter-end's 80MB file clears by 4am on the same path as a normal night. the format edge becomes a script component, and the proof runs into test-mode caps
Open the scenarioIntegrations died on large payloads, and on formats the platform had not anticipated.
Every record, file, and API response flows through a single engine with a small memory footprint. The platform does not care what shape your data arrives in or how much of it there is.
The nightly claims and inventory export lands at 1am as one file. At quarter end it is 80MB, and it has to be parsed, reconciled and posted before clinics open at 7am. Nobody is awake to babysit it.
Corrections post by 4am. Quarter end is not an incident category.
Their agent can author the scripting component an unsupported format needs, then deploy it. Proving a large payload is where it stops: test mode caps at 100 documents or 10 MB, test capture stops recording at 50 MB, and their skill pack states their API cannot inject document payloads into an execution.
Structurally invalid work is refused at build time, instead of surfacing later in production logs. nothing, on the structural half
Open the scenarioA generated integration that is syntactically fine and semantically wrong reaches production, and nobody knows until customer data is wrong.
After a hail week, 6,200 claims queue up. The integration pushing approved amounts into payments compiled and deployed cleanly. Farmers on the phone tell the claims supervisor which field it wrote.
The AI's intent passes through a constrained schema; the compiler refuses invalid structures at the door. It then tests the build on a real saved claim and reads what reached the payment field. Dee can open that run too.
Their AI closes this loop. The platform validates every push, and Companion reads the error, applies a fix and retries without a person.
The asset your company accumulates is a library of inspectable building blocks that any successor can open, not a portfolio of codebases that each had exactly one fluent reader, who has since changed jobs.
A connector that does not exist yet is a working session here; Boomi's own FAQ prices the SDK route at "it may take 2-3 months", the faster Gradle DSL route builds "from an OpenAPI specification" a partner API under NDA does not publish, and the route that needs no spec lands on the generic REST connector, where "Object - Not supported for this connector."
Connector catalogs are where integration platforms compete in public, and it is the wrong contest. The integration a deal depends on is reliably the one no catalog lists. The real questions are time-to-new-connector, and how deep the connector goes once it exists.
A niche partner API becomes a working connector in one session, and the renewal survives. Elsewhere it arrives as a Node project, times forty clients. the catalog connector stays a Java project
Open the scenarioThe integration the deal depended on was never in anyone's catalog, and the catalog vendor had no incentive to add it.
Membership holds and multi-site transfers live in a partner API behind an NDA, in no catalog anywhere. The client's renewal is conditioned on this integration existing within the month.
The connector exists in a working session. The renewal conversation changes subject.
Their AI reaches a process on the generic REST connector, with no object type and so no import wizard. A catalog entry with browse and field discovery is a Java SDK build by a developer who has signed their SDK agreement.
Five integrations clear their vendor portal paperwork in one afternoon, with the credentials landing straight in the vault instead of a spreadsheet. the OAuth step goes back to the GUI
Open the scenarioOnboarding stalled for days on OAuth paperwork before a single record moved.
Five integrations launch this quarter, each blocked on registering an app on a vendor's developer portal: forms, callback URLs, credentials. It is nobody's job, so it becomes everybody's bottleneck.
Five portals, one afternoon, zero credentials in a spreadsheet.
Their own AI documentation hands this step back. OAuth authorization is named as work that requires the GUI, so five portal registrations and five consent screens are five afternoons a person spends.
An onboarding call maps forty-one custom fields and a dropdown their admin invented, because the connector reads the customer's live tenant. discovery is a screen, and custom objects sit outside it
Open the scenarioField mappings built against documentation break on contact with a customer who renamed things and added forty custom fields.
A 60-store retailer's CRM carries forty-one custom fields and a member tier dropdown whose values exist in no documentation. The mapping screen has to show their CRM, not the CRM in the manual.
The onboarding call maps forty-one custom fields without a single "we'll get back to you."
The Import Wizard does read the customer's own container, and it is a GUI screen their Companion FAQ routes discovery-based configuration back to. Custom objects sit outside browse-and-map either way.
Every API gets a vetted way of announcing changes, so records stop going missing or arriving twice. the change-detection memory is a file a person clears
Open the scenarioEvery vendor's API announces change differently, and picking the wrong mechanism means missed or duplicated records.
Nine carrier systems, 1,400 load tenders a night. One feed replayed a status it had already sent and two trucks went to the same dock, so the night dispatcher now reconciles the tender log by hand.
The AI picks the right pattern per API and builds the trigger, or Dana's team picks it: polling for new records, polling for new-or-updated, manual webhooks, self-registering webhooks, service webhooks with event filtering, long-lived protocol listeners. Six vetted patterns either way, and which one a feed is using is visible on the trigger itself.
Their agent can author all three: a listener, a schedule, and the Find Changes step for a feed with no updated-at field. Two extra hands: the step is gated to Professional and above, and its memory is a file under the runtime's work/cdc directory whose documented reset is a person deleting it on the box.
Ask the AI for an inference or a price calculation and it arrives as a step your team can open and check. one operation component per action and object pair
Open the scenarioCreate-read-update-delete alone cannot express what modern APIs do.
The photo-damage model and the fraud score in claims intake sit inside a code block whose author left in March. At 3,000 claims a month, adjusters quote repair numbers the company cannot account for.
Ask the AI for the fraud score and it builds the call as an invoke action, the primitive for operations that compute, transform, or generate. Or Renata's team builds it. Add, delete, find, get, list, update, and invoke: seven primitives, and either way the step opens as data rather than as a contractor's code block.
Their agent creates the components, and the shape of the call sets how many. Boomi's rule is a separate operation component for each action and object pair, so a create and an update are two. The compute-style call has no object behind it, lands on a technology connector, and arrives without a profile.
Ask the AI to set the vendor's limit, or type it once yourself, and every account sharing that API queues against one 185-calls-per-10-seconds budget. the outbound arithmetic stays with your engineer
Open the scenarioA vendor's rate limit is the real constraint on a multi-location sync, and hitting it corrupts a run.
310 branches sync to one supplier API that allows 120 calls per 10 seconds. A rate-limit rejection killed the nightly refill batch partway through, and branch queues opened at 8am short of data.
Tell the AI the vendor's published limit and it sets the throttle, at connector, action, or connection level, or Sunil types it once himself. Either way the platform enforces it across every automation and every account touching that API, with queueing and backoff, and either of them can read the current setting back. One deployment runs 232 locations against a single 185-calls-per-10-seconds budget.
Boomi does not document a budget several automations draw against one vendor's published quota; the rate numbers they publish govern traffic arriving at a Boomi endpoint. On that basis the outbound arithmetic is manual work.
Time-to-new-connector is measured in working sessions, not sprints, and every connector you add, however obscure the API, joins the same inspectable library instead of adding one more codebase to the pile someone must maintain.
Awkward rules stay typed steps on a canvas either team can read; on Boomi, parallel processing reads "No | Yes ($) | Yes ($) | Yes | Yes" across the editions, and approvals are Flow, one of their "Standalone product plans".
Field-to-field mapping is the demo. The business is nested rules, parallel work, digests, approvals, waits, and the awkward requirement that makes your operation yours. The question for any platform: does that logic fit inside the model, where it stays visible and testable, or does it spill into code and patterns your team hand-builds?
214 stores get overnight prices in minutes, and the 6am report fires once. the summary after the fan-in is separate work
Open the scenarioProcessing two hundred locations in series took hours. In parallel, nothing knew when all of them had finished.
Launch N child runs in parallel, and the platform itself knows when the last one completes, so the "everything is done, now reconcile" step is a primitive, not a science project.
A 214-store chain pushes overnight price updates, and serially it runs past opening. The hard part was never the fan-out. It is knowing that all 214 are done before the reconciliation report goes out.
Prices land in minutes, the report is on the director's desk at 6am, and nobody wrote coordination logic.
Their agent can author the Flow Control step, and the fan-in genuinely waits. Two things change the design: the steps after it never run in the controlling process, so the single summary is separate work holding state the fibers can reach, and on a runtime cloud the unit ceiling is published as ten.
Contact changes flow both ways on day one, without the overnight loop that rewrites one record 4,000 times. the loop guard is yours to design
Open the scenarioTwo systems updating each other trigger each other, forever.
22 clinics keep patient details identical in practice management and marketing CRM, editable from either side. One record was updated four thousand times overnight and both APIs rate-limited them.
The sync runs both directions on day one, and "infinite loop" is not in the runbook.
Boomi does not document a named loop-prevention or echo-suppression feature in Integration. On that basis echo suppression is design work over their change-detection step rather than a platform behaviour.
One fix instead of nine, with nothing left behind in a forgotten copy to drift out of step. one edit, nine parents repackaged
Open the scenarioThe same twelve-step sequence appeared in nine automations and had to be fixed nine times.
A twelve-step onboarding sequence sits inside nine automations. The April rule change meant the identical edit nine times, and copy seven had drifted: a welder paid at the wrong rate for five weeks.
Ask the AI to extract the twelve steps into one subroutine and repoint all nine automations at it, or do the extraction by hand. Either way the fix lands once, all nine inherit it, and the subroutine tests on its own.
The edit is made once, and their agent can push it. Production is the extra work: the deploy unit is a package holding the process and every component it closes over, per environment, and their own troubleshooting list names the trap. Nine callers is nine parents repackaged and redeployed.
Customers get one 5pm summary instead of 400 pings, and nothing is lost when two runs land at once. the digest is a small system you own
Open the scenarioCustomers wanted one daily digest, not four hundred notifications.
One Tuesday produced roughly 400 emails, and two of the largest accounts asked to be removed from notifications. The operations manager assembles the 5pm digest by hand, and she is away next week.
The operations manager asks for one 5pm summary and the AI builds the collector: events drop into a named bucket all day, drained on the schedule. She can build the same bucket herself. It is a dedicated primitive, safe when two runs land at once.
Boomi does not document an aggregation primitive that collects items into a named bucket across executions and drains it on a schedule. On that basis a 5pm digest is a cache, a queue and a scheduled process your team owns.
A three-day follow-up needs one system, not a separate scheduler for somebody to own. a multi-day wait is a schedule you keep
Open the scenario"Follow up in three days" required an external scheduler and a second system to maintain.
If the adjuster has not followed up within three days, the claim ages into a regulatory bucket with a penalty. The scheduler holding that wait missed 34 follow-ups, and the audit is in November.
Ask the AI to hold the file for three days and it adds the snooze step; the supervisor can add that step herself. The run suspends for three days, or until next quarter, and resumes with its state intact. One system, one place to look.
Boomi does not document a snooze or resume-in-N-days step inside an Integration process. A Wait step exists in Boomi Flow, a separate product plan. On that basis a three-day pause is a schedule and a state table you keep.
Refunds over $500 wait for a manager's approval while everything else keeps moving. the approval queue is a second product
Open the scenarioSome records must not sync until a person says yes, and the wait cannot block the platform.
After £48,000 of refunds in one night, anything over £500 needs a venue manager to say yes. Those requests now sit in a shared inbox chased by text, while every small refund queues behind them.
Ask the AI for a gate above $500 and it adds the moderation step; the head of support can add it herself. The run pauses on a queue, a person approves or denies from a link, and the run resumes. Everything smaller keeps flowing.
Boomi has an approval gate, in Boomi Flow, a separate product plan with no Companion skill pack behind it, so nothing on their agent surface reaches it. The held record waits outside the run that produced it.
Change one step of a fifty-step process without re-testing the other forty-nine. a piece is testable if it was built and deployed to be
Open the scenarioOne monolithic automation became unmaintainable and untestable.
Order-to-cash is one automation that has grown to 64 steps. Any change to the credit-check rules means retesting all 64, so the applications manager tests none of it and edits at 5am on Sundays.
The AI splits the 64 steps into small automations that call each other with parameters, or the applications manager does the split himself. Either way each piece tests alone, so a credit-check change retests one piece instead of all 64.
Their agent breaks the process up and can deploy the pieces. What makes a piece separately exercisable is a decision taken earlier: their rerun page requires a subprocess to have its own Start step connector and its own deployment, and a piece that takes its input from the parent is exercised by running the parent.
A customer's 300-row mapping sheet becomes the configuration directly, with unresolved rows flagged, instead of a week of error-prone typing. the sheet is keyed in by hand
Open the scenarioA customer's mapping requirements arrived as a 300-row spreadsheet, and hand-entering it was a week of error-prone work.
The field map arrived as a 300-row spreadsheet, and hand-keying it eats most of week one of four. Every keying slip surfaces later as a subscriber billed twice, and renewal season opens 1 October.
Hand the AI the 300-row file and it becomes the mapping directly: the AI reads it, applies it, and flags the rows that do not resolve. The consultant can key a row herself, or correct one the AI flagged, on the same screen.
Boomi does not document importing a mapping spreadsheet into a Map component. Their published suggestion engines read a community corpus rather than this customer's sheet. On that basis the 300 rows are keyed in.
Turnover stops costing you the same debugging twice: a quirk solved once stays solved after its author leaves. the memory is a file, not a searchable store
Open the scenarioThe same API quirk was rediscovered every time, by whoever drew the short straw.
The engineer who holds the loan-status lookup table in his head has given notice. 11 live integrations rest on knowledge that was never written down, and his replacement starts in three weeks.
The AI writes each solved quirk into a searchable library and checks that library before it builds anything, so the timestamp-zone trap is solved once, ever. Your engineers read and write the same library, which is what keeps the knowledge after its author leaves.
Their agent can write the conventions file, and Boomi copies it into every new project. It is context read at the start of a session rather than a searchable store of solved cases, and none of their five skill packs publishes a save or search tool over one, so the timezone quirk is retrievable if somebody thought to write it in words a successor would use.
Logic complexity does not convert into code ownership. The awkward rules that make your business yours stay inside a model that your people can read, your tests can cover, and your AI can safely change.
Boomi customers do test, in test mode and through Companion's retest loop; what is not documented is a branch or path coverage figure, and Boomi Assure's own page says it "does not provide a way for partners or customers to conduct their own process integration, regression, or automated testing".
"It worked when I tried it" tests one path out of eleven. The other ten are where customers live. This act is the answer to the third standing test: when the AI, or a person, gets something wrong, what in the architecture catches it before production data does?
Prove a path that fires once a year works today, not in nine months. their API cannot inject the document
Open the scenarioThe branch nobody could trigger on demand was the branch that broke.
The donation pipeline has a branch that fires only in the last week of December. It is March and the integration was just modified. Prove the December branch still works without waiting nine months.
The branch that used to be tested by December is tested by lunch.
Asking their agent to force the December branch reaches process properties, not the record. Their own skill pack states the ceiling, so producing a December-shaped document is a person's job, and test-mode evidence is discarded when you exit.
The AI tests every branch before it ships. Not the branches somebody thought to write payloads for. Every branch.
Ship a one-line fix across 300 accounts knowing exactly which customers it touches. the dependency answer is per account
Open the scenarioA one-line connector fix silently changed behaviour for three hundred accounts.
A date-format bug turns up in a shared connector operation, with 300 customer accounts live. The fix is one line. Which automations call it, on whose accounts, and which rely on the buggy behaviour?
The one-line fix ships with a printed list of everyone it touches, so the dependents are known before the edit rather than after it.
Which components a change touches is a strength, and their agent walks the reference graph in both directions in a single call. The scope is one account. Which customers means that call per account, with no account-enumeration tool in any of their five packs, against a Platform API published at ten requests per second.
You know a change is fully tested because the platform counts untested paths, not because someone felt confident. the number that says when to stop is not published
Open the scenario"It worked when I tried it" tested one path out of eleven.
The claim-intake automation has eleven branches. The claims supervisor signed off on a mapping change because the hail path ran clean in test. Harvest starts in five weeks and ten were never walked.
She asks whether the change is fully tested, and the AI answers from the branch test points the platform tracks, then walks the ones still unexercised. She can read the same list herself. Coverage is measured, not assumed.
Boomi does not document a branch or path coverage figure for an integration, and no coverage tool appears in their five skill packs. On that basis knowing which branches a test exercised is manual work rather than a platform behaviour.
Bugs get retested against the actual record that broke, emoji in the surname included. the record you retest with is kept thirty days
Open the scenarioSynthetic test data does not contain the thing that breaks integrations.
A patient pre-authorisation posted wrong on 3 July, escalated after the third rejected claim. Reproducing it needs that exact run: an emoji in the surname field. That run is six weeks old.
She names the 3 July run; the AI re-executes it from the step that broke, its captured data intact, or she does it herself. The emoji in the surname and the mangled mobile number are in the test, because the real record is the test.
Replaying the stored document is real, and it is a person on the Process Reporting page. No Companion script reruns a document, and the record carries a thirty-day default clock a September escalation falls outside.
Answer a month-old complaint by re-firing the exact message that failed. a replay is scoped to one execution ID
Open the scenarioTesting a webhook-triggered flow meant asking a customer to go and click something in their system.
An undocumented rate-confirmation payload began dropping accessorial charges worth 18,000 euros a week. The fix is written. Validating it means asking a shipper to re-tender loads they already moved.
She asks for last month's tender; the AI finds the stored payload and re-fires it at the fixed automation, or she replays it herself and watches it process. No shipper is asked to re-send a load they already moved.
The replay is a person, one execution ID at a time, in Process Reporting. A process on a fifteen-minute schedule that failed through four hours left roughly seventeen of them, each opened and rerun on its own.
Shared logic proves itself in one run instead of dragging nine workflows through a test cycle. passing data in and testing alone pull against each other
Open the scenarioProving one shared component meant running nine automations.
One change is needed to the address-and-residency normalisation sequence before enrolment opens Monday at 8am. Proving it means dragging all nine parent automations through a test cycle on a Sunday.
She asks the AI to prove the shared sequence; it runs the subroutine alone on controlled inputs and reports what came back. She can run it the same way herself. One run, not nine parents dragged through a cycle.
Their test tool starts a process and cannot supply the block's inputs, so proving a shared piece alone is a person's run of the parents that call it, or a build decision taken earlier.
An agent works production with full read, and the actions that reach a fleet return a plan a human approves. the production boundary is a role you configure
Open the scenarioThe fastest way to an outage is a confident agent with production credentials.
An AI agent is to work directly on production integrations posting 2,600 ACH transactions a night. One mis-sequenced deploy at 11pm is a reportable incident by the time branches open.
The AI reads production freely: run history, step data, assembly logs, the account changelog. The actions that reach a fleet are preview-first by design. deploy_to_accounts returns the deployment plan on its first call and writes when a human passes an explicit confirmation, not before, and the group kill switch and its restore behave the same way. Marcus can make those same calls himself, and the changelog shows what happened either way.
Their in-product agents do gate writes: platform agents produce output a customer approves before it persists. The surface that edits integrations sits outside that gate, and its restraint is a role you configure plus a guideline, rather than a preview the destructive call returns before it writes.
Test coverage is a property of the platform, not of your team's imagination for payloads. Across months of daily production builds on APIANT, no hallucinated mapping, structure, or logic has been observed reaching production. That is what the compiler and the branch walk are for.
One release does reach Boomi's whole install base, conceded; what it carries is capped at "up to 100 shareable packages" and excludes Process Route components, certificates, custom libraries and tracked fields.
Building the integration once is the demo. Running it for three hundred customers, each configured differently, each on their own credentials, all needing the same fix on the same day, is the business. This act is where per-customer platforms and per-fleet platforms part ways.
Ask the AI to ship the fix and it deploys to 232 linked accounts on your confirmation of the plan it returns. the fleet model is rep-enabled and human-operated
Open the scenarioEvery customer wants the same integration configured differently, and cloning it per customer creates hundreds of divergent copies.
One codebase carries the logic. Settings (which fields sync, which features are on, time zones, branding) vary per customer. The same automation serves a single-location studio and a 232-location franchise.
A fitness franchise runs the same booking-system-to-CRM integration at 232 locations, each on its own credentials. A fix has to reach all 232 before the evening class rush.
Fix at 2pm, fleet-wide by 2:15, evening classes uneventful.
Integration packs plus extensions are exactly this shape, and none of their five skill packs creates, publishes or releases one, so the fleet mechanism is a person in the UI. Enabling it is a conversation with a representative.
One incoming request lands in the right location's account, on that location's own credentials, with hundreds of accounts behind the curtain. the router is excluded from the pack
Open the scenarioThree hundred locations cannot each hold their own credentials and configuration.
Kestrel Pharmacy Group's 178 branches share one refill endpoint, with the store code buried in the payload. The first batch lands at 6:40am, and every message has to reach the branch that can fill it.
A parent account governs 178 children: the webhook hits the master, which routes by store code to the right child, processing on that branch's own credentials. Priya asks the AI where a refill landed and admin_auto_search_exec_history answers across all 178, or she opens the run herself.
The router that sends a payload to the right branch on that branch's credentials is a Process Route component, and Boomi lists it among the components a managed account does not receive in an integration pack. It ships on its own path, by hand.
One CRM login covers every location while each site keeps its own booking login. a credential is a value per environment
Open the scenarioRe-authenticating per location does not scale past about twenty.
Southern Reef Dental's 96 practices each hold their own practice-management login, but the one group CRM token expires every 90 days. Re-authorising clinic by clinic has cost three weekends.
One CRM credential, flagged shared, serves all 96 practices while each keeps its own practice login. Dan asks the AI whether the group token still authenticates: asm_test_api_connection. He can check by hand. Sharing is a toggle on the hierarchy, alongside shared settings and automations.
Their agent can set extension values, so a rotation is reachable. It is reachable per environment: ninety-six practices is ninety-six calls, and Boomi publishes the places where those values have to be typed again, with a documented repair routine for values that do not take after a redeploy.
A week of hand-updating becomes one confirmed action, staged if you prefer, with every prior version kept for a redeploy. the fleet push is real, and it is a person's action
Open the scenarioShipping a fix to two hundred customers by hand takes a week and misses some.
A payment provider renamed a field overnight and refunds have been failing since 05:00. The head of support has the fix in hand and 186 venue environments to get it into before Friday's 10am on-sale.
Marta tells the AI to ship it: deploy_publish_folder, then deploy_to_accounts across the 186 venues, each returning its plan and writing on her confirmation, per-account results in front of her. She can run both herself. Staging is naming a subset on one call, and every prior version is kept, so a reversal is a redeploy rather than a rebuild.
One release reaches the whole install base, by UI or by their API, and any page saying otherwise is wrong. None of their five skill packs creates or releases an integration pack, so the action is a person on the Integration Packs page.
A new account is created, linked, and inheriting shared logins, settings and automations in one operation, with no onboarding checklist to work through. On Boomi's embedded path, twelve properties is twelve child-account forms, and the runtime attachment is serial either way. onboarding is several admin builds, done in order
Open the scenarioOnboarding a customer was a manual checklist.
Twelve newly acquired hotels each need their management system talking to the group's revenue and CRM stack before the 1 October rebrand. The onboarding checklist runs 31 steps per property.
Ines asks the AI to onboard the next hotel: admin_create_account creates it, links it into the hierarchy, inheriting shared connections, settings and automations, and deploy_to_accounts covers the rest. She can do the same in the console. The 31-step checklist becomes one operation.
Installing a pack is self-serve in the customer's account. Getting there is admin builds and a per-customer form: child account email, account ID and an API token that cannot be read back. Boomi's own guidance for volume is serial.
You ask the AI who is exposed and get the list in minutes. the exposure list is assembled account by account
Open the scenarioAn API deprecation notice arrived, and nobody knew who was exposed.
A carrier emails that v1 of its claims API retires in 90 days. By Friday the claims systems manager must name which of 74 connected systems touch that endpoint. That list does not exist.
The carrier emails that v1 retires in 90 days. Rosa asks the AI who is exposed: admin_auto_search_by_app names every automation on that app across the broker accounts, asm_find_referencers the assemblies depending on the connector, permission-scoped. She can search herself. Minutes, and it is the migration worklist.
Inside one account their agent answers this well, both directions in one call. Nineteen hundred broker accounts is that call per account, through a Platform API published at ten requests per second with a bulk read ceiling of a hundred instance IDs, and Boomi assigns the impact analysis to the publisher.
Customer three hundred costs what customer three cost. Growth in breadth, more customers, more locations, does not multiply your operational surface, and does not show up as a per-deployment line item on the platform bill.
Support answers come from the run itself; Boomi caps searchable identifiers at "a maximum of 20 tracked fields", and those "cannot be used with integration packs", which is the shape a build shipped to 90 sites has.
Nobody buys an integration platform for month one. The purchase is really years two through five: the customer reports, the API drift, the 2am incidents, the person who left. Every platform demos the build. This act is about everything after the demo, which is where the money is, and where architectures stop being interchangeable.
Answer a three-week-old customer complaint before standup: find the run, fix it, prove it, ship to all 90 sites. the field that finds her is excluded from the pack
Open the scenario"It did not work for this one customer last Tuesday" was a multi-day archaeology project, and often unanswerable.
6:51am: one location of a 90-site franchise writes that a member signed up on June 30 and never appeared in their CRM. It is July 21, and hundreds of thousands of executions have run since.
All of it directed conversationally, by one person, before the 9:30 standup. The reply to the location: what happened, why, fixed, and here are the other three members we caught and restored.
Their agent queries execution records, and a three-week-old run is inside the thirty-day window. Finding her by email address is the extra work: a business identifier is a tracked field, capped at twenty per account, and unavailable on the deployment shape this comparison is about.
"It didn't work for one customer last Tuesday" stops being a week of archaeology. It becomes a conversation.
A real deployment went from 140 alerts a day to 3. narrowing a subscription is a rebuild by hand
Open the scenarioAlerting was either silent or so noisy that everyone stopped reading it, which is the same thing.
A platform team's alert channel gets 140 integration alerts a day and two are real. They muted it months ago. Last Thursday one of the two sat unread for nine hours while orders silently queued.
Three alerts a day, each one real, each one read. The channel gets unmuted.
On their ELT product an agent does edit a flow's notification block. On the integration platform none of their 351 published API paths is an alerting endpoint and no skill pack tool reaches one, so narrowing a subscription is a person rebuilding it.
Ask once and 180 automations across a parent and 60 children are snapshotted and disabled, then restored exactly as they were. the list of what to turn back on stays yours
Open the scenarioWhen an upstream vendor breaks, the choice was between flooding a broken API and losing track of what to turn back on.
An upstream CRM is down and 180 automations across 60 child accounts are hammering a dead API. When it recovers you must restore the previous state exactly, not reawaken the three disabled on purpose.
Total human attention: minutes at the start, minutes at the end. No flood, no amnesia.
Three levers exist, at three altitudes, and each is a UI action no skill pack wraps: stop a schedule, pause a listener, stop a runtime. There is no parent handle to pull across accounts, and the restart list is your own bookkeeping.
Transient blips retry themselves while broken credentials stop instead of hammering a customer's API, set once for the whole tenant. retry is a per-process schedule, not a per-error rule
Open the scenarioTransient failures were treated as fatal, and genuine auth failures were retried forever.
At 03:10 transient 502s marked 340 overnight freight tenders fatal, while an expired token retried until that carrier's account locked. Trucks unassigned past 07:00 come off the contract rate.
Ask the AI to retry the 502s and stop the expired token, or set the lists yourself: retryable error classes are tenant-wide, and auth failures on named domains get carve-outs. Shutoff is a policy on record, not a surprise you discover.
Retry is a schedule attached to a process with a maximum attempt count, not a rule about which errors deserve another attempt. Stopping it is infrastructure work: deleting files on the runtime, or Support on a hosted one.
After an outage, hundreds of failed records get reprocessed from one screen instead of by hand. bulk retry stops at one execution ID
Open the scenarioAfter an upstream outage, hundreds of records needed reprocessing, and there was no safe way to do it in bulk.
A Saturday outage left 2,600 prescription-refill requests failed on the way to the dispensing system. The operations manager has Sunday and two staff before patients walk in Monday.
Ask, and the AI lists every failed run, shows what each was carrying, and retries them in bulk once the cause is fixed. Priya can work the same surface herself, at 2,600 or at any scale.
Bulk retry within one run is real and not per record. Across runs it is a person opening each execution ID in Process Reporting, with manual selection paged, and nothing in their five skill packs reruns a document.
Catch a silent backlog before the customer calls: work that arrived but never ran has its own screen. the backlog you can see is the one that reached a queue
Open the scenarioSilent backlogs: everything looks healthy, and nothing is moving.
At 08:10 the dispatcher finds 430 missed-pickup webhooks arrived overnight and never moved past the door. Every status board was green, and the trucks left the yard without the reroutes.
Ask what arrived and never ran: the AI returns the received-but-unprocessed queue, 430 events, and Marlene sees the same view unprompted. Stuck work shows up before a customer notices the gap.
For an event that reached a listener and never started a process, Boomi does not document a backlog view outside the licensed queue and dead-letter mechanism. On that basis finding it is manual work.
Type a customer's email or order number and land on the runs that touched it across every account. An hour of log reading becomes a minute. search by value is per account, and off for packs
Open the scenarioCorrelating a failure across accounts meant reading logs by hand.
Claim AV-2291884 was acknowledged to the policyholder but never reached the loss adjuster, and the regulator's clock runs out Monday. Nobody knows which of 74 broker accounts it passed through.
Ask with the claim reference and the AI searches every account at once for that value, returning the runs that touched it. Eoin can run the same search. Correlation across 74 accounts is a query, not a shift.
Boomi does not document a single query that searches document data across many accounts. Search runs inside one account, over fields nominated in advance. On that basis reaching a few hundred accounts is manual work.
A support question that used to need a database ticket and two days gets answered in the meeting. step-level detail is an enabled download and a poll
Open the scenarioDiagnosis stalled waiting for someone with database access.
The overnight sync left 260 students without timetable records, and a queue is forming at the registry counter on day two of term. The registrar has a theory she cannot test without database access.
Is it the part-time cohort at one campus? The AI answers in seconds with a guardrailed read-only query, and Alison can run the same query herself. Tested in the meeting, not in a database ticket.
Run history is queryable and their agent reaches it. Step-level detail is the longer path: an artifact download a Cloud owner has to enable on the Attachment Quotas tab, requiring the Runtime Management privilege, returning a 202 so it is a poll rather than an answer, and scoped to one account.
Support stops being the silent tax on your margin. The question every vendor dreads, "what happened for this one customer three weeks ago," has a fixed cost of minutes, answered by one person, with the evidence still there.
EmbedKit renders in your own DOM, so white-label is real and it carries no partner gate; the embedded Spaces path "must be registered and onboarded as a Partner" and is "available only on the US platform".
Your customer never sees the engine. They see a setup screen, a connect button, a status page, and increasingly, a tool their own AI can call. Whether those surfaces feel like your product or like someone else's is a brand decision you are making when you pick the platform.
Customers set up the integration inside your product, on your domain, with no second settings screen to build. the embed is your front-end work, behind a partner gate
Open the scenarioCustomers were being sent to a third-party integration UI that broke the product experience and advertised the vendor's supplier.
The settings that drive the integration are the interface the customer configures it with. No translation layer, no second UI to build and keep in sync. Your customers never see the platform. They think it is you.
A practice manager clicks "Connect accounting" in Lumen's settings, authorizes, maps two fields, done, without seeing another company's name. She is trusting Lumen, not buying an integration platform.
The customer's takeaway: "Lumen's integrations are great." Which is the entire point.
EmbedKit is a plugin your front-end team installs into your own page, which is real and better than an iframe. Nothing on their agent surface builds or configures it, and the Spaces path starts with Boomi onboarding your company.
Your customers' AI assistants can drive multi-system work through your product, with an approval gate before anything destructive and a record afterwards. Your domain, every tier. the route from your processes to tools carries a preview label
Open the scenarioCustomers now want their own AI agents to reach these systems, and hand-building an interface per client does not scale.
An operations director tells her AI assistant: "Move every Thursday booking at Riverside to Friday and notify the affected members." Your customers judge your product on whether their AI can drive it.
The Thursday bookings move, the members get notified, and the audit trail shows exactly what her agent did.
Their agent can author the connector that turns your own processes into callable tools, and Boomi labels that route Technology Preview, plain HTTP, server-sent events. Changing one tool means redeploying every process that uses it. Their managed route reaches their catalog rather than your processes.
The AI assembles the setup screen, so there is no front-end project: validated input, live choices from the customer's systems, embed code returned. form depth past their components is your front-end team
Open the scenarioConfiguration UIs were bespoke front-end projects, every time.
Palletworks promised its three largest brokers a screen that pulls their live carrier list and validates SCAC codes before anything saves. Its two front-end engineers are nine weeks into a backlog.
The AI assembles the setup screen from an element catalog and saved patterns: input validated before it saves, choices pulled live from the customer's systems, embed code returned. Adjust it in the designer yourself; the same form either way.
For a form element in the embedded configuration surface whose choices are populated live from the end customer's connected system, Boomi does not document this. On that basis it is front-end work or a second product.
The assistant you ship resolves requests instead of deflecting them: real lookups, real writes, an approval gate before anything destructive, full logs. a tool call returns run status, not the records
Open the scenarioA chatbot that cannot act is a deflection tool, not an integration.
Aldergate's chat agent handled 6,400 conversations and 2,100 ended as after-hours callbacks. A tenant asks at 11pm to move Thursday's plumbing visit, and all the agent can offer is an on-call number.
The AI builds the agent you ship: explicit goals, scoped tools, each tool an automation you can open and read. Or you wire the goals yourself. It acts through the same governed engine as everything else: real writes, approval gates, full logging.
An agent can start your integration from a conversation, which is real. What comes back is whether the run succeeded, so answering with the customer's own records means building and maintaining an API around the process, and Boomi's own page recommends that route.
Every surface a customer's IT team inspects, screens, addresses, callbacks, carries your name on every plan. the embed's API host and the OAuth callback stay theirs
Open the scenarioAn integration layer that shows a supplier's name tells your customer who really built it.
Fenmark is 48 hours from signing a carrier worth 1.4 million a year. Question 41 asks for every hostname claim data touches, and its webhook receiver answers on a domain carrying someone else's name.
Ask the AI which hostnames the integration answers on and it lists them off the connectors and the embed code. The dev and production servers are yours, so the configuration screens, the webhook receivers and the authorization callbacks all answer on your domain from the first paid tier. If you also embed one of our hosted widget scripts, that file is served from ours, and that is the one line on the list you did not write.
Your page is yours, and EmbedKit theming is deep. Boomi does not document an override for the embed's API host or the OAuth callback host. On that basis aligning those two hostnames is a conversation rather than configuration.
The integration experience compounds into your brand instead of your supplier's. Every setup flow, every status page, every AI tool call is a moment your product looks finished, in your customer's language, on your domain.
Their AI diagnoses, fixes and redeploys, which we concede; Boomi publishes that agent as "not covered by Boomi support agreements or SLAs", and a Boomi developer post prescribes the production role as "Read-only, production: watch logs and executions, nothing else".
Everything on this page is exposed to AI, but "AI-powered" is the emptiest phrase in the category. The question with teeth: which phases of the integration lifecycle does the AI have real tooling for? Building is one phase. There are seven more.
One person and the AI cover an integration's whole life, launch through incidents. Elsewhere the AI diagnoses, then a developer does the fixing. the agents that deploy and retest carry no support commitment
Open the scenarioAn AI with raw API access improvises. An AI with encoded procedures repeats what works.
Day two. A customer reports a discrepancy, an API starts rate-limiting, a fix needs to reach the fleet. The question for the AI is no longer "can you build it" but "how much of this can you handle?"
One person and the AI cover the lifecycle. Day two looks like day one.
Their agent reaches build, debug, deploy, diff and rollback, which is broad. Alerting and fleet release have no tool in any of their five packs, so day two is a person in the UI, on a surface published without a support commitment.
Give an AI forty similar-looking tools and it picks the wrong one. Here it sees only the handful this job needs. the unit of scope is the product pack
Open the scenarioDepth and focus are in tension: an AI drowning in tool definitions gets worse, not better.
Friday, 16:40. The integration lead has the AI retune a load-tender mapping inside 61 automations, a change 40 dispatchers need Monday. Every irrelevant tool is another way to reach the wrong one.
Sanne asks for the retune and the session loads that procedure with the tools it needs, the connector and mapping edits, a test run against real data, the alert rules, not all 138. The rest stay one request away when the job widens. Or she makes the same edits in the editor herself, on the same automation either way.
Boomi does not document tool-set narrowing scoped to a task inside a running session. The unit is the product pack, chosen before the session starts. On that basis focus is manual work rather than a platform behaviour.
The AI files the platform defect it hits, so it gets fixed instead of papered over by an undocumented workaround. a bug goes to a curated intake channel
Open the scenarioAgents silently working around platform bugs means the bugs never get fixed.
The platform layer behaves differently than documented, the AI routes around it, and that detour is permanent, undocumented, and a 2am problem next hail season. The supervisor has inherited three.
The AI files the defect itself: a structured report to engineering, autonomously, instead of routing around it and shipping. Or Marla files one from the same session. Either way the detour becomes a record with the defect attached, not an undocumented workaround somebody inherits. The tools get better because the agent using them is also their reviewer.
A defect their agent trips over goes to an intake channel Boomi curates, filed by a person, and not into the code. The tool it would be filed against is the same one published without a support commitment.
The AI is not a build accelerator bolted to the front of the lifecycle. It is a colleague with a runbook for all of it, which is why one person can run what used to take a team.
Every row on this page reduced to the same fork. On APIANT the job was a walkthrough: ask for it, watch it get built at whatever depth the API allows, prove it, ship it, and change it later without a rebuild. On Boomi the same job was reachable when someone had already built the piece you needed, at the depth they chose to build it, and priced by how many records moved through it. Not because their product is careless. It is the most widely used automation tool in the world and it is genuinely fast to a first result. But its integrations are assembled from operations that people hand-authored one at a time, so what you can automate is bounded by what someone else already decided to expose, and what it costs grows with the volume you push through it. On APIANT the connector is generated from the API's own documentation and stored as data, which is why depth is not a roadmap request, a missing operation is a working session, and the thing you end up owning is an asset your team can read rather than a subscription to someone else's catalogue.
Then you write code, in the one place code belongs: a scripting escape hatch that slots in as a single node of the structured document. Code is an optional leaf inside a data document, never the foundation. The loop, the branches, the mappings, the tests around that leaf all remain visible, machine-editable, and compiler-checked; the custom logic is contained to the one spot that genuinely needed it.
Compare the shape of the same answer elsewhere: when the model runs out, the escape hatch is more code on a foundation that is already code. The exception and the rule are indistinguishable. Here, the exception stays the exception, and a decade of production has kept it rare.
Own the outcome, and be precise about what owning the artifact costs. A code integration is cheap on day one and priced like a liability thereafter: it is reviewed by whoever has time, it carries a dependency tree that ages, every API drift re-opens it, and its real documentation is the memory of whoever wrote it. Multiply by every integration you will ever ship, then by the years you will run them, then subtract the engineers who will have moved on. That is the asset you would own.
What you own on APIANT is the thing you actually wanted: integrations that run, on your domain, inspectable by your team, provable before they ship, and operable by AI for as long as you run them. The buildings your company works in are owned this way too: you own the use of something built and maintained by people whose whole business is that it never falls down.
The API with no catalog entry, the forty custom fields, the sync that loops, the customer report from three weeks ago. One working session, on your systems, and you watch it built, tested on every branch, and running. Judge the architecture with your own scenario, which is what this page has been asking you to do all along.
Book a working session See the AI operate the platformScenario companies on this page are composite illustrations drawn from real deployment shapes. Company names are fictional and are not customer references. Where a figure comes from a live APIANT deployment it is identified as such and the customer is not named. Every statement about Boomi on this page derives from Boomi's public documentation, help centre, developer platform docs and pricing page as reviewed in August 2026. Direct quotes are reproduced verbatim for comparison purposes. Boomi is a trademark of Boomi, Inc.; all product names belong to their owners. Platform capabilities evolve; verify anything decision-critical against the current versions of the linked pages.
