Adobe Workfront - Kentico Integration and Automation

Common Integration Use Cases Between Adobe Workfront and Kentico

1. Campaign Brief to Website Content Production Workflow

Direction: Adobe Workfront ? Kentico

Marketing teams can create campaign briefs, launch plans, and content production tasks in Adobe Workfront, then push approved web content requirements into Kentico for page creation and publishing. This is useful for coordinated product launches, seasonal campaigns, and promotional microsites where multiple teams need a shared workflow from planning to publication.

• Workfront captures campaign scope, deadlines, owners, and approval steps
• Kentico receives page, component, or content item requests for implementation
• Reduces manual handoffs between marketing operations and web content teams
• Improves launch readiness and keeps web publishing aligned with campaign schedules

2. Content Review and Approval Synchronization

Direction: Bi-directional

When web content is drafted in Kentico, approval status can be synchronized back to Adobe Workfront so project managers and stakeholders can track review progress in one place. This supports controlled publishing processes for regulated industries, brand-sensitive content, and high-volume editorial operations.

• Kentico content status updates flow to Workfront task or proof records
• Workfront approval decisions can trigger next-step publishing actions in Kentico
• Provides visibility into bottlenecks across editorial, legal, and brand review teams
• Helps ensure only approved content is released to production

3. Creative Asset Delivery from Production to Web Publishing

Direction: Adobe Workfront ? Kentico

Creative assets such as banners, hero images, videos, and campaign graphics can be produced and approved in Adobe Workfront, then delivered to Kentico for use in website pages and landing pages. This is especially valuable for teams managing frequent creative updates across multiple digital properties.

• Final approved assets are routed from Workfront to Kentico
• Asset metadata can include campaign name, usage rights, and expiration dates
• Minimizes the risk of using unapproved or outdated creative files
• Speeds up web publishing by removing manual file transfer steps

4. Website Request Intake and Work Management

Direction: Kentico ? Adobe Workfront

Requests submitted through Kentico, such as content updates, landing page changes, or campaign microsite needs, can automatically create work items in Adobe Workfront. This gives marketing and web teams a structured intake process and ensures requests are prioritized, assigned, and tracked consistently.

• Kentico forms or content workflows generate Workfront projects, tasks, or issues
• Request details such as page URL, content type, and due date are captured automatically
• Improves governance for website change management
• Creates a single operational queue for digital experience work

5. Personalized Campaign Content Planning

Direction: Adobe Workfront ? Kentico

Adobe Workfront can be used to plan personalized campaign variants, audience-specific content, and regional web experiences, then pass structured content requirements to Kentico for implementation. This supports teams delivering segmented experiences across markets, customer groups, or product lines.

• Workfront manages content variant planning and localization schedules
• Kentico receives structured content requirements for personalized pages or modules
• Supports coordinated execution across content, design, and web development teams
• Helps launch targeted experiences on time and with fewer production errors

6. Launch Readiness and Publishing Coordination

Direction: Bi-directional

For major launches, Adobe Workfront can manage the overall project timeline while Kentico tracks content readiness and publishing milestones. This integration gives launch managers a complete view of what is complete, what is pending, and what still needs approval before go-live.

• Workfront holds master launch plans, dependencies, and milestone dates
• Kentico updates content completion and publish status back to the project plan
• Enables better coordination between marketing, web, legal, and product teams
• Reduces launch delays caused by missed content dependencies

7. Content Governance and Audit Trail Alignment

Direction: Bi-directional

Organizations with strict compliance or brand governance requirements can align approval records between Adobe Workfront and Kentico. Workfront can serve as the system of record for approvals, while Kentico stores the final published content and associated metadata, creating a clear audit trail from request to publication.

• Approval history in Workfront is linked to published content in Kentico
• Supports auditability for regulated or highly controlled content environments
• Makes it easier to prove who approved what and when
• Improves accountability across marketing, legal, and compliance teams

8. Post-Launch Content Optimization Requests

Direction: Kentico ? Adobe Workfront

After a page or campaign goes live in Kentico, performance insights or content update needs can be converted into follow-up work in Adobe Workfront. This allows teams to manage optimization cycles for web content, conversion pages, and campaign assets in a disciplined workflow.

• Kentico content owners can trigger optimization or refresh tasks in Workfront
• Supports continuous improvement for landing pages and campaign content
• Ensures post-launch changes are tracked and prioritized alongside other work
• Helps marketing teams respond quickly to performance data and stakeholder feedback