inriver - Ziflow Integration and Automation

Common Integration Use Cases Between inriver and Ziflow

• Product launch content review workflow
  When inriver product managers and marketers finalize new product data, the integration sends associated copy, images, and campaign assets to Ziflow for structured review and approval. This helps ensure product descriptions, feature claims, and visuals are approved before publishing to e-commerce sites, catalogs, and partner portals. Data flow: inriver to Ziflow.
• Localized product content approval
  inriver often manages multilingual product information for global markets. Approved source content can be routed to Ziflow for regional review by local marketing, legal, or compliance teams before release. This reduces translation errors, ensures market-specific messaging is correct, and speeds up localization cycles. Data flow: inriver to Ziflow.
• Digital asset proofing for product enrichment
  Product images, lifestyle visuals, spec sheets, and packaging artwork stored or referenced in inriver can be sent to Ziflow for creative proofing. Teams can annotate changes directly on proofs, approve final versions, and then update the approved assets back into the product record. This improves asset quality and keeps product content aligned with brand standards. Data flow: bi-directional.
• Compliance and regulatory approval for product claims
  For regulated industries such as consumer goods, electronics, or healthcare, product claims and mandatory disclosures managed in inriver can be reviewed in Ziflow by legal, regulatory, and quality teams. Once approved, the status can be returned to inriver to prevent unapproved content from being published. Data flow: inriver to Ziflow, then Ziflow to inriver.
• Packaging artwork and label approval
  inriver can provide the latest product attributes, dimensions, ingredients, warnings, and barcodes to Ziflow for packaging artwork review. Packaging teams use Ziflow to manage comments and approvals on labels, cartons, and inserts, then publish the approved artwork status back to inriver for downstream channel distribution. Data flow: inriver to Ziflow, then Ziflow to inriver.
• Campaign asset synchronization for product marketing
  Marketing teams can trigger Ziflow review workflows from inriver when a product is ready for campaign execution. This is useful for banners, landing page copy, email creative, and social assets tied to specific SKUs or product families. Approved creative can be linked back to the product record to maintain a single source of truth. Data flow: inriver to Ziflow, with approval status returned to inriver.
• Exception-based reapproval after product data changes
  If critical product information changes in inriver such as dimensions, pricing statements, ingredients, or compliance text, the integration can automatically send affected assets back to Ziflow for reproofing. This prevents outdated creative from being reused and ensures only current, approved content is published. Data flow: inriver to Ziflow.

These integrations help teams connect product data governance in inriver with creative review and approval in Ziflow, reducing manual handoffs, shortening launch timelines, and improving content accuracy across channels.