Omnisend · Arazzo Workflow

Omnisend Refresh Product Catalog Entry

Version 1.0.0

Read a product by id, then replace it with an updated representation.

1 workflow 1 source API 1 provider
View Spec View on GitHub Email MarketingMarketing AutomationE-CommerceSMS MarketingCustomer EngagementSegmentationCampaignsFormsPopupsWeb PushAutomation WorkflowsAnalyticsMCPAgent ReadyTransactional MessagingArazzoWorkflows

Provider

omnisend

Workflows

refresh-product
Read a product and then replace it with updated catalog values.
Confirms a product exists by reading it, then fully replaces it with the supplied representation.
2 steps inputs: apiKey, currency, price, productId, title outputs: productId
1
getProduct
{$sourceDescriptions.omnisendApi.url}#/paths/~1products~1{productId}/get
Read the current product by id to confirm it exists before replacing it.
2
replaceProduct
{$sourceDescriptions.omnisendApi.url}#/paths/~1products~1{productId}/put
Replace the product in full with the updated representation.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Omnisend Refresh Product Catalog Entry
  summary: Read a product by id, then replace it with an updated representation.
  description: >-
    Keeps a catalog entry in sync with the store of record. The workflow reads
    the current product by id to confirm it exists, then performs a full
    replace (PUT) of that product with the updated title, price, and currency.
    Every step spells out its request inline, including the X-API-KEY header, so
    the flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
sourceDescriptions:
- name: omnisendApi
  url: ../openapi/_original/_superseded/omnisend-openapi-scaffold-v5.yml
  type: openapi
workflows:
- workflowId: refresh-product
  summary: Read a product and then replace it with updated catalog values.
  description: >-
    Confirms a product exists by reading it, then fully replaces it with the
    supplied representation.
  inputs:
    type: object
    required:
    - apiKey
    - productId
    - title
    properties:
      apiKey:
        type: string
        description: The Omnisend API key sent in the X-API-KEY header.
      productId:
        type: string
        description: The id of the product to read and replace.
      title:
        type: string
        description: The updated product title.
      price:
        type: number
        description: The updated product price.
      currency:
        type: string
        description: The ISO currency code for the price.
  steps:
  - stepId: getProduct
    description: >-
      Read the current product by id to confirm it exists before replacing it.
    operationPath: '{$sourceDescriptions.omnisendApi.url}#/paths/~1products~1{productId}/get'
    parameters:
    - name: X-API-KEY
      in: header
      value: $inputs.apiKey
    - name: productId
      in: path
      value: $inputs.productId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      currentProductId: $response.body#/productID
  - stepId: replaceProduct
    description: >-
      Replace the product in full with the updated representation.
    operationPath: '{$sourceDescriptions.omnisendApi.url}#/paths/~1products~1{productId}/put'
    parameters:
    - name: X-API-KEY
      in: header
      value: $inputs.apiKey
    - name: productId
      in: path
      value: $steps.getProduct.outputs.currentProductId
    requestBody:
      contentType: application/json
      payload:
        productID: $inputs.productId
        title: $inputs.title
        price: $inputs.price
        currency: $inputs.currency
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      productId: $response.body#/productID
  outputs:
    productId: $steps.replaceProduct.outputs.productId
x-provenance:
  reviewed: '2026-08-13'
  status: stale
  note: >-
    Authored against the pre-2026-03-15 Omnisend contract (base https://api.omnisend.com/v5,
    X-API-KEY header) using a documentation-derived scaffold spec, which the 2026-08-13 enrichment
    pass superseded with 15 OpenAPI documents harvested from Omnisend's own docs host. The current
    contract uses base https://api.omnisend.com/api, a required Omnisend-Version: 2026-03-15 header
    and Authorization: Omnisend-API-Key {key}. This workflow needs regenerating against
    openapi/omnisend-*-openapi.yml before it will execute.

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/omnisend-replace-product-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.