Home | Connectors | OpenText Core Case | OpenText Core Case - Brandfolder Integration and Automation

OpenText Core Case - Brandfolder Integration and Automation

Integrate OpenText Core Case Case Management and Brandfolder Digital Asset Management (DAM) apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Core Case and Brandfolder

OpenText Core Case and Brandfolder complement each other well when organizations need to manage case-driven work that depends on approved brand assets, controlled content, and cross-functional collaboration. OpenText Core Case provides structured case management, task tracking, and auditability, while Brandfolder serves as the central source for approved digital assets and brand content. Together, they help teams move faster while maintaining consistency and governance.

1. Approved Brand Asset Retrieval During Customer or Partner Cases

When support, account management, or partner services teams handle a case that requires branded collateral, OpenText Core Case can surface the correct assets from Brandfolder directly within the case workspace. This reduces time spent searching for files and ensures teams use only approved, current materials.

  • Direction: Brandfolder to OpenText Core Case
  • Business value: Faster case resolution and fewer brand compliance errors
  • Example: A customer support agent handling a reseller request can attach the latest product one-pager or logo package from Brandfolder to the case response

2. Case-Based Approval of Marketing and Sales Assets

Marketing teams can use OpenText Core Case to manage review and approval workflows for assets stored in Brandfolder. When a new campaign asset is uploaded, a case can be created for legal, product, and brand review, with tasks and approvals tracked centrally before the asset is published.

  • Direction: Brandfolder to OpenText Core Case, then OpenText Core Case to Brandfolder
  • Business value: Stronger governance and faster approval cycles
  • Example: A new product launch banner is submitted in Brandfolder, routed through a case for compliance review, and then marked approved for distribution

3. Brand Asset Requests from Internal Teams

Employees in sales, regional marketing, or field operations often need localized or campaign-specific assets. A request submitted in OpenText Core Case can trigger a workflow to locate, assign, or generate the correct asset in Brandfolder, with status updates returned to the case until fulfillment is complete.

  • Direction: OpenText Core Case to Brandfolder
  • Business value: Centralized request handling and reduced email-based coordination
  • Example: A regional sales team requests a translated brochure, and the case routes to the brand team to provide the approved version from Brandfolder

4. Compliance Review of Regulated Content

Organizations in regulated industries can use OpenText Core Case to manage compliance reviews for assets stored in Brandfolder before those assets are released externally. The case can capture reviewer comments, required edits, and final approval status, creating a clear audit trail for governance teams.

  • Direction: Bi-directional
  • Business value: Better compliance control and defensible audit history
  • Example: A pharmaceutical marketing asset is reviewed in a case for required disclaimers before being approved in Brandfolder for field use

5. Customer Escalation Cases Requiring Branded Response Materials

When a customer issue escalates, service teams may need to send formal communications, troubleshooting guides, or executive response templates. OpenText Core Case can pull the latest approved materials from Brandfolder so that responses remain consistent with corporate branding and messaging standards.

  • Direction: Brandfolder to OpenText Core Case
  • Business value: Consistent customer communications and reduced rework
  • Example: A high-priority outage case includes an approved customer notification template and status update graphic from Brandfolder

6. Product Launch Coordination Across Teams

Product launch activities often involve multiple stakeholders, including product, marketing, legal, and regional teams. OpenText Core Case can coordinate launch readiness tasks, while Brandfolder stores the final approved launch assets. The integration ensures that only launch-ready files are linked to the case and distributed to the right teams.

  • Direction: Bi-directional
  • Business value: Better launch coordination and fewer version control issues
  • Example: A launch readiness case tracks approvals for packaging images, sales decks, and social media graphics, then publishes the final set in Brandfolder

7. Asset Exception Handling and Content Correction

If a team identifies an outdated, incorrect, or noncompliant asset in Brandfolder, OpenText Core Case can be used to open an exception case, assign ownership, and track remediation. Once corrected, the updated asset can be revalidated and republished in Brandfolder.

  • Direction: Brandfolder to OpenText Core Case
  • Business value: Faster issue resolution and stronger content governance
  • Example: A sales enablement team flags an obsolete pricing sheet, and the case routes to the content owner for replacement and approval

These integrations help organizations connect case management with controlled asset distribution, improving operational efficiency, reducing manual follow-up, and ensuring that teams always work from approved content.

How to integrate and automate OpenText Core Case with Brandfolder using OneTeg?