Skip to main content
Gradial’s AI agents automate content updates across your marketing systems — from a single copy change to a coordinated update across hundreds of pages. This section explains how content updates work in Gradial, how to run them, and how the workflow maps to your specific platform.

​
What Is a Content Update?

A content update is any task where Gradial reads, modifies, and publishes content in a connected system based on your instructions. This includes:
  • Editing copy, headlines, or body text on a page
  • Swapping or updating images and media
  • Modifying links, CTAs, or metadata
  • Updating reusable content blocks that appear across multiple pages
  • Replacing or reordering components on a page
  • Bulk changes applied across many pages or assets at once
You describe the change you want — in plain language, via a ticket, or through a structured template — and Gradial’s agent handles the authoring, validation, and publishing steps inside your connected system.

​
Update Complexity: Small, Medium, and Complex

Gradial organizes content updates into three tiers based on scope and risk. Understanding these helps you set appropriate review expectations and write better task prompts.

Small Updates

Single-item changes with a well-defined scope. The target is clear, the change is bounded, and there’s no cross-page or cross-asset impact.Examples: Updating a hero headline, swapping a CTA label and URL, replacing a banner image, correcting a typo.

Medium Updates

Changes that require interpreting structure, working across components, or touching content that is reused in multiple places.Examples: Updating a shared header or footer block, swapping a component type, adding a new section, updating metadata across related pages.

Complex Updates

Multi-page or multi-asset operations that require sequencing, conditional logic, or coordinated publishing.Examples: Find-and-replace across a site section, migrating content between templates, batch-updating from a spreadsheet, coordinating a campaign launch.

​
Small Updates

Single-item changes with a well-defined scope. The target is clear, the change is bounded, and there’s no cross-page or cross-asset impact. Examples: Updating a hero headline, swapping a CTA label and URL, replacing a banner image, correcting a typo. What to provide: The page URL or item path/ID, a clear description of what to change, and optionally a reference screenshot or copy doc.

​
Medium Updates

Changes that require interpreting structure, working across components, or touching content that is reused in multiple places. These carry more risk because a change in one place may surface in others. Examples: Updating a shared header or footer block, swapping a component type, adding a new section using an existing pattern, updating metadata across a set of related pages.
Updates to shared or reusable content blocks will affect every page or asset where that block appears. Always confirm scope before running.
What to provide: The specific component, block, or field to target, clear guidance on what changes and what stays the same, and a note on which pages or assets are in scope.

​
Complex Updates

Multi-page or multi-asset operations that require sequencing, conditional logic, or coordinated publishing. Examples: Finding and replacing copy across a site section, migrating content between templates, batch-updating a product line’s pages from a spreadsheet, coordinating a campaign launch across multiple assets. What to provide: A detailed brief, reference document or spreadsheet, and explicit publishing or sequencing instructions. Complex tasks are best run through Gradial’s batch capability or ticketing integrations.

​
How to Run a Content Update

The core workflow is the same across all platforms:
1

Create a task

From your project dashboard, select New Task. Identify the target page or content item, describe the change, and attach any reference materials.
2

Verify and run

Review the task details and click Run Task when ready.
3

Monitor the Work Log

The Work Log shows each step the agent is taking in real time: what it’s reading, modifying, and writing back to your system.
4

Review the result

Click View Page or navigate to the item in your platform to review changes in the staging environment before they reach production.
5

Approve or iterate

Promote or publish using your platform’s workflow. If adjustments are needed, describe them in the task chat and re-run.

​
Creating Tasks: Three Methods

Directly in Gradial

Use the task interface for structured, precise requests. Gradial validates the target path, lets you attach references, and gives you full control before running.

Via the AI Assistant

Describe the task conversationally from the homepage. The assistant converts natural language into a structured task automatically.“Update the homepage hero headline to say ‘AI-powered content operations for enterprise teams.’”

Via Ticketing Integration

Connect Gradial to Jira, Workfront, Wrike, or Azure DevOps. Gradial pulls tasks from your queue, executes the update, and writes results back — without leaving your workflow.

​
Staging and Review: How Gradial Protects Production

Gradial never writes directly to your production environment by default. All updates are staged for review first. The mechanism for this varies by platform.
Gradial uses AEM Launches as its staging layer. A Launch creates a non-destructive copy of your live content tree where the agent makes changes safely.Workflow: Gradial creates a Launch → agents author within it → reviewers validate via AEM Preview → Launch is promoted to production on approval or schedule.When to use Launches vs. Publish to Preview: Use Launches for multi-page changes, AI-generated content, or anything requiring formal approval. For low-risk single-page edits, publishing to Preview directly may be sufficient.Governance tips:
  • Define which content Gradial can update autonomously
  • Require approval before any Launch promotion
  • Use AEM workflow triggers to notify reviewers automatically
  • Maintain version history for rollback
Gradial stages updates using Sitecore’s publishing workflow, placing changed items into a review workflow state rather than publishing immediately.Workflow: Gradial authors changes in the Content Editor → items are set to a review workflow state (e.g., Awaiting Approval) → reviewers validate via the rendering host preview → items are advanced through workflow and published to the target.Key concepts: Workflow states gate what can be published — Gradial respects this and will not advance items past the configured review state. Publishing targets (Web DB, Edge) are set per environment in Gradial’s workspace settings.Governance tips:
  • Configure an explicit review workflow state for Gradial-authored content
  • Use the Work Log to trace which items were touched
  • For bulk updates, review a representative sample before approving the full batch
Gradial stages updates using Contentful’s environment model, authoring into a non-production environment that is promoted via alias once approved.Workflow: Gradial authors entries as Drafts in your staging environment → reviewers validate via the preview API or front-end preview URL → entries are published and the environment alias is updated (or content is promoted to master per your setup).Key concepts: Gradial only writes to the environment mapped in your workspace settings — it will never touch master/production directly. Entry IDs are the most reliable targeting method for structured content updates.Governance tips:
  • Map separate Gradial workspaces to separate Contentful environments
  • For coordinated multi-entry changes, use Contentful Launches if available on your plan
  • Always include Entry IDs in tasks for precision
Gradial updates Marketo emails, landing pages, and program assets. All changes are made to draft versions — Gradial never activates or approves assets on your behalf.Workflow: Gradial locates the target asset by name or ID → edits the draft → your team reviews and approves in Marketo → the asset is activated or scheduled per your campaign workflow.Key concepts: Approved assets cannot be edited directly. If an asset is approved, it must be unapproved (reverted to draft) before Gradial can make changes. Always specify the program context in your task for accurate targeting.Governance tips:
  • Include the asset name or Marketo URL in every task
  • Use Gradial’s batch capability to prepare multiple assets in parallel for a campaign launch, then approve them together in Marketo
Gradial updates SFMC content blocks, emails, and landing pages within Content Builder. Gradial saves a new version of the asset — activation within sends or journeys remains with your team.Workflow: Gradial locates the asset in Content Builder by name, ID, or folder path → edits and saves a new version → your team previews and approves in SFMC → the asset is used in sends or journeys as needed.Key concepts: Assets must be stored in Content Builder for Gradial to access them. For journey-based content, Gradial edits the underlying asset — re-linking it to an active journey is a manual step.Governance tips:
  • Organize Content Builder assets into clearly named folders to make task targeting easier
  • For shared content blocks used across many emails, confirm blast radius before updating
  • Use batch mode for campaign-wide refreshes like global disclaimer updates

​
Batch Content Updates

For large-scale operations, use Gradial’s Batch Updates capability. Upload a CSV or spreadsheet where each row defines an item and the change to apply. Gradial processes the full list, applying changes consistently across all targets.
Always review a sample of batch results before promoting to production. Batch works across all supported platforms.

​
Writing Better Prompts

Name the section, component, field, or entry — not just the page. Include the URL, path, or ID.
“Change the headline from X to Y” beats “update the headline.” Attach reference copy when you have it.
If you’re updating something that appears in multiple places, say so explicitly and confirm whether all instances should change.
Copy docs, Figma files, annotated screenshots, and spreadsheets all improve accuracy and reduce iteration.
For content generation, use one source per task (Figma, Word doc, or URL) for best results.
For platform connection setup, see Integrations. For building net-new pages, see New Page Workflow.