Kentico - Ziflow Integration and Automation

Common Integration Use Cases Between Kentico and Ziflow

• Campaign asset review from Kentico content workflows to Ziflow
  When marketing teams create landing pages, banners, or campaign pages in Kentico, the related creative assets can be automatically sent to Ziflow for review and approval. This reduces manual handoffs between content and creative teams, shortens approval cycles, and ensures only approved assets are published to the website or campaign microsite. Data flow: Kentico to Ziflow.
• Approved creative assets returned from Ziflow to Kentico for publishing
  Once a design, video, or copy asset is approved in Ziflow, the final version can be pushed back into Kentico and linked to the correct page, campaign, or content item. This helps web teams avoid using outdated files and supports faster content deployment across digital channels. Data flow: Ziflow to Kentico.
• Automated approval status updates for campaign content
  Kentico can receive approval status updates from Ziflow so content managers know whether a page component, hero image, or promotional asset is still under review, approved, or rejected. This improves visibility for launch readiness and helps teams prevent publishing delays caused by incomplete approvals. Data flow: Ziflow to Kentico.
• Localized content review for regional website variants
  For global organizations, Kentico can send translated page assets or region-specific creative to Ziflow for localized review by regional marketing, legal, or brand teams. Approved localized versions can then be returned to Kentico for deployment on country-specific sites. This supports consistent brand governance while allowing market-level flexibility. Data flow: Bi-directional.
• Compliance and legal sign-off for regulated content
  In regulated industries such as healthcare, finance, or pharmaceuticals, Kentico campaign content can be routed to Ziflow for mandatory legal and compliance review before publication. Ziflow approval records can then be stored or referenced in Kentico as proof of sign-off, helping teams maintain auditability and reduce compliance risk. Data flow: Kentico to Ziflow, then Ziflow to Kentico.
• Content change requests triggered by proofing feedback
  If reviewers in Ziflow reject an asset or request revisions, the feedback can be sent back to Kentico as a task or content update request for the web or content team. This creates a closed-loop workflow that keeps content production aligned with review outcomes and reduces back-and-forth across email and chat. Data flow: Ziflow to Kentico.
• Campaign launch coordination across web and creative teams
  Kentico can act as the source of truth for campaign pages and launch dates, while Ziflow manages the creative approval process for supporting assets. Integration allows both teams to track readiness in one workflow, making it easier to coordinate launch timing, identify blockers, and ensure all assets are approved before go-live. Data flow: Bi-directional.