Wrike - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between Wrike and OpenText Decision Service

1. Automated project intake and routing based on request type

When a new work request is submitted in Wrike through a request form, OpenText Decision Service can evaluate the request against business rules such as region, budget, service line, priority, or client tier. Based on the decision outcome, the request is automatically routed to the correct Wrike project, team, or workflow stage.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Faster intake, fewer manual triage steps, and consistent assignment of work to the right team

2. Approval path selection for creative and marketing deliverables

Wrike proofing and approval workflows can be enhanced with decision rules that determine which approval chain is required for a deliverable. OpenText Decision Service can apply rules based on content type, brand, geography, legal sensitivity, or campaign spend, then return the required approval path to Wrike.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Reduces approval delays and ensures the correct stakeholders review the right assets

3. Priority scoring and SLA assignment for professional services work

For client delivery teams using Wrike, OpenText Decision Service can calculate priority and service level targets using factors such as contract value, due date, client segment, and resource availability. Wrike can then update task priority, due dates, and escalation rules automatically.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Improves workload balancing, protects high-value accounts, and supports SLA compliance

4. Budget threshold controls for project and campaign work

Wrike can send project cost, time, or estimate data to OpenText Decision Service to determine whether work can proceed, requires manager approval, or must be escalated to finance. The decision engine can apply thresholds by department, campaign type, or client contract terms and return the appropriate action to Wrike.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Prevents overspend, enforces financial controls, and improves governance across projects

5. Dynamic resource allocation based on business rules

Wrike resource planning data can be evaluated by OpenText Decision Service to determine whether a task should be assigned to an internal team, a contractor, or a specialized group. Rules can consider capacity, skill requirements, location, and project criticality, then update assignment recommendations in Wrike.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Better utilization of resources, fewer bottlenecks, and improved delivery predictability

6. Exception handling for blocked or noncompliant work

If a task in Wrike fails a compliance check, misses a required field, or violates a policy rule, OpenText Decision Service can classify the exception and determine the next action. Wrike can then create a remediation task, notify the responsible owner, or move the item into an exception workflow.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Standardizes exception handling and reduces time spent resolving policy issues manually

7. Bi-directional status updates for rule-driven case and workflow management

In organizations where Wrike is used to manage work tied to operational cases, OpenText Decision Service can trigger decisions when case attributes change, while Wrike sends task progress updates back to the decision layer. This supports rule changes such as reassigning work, escalating overdue items, or changing the required next step when a case reaches a specific condition.

• Data flow: Bi-directional
• Business value: Keeps operational decisions aligned with real-time work status and improves cross-team coordination

8. Policy-driven campaign launch governance

Before a marketing campaign moves from planning to execution in Wrike, OpenText Decision Service can validate whether all launch criteria are met, such as legal approval, regional compliance, asset readiness, and budget authorization. If conditions are satisfied, Wrike can advance the campaign to launch; otherwise, it can create corrective tasks and hold the release.

• Data flow: Wrike to OpenText Decision Service, then back to Wrike
• Business value: Reduces launch risk, improves governance, and ensures campaigns meet internal and regulatory requirements