OpenText Extended ECM - Business Workspaces - Contentful Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and Contentful

1. Publish approved workspace content from OpenText Extended ECM to Contentful for omnichannel delivery

Business teams manage source documents, product briefs, policy content, or campaign assets inside OpenText Extended ECM Business Workspaces, where governance, version control, and approvals are enforced. Once content is approved, it is pushed to Contentful as structured entries for websites, portals, mobile apps, or partner channels.

• Direction: OpenText Extended ECM - Business Workspaces ? Contentful
• Business value: Ensures only approved, compliant content is published across digital channels
• Typical use case: Legal, compliance, or product teams approve content in a workspace before marketing publishes it in Contentful

2. Store final published content references back in OpenText for audit and governance

After content is published in Contentful, the published entry ID, URL, version, and approval metadata are written back to the related OpenText workspace. This creates a governed record of what was published, when, and by whom.

• Direction: Contentful ? OpenText Extended ECM - Business Workspaces
• Business value: Improves auditability and reduces risk of publishing outdated or unapproved content
• Typical use case: Regulated industries that need a traceable link between source content and live digital experiences

3. Create a workspace in OpenText when a new Contentful content model or campaign is initiated

When digital teams create a new content model, campaign, or microsite in Contentful, an OpenText workspace is automatically created to manage supporting documents such as briefs, legal reviews, brand guidelines, and stakeholder approvals. This gives business users a controlled collaboration space tied to the digital initiative.

• Direction: Contentful ? OpenText Extended ECM - Business Workspaces
• Business value: Aligns content operations with governance and cross-functional review processes
• Typical use case: Launching a new product page or campaign that requires structured approvals and supporting documentation

4. Synchronize approved metadata from OpenText into Contentful content fields

OpenText often holds authoritative business metadata such as product names, region, regulatory classification, customer segment, or document status. That metadata can be synchronized into Contentful fields so digital teams can reuse trusted business data in structured content entries.

• Direction: OpenText Extended ECM - Business Workspaces ? Contentful
• Business value: Reduces manual rekeying and keeps digital content aligned with enterprise records
• Typical use case: Publishing product pages that must reflect approved product attributes from the business system of record

5. Link Contentful content assets to supporting documents stored in OpenText workspaces

Contentful entries can include references to governed documents stored in OpenText, such as compliance certificates, technical datasheets, policy PDFs, or legal disclaimers. Contentful remains the delivery layer, while OpenText remains the controlled repository for source documents.

• Direction: OpenText Extended ECM - Business Workspaces ? Contentful
• Business value: Keeps high-governance documents managed centrally while making them available in digital experiences
• Typical use case: Product detail pages that need downloadable regulatory documents or approved technical attachments

6. Trigger review workflows in OpenText when Contentful content is updated

When editors update a Contentful entry that affects regulated or business-critical content, the integration can create or update a review task in OpenText. Stakeholders can then review the change in a governed workspace before it is released to production channels.

• Direction: Contentful ? OpenText Extended ECM - Business Workspaces
• Business value: Adds enterprise approval control to fast-moving digital content operations
• Typical use case: Changes to pricing, claims, product descriptions, or policy statements that require formal sign-off

7. Consolidate campaign source materials in OpenText and distribute approved snippets to Contentful

Marketing, legal, and product teams collaborate in OpenText on campaign source materials such as messaging frameworks, claims, images, and supporting evidence. Approved snippets, summaries, or structured content blocks are then published into Contentful for reuse across web pages, apps, and localized experiences.

• Direction: Bi-directional
• Business value: Improves content reuse, speeds campaign rollout, and reduces inconsistencies across channels
• Typical use case: Global marketing teams managing a single source of truth for campaign content and localized channel delivery

8. Use OpenText as the governed archive for expired or superseded Contentful content

When content in Contentful is retired, superseded, or no longer approved for public use, the final version and related metadata can be archived in OpenText. This preserves the business record, supports retention policies, and helps teams retrieve historical content when needed.

• Direction: Contentful ? OpenText Extended ECM - Business Workspaces
• Business value: Supports retention, compliance, and historical traceability without cluttering active digital content models
• Typical use case: Archiving old campaign pages, product descriptions, or policy content after a launch or regulatory change