Name: using-marketplace-templates
Author: celigo

Find, install, and reuse pre-built integration blueprints from the Celigo Marketplace -- Templates (unlocked, fully editable, no ongoing updates) and Integration Apps (vendor-maintained, upgrade-protected, receive updates). Covers whole-template install versus copying a single element, how connectio

<! TIER:1 Using Marketplace Templates The Celigo Marketplace is a catalog of pre built integration blueprints packaged flows, exports, imports, connections, and scripts you can browse, install, or reuse instead of building from scratch. Each listing is a Template or an Integration App (IA) ( docType Template or Connector ). A template installs either an integration or an MCP server (its type ), and the AI agent listings are integration templates tagged aiagent whose flows carry an AI agent step. Most decisions come down to Templates vs Integration Apps. Templates vs Integration Apps Templates are open, customizable blueprints. Every flow, export, import, and script ships into your account as your own editable resource rename, restructure, or rewrite anything. The trade off: templates receive no ongoing updates . A template is a starting point, not a maintained product; if the source application's API changes, you carry the fix. Integration Apps (IAs) are vendor maintained, structure locked products. Their flows' steps, the connection each step uses, and the code the app ships are upgrade protected so Celigo (or a partner) can ship updates without breaking your customizations. The trade off: you change behavior through the app's settings and edit only what it leaves open, such as import mappings, and can't rewrite the core in exchange you inherit bug fixes and new features over time. See [Changing an Installed Integration App]( changing an installed integration app). An IA also sits outside cloning and ILM: to run one in another environment, install it there from the Marketplace (one license covers every environment) see [managing integrations Plain Integrations vs Integration Apps](../managing integrations/SKILL.md plain integrations vs integration apps). Choosing wrong has opposite failure modes: pick a template when you needed an IA and you own the integration forever with no upstream fixes; pick an IA when you needed a template and you hit the locked component ceiling the moment you must customize beyond what it exposes. When unsure, list both and compare. MCP server templates ( type: mcpserver ) install an MCP server, not an integration, through their own route (step 5). Whole Install vs Borrowing One Piece Two distinct intents: Whole template install creates a brand new integration containing fresh copies of every resource in the blueprint. Intent: "set up the whole integration." This runs in the Celigo Marketplace UI installer on the listing's preview page. Borrowing one piece brings a flow, export, import, or script into an integration you already have. Intent: "borrow one piece." No API call, CLI command or MCP tool copies one element out of a template. Read the template preview (every resource it would create, in write shape with placeholder ids) and create what you need yourself in dependency order scripts, then exports and imports, then the flow with integrationId set replacing each placeholder connection id with one of your connections. Or install the whole template with your connections mapped and keep only what you need. Recognize intent from wording: "install the X template" / "set up X from a template" whole install; "copy the Y flow from the X template" / "I just want the customer export" borrow one piece. What Gets Copied vs Mapped When an install lands resources in your account, they fall into two camps: Copied flows, exports, imports, scripts, lookup caches, and response mappings become fresh resources you own. There is no link back to the blueprint: editing them doesn't touch the source, and editing the source wouldn't touch them. Mapped connections are never copied, and nothing maps them for you. The blueprint's connection ids are placeholders. Before an API install, pick or create the account connection for every connection the preview lists, then send a connectionMap with every template connection id as a key; a partial map is refused. A ZIP install creates new connections without credentials for any you leave out, and in the UI installer you should choose your existing connection instead of creating another. Quick Reference Templates vs Integration Apps Dimension Templates Integration Apps (IAs) After install Fully unlocked every resource is yours to edit Structure locked steps, their connections, and the app's endpoints and hooks are upgrade protected Ongoing updates None a starting point you maintain Vendor maintained receives bug fixes and new features Customization Rename, restructure, rewrite anything Change behavior through the app's settings; edit import mappings, lookups, input filters and response mappings If the source API changes You fix it yourself The vendor ships the update Best for A fast start you'll own and adapt A supported product you don't need to rewrite Install path Marketplace UI installer (preview page) Marketplace UI installer (multi step wizard) Preview celigo templates preview <id every resource the install creates None an IA's id answers 404 on the preview; read its listing and documentation Borrowing one piece Recreate it from the template preview Installed as a whole product Start From a Blueprint vs Build From Scratch Situation Do this A listing matches your source + destination and you want a fast start you'll own Install a Template You want a supported, auto updated product and don't need to rewrite core logic Install an Integration App You only need one flow or step from an otherwise unfit blueprint Recreate that piece from the template preview, with your own connections No listing matches, or requirements are highly custom Build from scratch Related Skills [getting started Build Order](../getting started/SKILL.md build order) where installing from a blueprint fits versus building bottom up [managing integrations](../managing integrations/SKILL.md) a whole template install lands as a new integration you then organize and promote [configuring connections Quick Reference](../configuring connections/SKILL.md quick reference) connections are mapped, not copied; verify or create the ones an install needs [building flows How to Build a Flow](../building flows/SKILL.md how to build a flow) edit or extend a flow after it lands in your account [configuring exports Quick Reference](../configuring exports/SKILL.md quick reference) exports an install brings in, or that you recreate from a preview [configuring imports Quick Reference](../configuring imports/SKILL.md quick reference) imports an install brings in, or that you recreate from a preview [writing scripts Quick Reference](../writing scripts/SKILL.md quick reference) hook scripts that come with installed or recreated flows and steps <! TIER:2 How to Use a Marketplace Template 1. Check what already exists Before installing anything, search the account so you don't duplicate an integration or connection you already have. 2. Browse the marketplace List catalog entries and note each one's docType (Template or Integration App) and, for a template, its type . UI (primary): the Marketplace UI is the primary place to browse and install open the listing's preview page there. Over the Celigo Platform MCP server, list marketplace lists the catalog (Templates only unless you pass includeConnectors or docType ); its rows carry docType but not type . 3. Decide: Template, Integration App, or build from scratch Use the [Quick Reference]( templates vs integration apps) tables. Key questions: Do you need ongoing vendor updates ( Integration App ) or full control ( Template )? Do you need the whole integration ( install ) or one piece ( recreate it from the preview )? Does anything even match ( otherwise build from scratch )? 4. Preview before you install Inspect the blueprint's contents and the connections it expects before committing. Only templates have a preview. An Integration App's id answers 404 Template not found. , which doesn't mean the listing is gone; for an app, read its listing and documentation instead. Read the readme. The template author's readme is on the preview's Integration object and usually lists prerequisites, required settings and post install steps. A whole install keeps it on the new integration; when you recreate a piece, carry over what applies. type decides the install route (step 5): integration or mcpserver . stackRequired: true means a hook or wrapper connection in the template runs on a stack. The Marketplace installer asks for one; the API install takes it as stackId beside the connectionMap ( celigo templates install <id sends the body you pipe as is) and fails with 400 stack not found without it ([managing stacks](../managing stacks/SKILL.md)). Over MCP, list marketplace with the template's id returns the whole preview, type and stackRequired included. 5. Install a whole template or Integration App Whole template and IA installs run in the Celigo Marketplace UI installer on the listing's preview page. The installer walks the multi step wizard: mapping or creating connections, accepting the license, selecting a plan, and configuration. Programmatic whole install works only for some templates. The one shot install API ( POST /v1/integrations/template/{id} with a connectionMap body) doesn't run a template's own install steps, so read the preview's Integration object first: if its installSteps include a step with type: template zip most published templates have one the install is refused with 422 Install step is invalid: invalid templateZip and creates nothing. Install those from the UI installer. Over MCP, install template is the same one shot install, with the same connectionMap . An MCP server template installs through its own route. A template whose type is mcpserver takes no body and no connection map: celigo mcp servers install template <id . A prompt only template creates the MCP server, disabled; a tool bearing one creates an integration in install mode, where its connections are mapped, and that integration's last step creates the disabled server ([building mcp servers](../building mcp servers/SKILL.md)). The integration route refuses an MCP server template (400 invalid template ), the MCP server route answers 404 for an integration template, and no MCP tool installs an MCP server template. From a ZIP. An integration downloaded with celigo integrations download <id installs into another account or environment with celigo templates install zip <file ; preview it first with celigo templates preview zip <file to list the connections to map. The ZIP carries no credentials, so a connection you don't map arrives without them. An install that timed out may have worked. Each install request that reaches the platform creates another integration, and a gateway timeout (504) or a dropped connection doesn't mean it failed. Before any retry including when the user asks you to "run it again" look for what the first request would have created: an integration carrying the template's templateId (usually under the template's name), created around the time of the request, with its flows (the audit log shows the creates). If it's there, the install went through: report it, and don't install again. If you can't tell either way a lookup fails, or the list is ambiguous ask the user before installing again. 6. Or borrow one piece Nothing copies a single element out of a template, so recreate it from the preview. Read what you need ( celigo templates preview <id model Flow , then the exports, imports and scripts the flow references) and create each piece yourself in dependency order: scripts, then exports and imports, then the flow.