--- schema_version: "1" id: b692aaa549d5e8011ae5a18a62fb08d9df1fbdbd0324486007eb7922c56068d3 title: Build a Content Approval Workflow in Agentforce Operations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/afo_workflow_example.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.afo_workflow_example.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: ca4c0220836878ebdde74a013bf1836b8bc0c9e05a43866757509663d6179d63 description: Build a content approval blueprint in Agentforce Operations to automate your team's review and sign-off process. This example walks you through creating fields, configuring stages and tasks, testing the workflow end to end, and publishing the blueprint. products: - Cross Cloud release: "264" --- # Build a Content Approval Workflow in Agentforce Operations Build a content approval blueprint in Agentforce Operations to automate your team's review and sign-off process. This example walks you through creating fields, configuring stages and tasks, testing the workflow end to end, and publishing the blueprint. ### Required Editions
License Required

This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license.

To purchase an Agentforce Operations license, contact your Salesforce account executive.
![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-agentforce_operations-264-0-0-production-enus/dce314e6-0a31-4a8b-98f7-3d2a3fd02ee2/images/icon_note.png) Note Agentforce Operations is the new name for the product previously known as Agentforce Supply Chain. As we work on updates, you can possibly see references to both Agentforce Operations and Agentforce Supply Chain. ## Scenario Your company produces marketing content including blog posts, case studies, and campaign copy. Before anything goes live, it goes through a standard review and approval process: a writer submits the draft, an editor reviews it for quality and accuracy, and a manager gives final sign-off. Right now, this all happens over email, so drafts get lost, reviewers miss deadlines, and no one can tell where any given piece is in the process. Agentforce Operations automates this process. ## Design and Build the Blueprint A blueprint is the reusable template that defines the stages, tasks, and routing rules for a workflow. To build a blueprint, start by understanding what your finished workflow needs to do. Before you configure anything, map out the handoffs in your process: who submits, who reviews, and what information passes between them at each step. Each stage you build groups a set of tasks, and each task collects or shares the information needed for that step. In this example, the finished workflow moves draft content through an AI completeness check, an editorial review, a revision cycle, and a manager sign-off. That end-to-end flow maps directly to the stages and tasks you configure here. ### Add Fields That Collect and Pass Information Before you build the blueprint, create the fields that tasks in the workflow use to collect and pass information. Fields are workspace-level resources, so you create them once and they become available to add to any task in any blueprint. For this exercise, you need three: one for the writer to submit draft content, one for the editor to record feedback, and one for the writer to submit a revised version. 1. In the Agentforce Operations navigation sidebar, click **Fields**. 2. Click **\+ Add** field, name it Content Draft, and select **Text** as the type. Click **Create**. To accept a document upload instead, select **Document** as the type. 3. Click **\+ Add** field, name it Review Notes, and select **Text** as the type. Click **Create**. 4. Click **\+ Add** field, name it Revised Draft, and select **Text** as the type. Click **Create**. To accept a document upload instead, select **Document** as the type. ### Create the Blueprint Creating a blueprint from scratch gives you full control over its structure to match your team's review process exactly. If you have an existing process documented, you can also generate a blueprint draft using AI. See [Create an Automation Template with a Blueprint in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") for details. When you publish the blueprint, workspace members with the right permissions can use it to create new workflows and run content through approval. 1. Click **\+ Create**, and then select **Blueprint**. 2. Select **From scratch**. 3. Replace Untitled blueprint with Content Approval. ### Add Stages Stages define the phases of the workflow. Each stage groups a set of related tasks and controls when those tasks become active. Start conditions determine when each stage begins relative to the others: the first stage starts when the workflow launches, and subsequent stages start after the previous one completes. In this blueprint, you create three stages: Submission, Editorial Review, and Final Approval. 1. Add the first stage: 1. Click **+Add stage** 2. Name it Submission. 3. Set its start condition to **When the workflow starts**. 4. Click **Add stage** 2. Add the second stage: 1. Click **+Add stage** 2. Name it Editorial Review. 3. Set its start condition to **After the previous stage completes**. 4. Click **Add stage** 3. Add the third stage: 1. Click **+Add stage** 2. Name it Final Approval. 3. Set its start condition to **After the previous stage completes**. 4. Click **Add stage** ## Add Tasks to Blueprint Stages Add tasks to the submission, editorial review, and final approval stages in the blueprint. ### Add One Task to the Submission Stage Add one task to the Submission stage that has the writer upload draft content including a title and a summary. 1. Click **\+ Task**. 2. Name it Submit draft content. 3. Set Start to **When the stage starts**. 4. Set Due to **Time to complete: 1 Day**. 5. Set the assignee to yourself or a colleague representing the writer role. 6. In the Description field, enter: Paste your draft content and provide a title and a brief summary of the topic. 7. In Request information, click **+Add field or role**. 8. Search for and select **Content Draft**, which is the field you created in the Add Fields That Collect and Pass Information step. 9. Click **Add**. ### Add Four Tasks to the Editorial Review Stage The Editorial Review stage has four tasks. The first is an approval task assigned to an AI agent that checks whether the submission is complete before any human reviewer sees it. The second is a standard task where the editor reviews and provides feedback. The third returns the work to the writer for revision. The fourth is an approval task where the editor signs off on the revised version before it moves to the manager. 1. Add the first task, which is a completeness check. 1. Click **\+ Approval**. 2. Name the task Check submission for completeness. 3. Set Start to **When the stage starts**. 4. Set Due to **Time to complete: 1 Day**. 5. Assign it to an AI agent: In Assigned to, select **AI Agents**. Then select the **Document Agent 004**, which is the agent best suited for verifying that required inputs are present. 6. Set the **Fallback assignee** to yourself. 7. In the Description field, enter: Review the submitted content. If a title, topic summary, and draft document are all present, approve this task. If anything is missing, reject this task and list exactly what is missing in your comments. 8. In the Information for approval section, click **\+ Select** field and select Content Draft. 9. Click **Apply**. 10. In the If Rejected section, for Action, select **Restart task**. 11. For Task to restart, select **Submit draft content**. 12. Select **Require comments** so that the agent must describe what’s missing before rejecting. 13. Click **Add** to save the approval task. 2. Add the second task, which is the human editorial review. 1. Click **\+ Task**. 2. Name the second task Review content. 3. Set Start to **After another task ends**, and then select **Check submission for completeness**. 4. Set Due to **Time to complete: 3 Days**. 5. Set the assignee to yourself or a colleague representing the editor role. 6. In the Description field, enter: Review @Content Draft for accuracy, tone, and quality. Record your feedback and required changes in Review Notes. For the "@" reference to work, type this text directly. Do not use copy/paste. 7. In Share information, click **+Select field** and select **Content Draft**. 8. In Request information, click **\+ Add field or role** and select **Review Notes**. 9. Click **Add** to save the approval task. 3. Add the third task, which is for the writer to review the editor’s comments and make content revisions. 1. Click **\+ Task**. 2. Name the third task: Revise content. 3. Set Start to **After another task ends**, and then select **Review content**. 4. Set Due to **Time to complete: 3 Days**. 5. Set the assignee to yourself or a colleague representing the writer role. 6. In the Description field, enter: Review @Review Notes and revise your content accordingly. Upload your revised version to Revised Draft. For the "@" reference to work, type this text directly. Do not use copy/paste. 7. In Share information, click **+Select field** and select **Content Draft and Review Notes**. 8. In Request information, click **+Add field or role** and select **Revised Draft**. 9. Click **Add** to save the approval task. 4. Add the fourth task, which is for the editor to approve the revised content before it goes to a manager for final approval. 1. Click **\+ Approval**. 2. Name the task Approve revised content. 3. Set Start to **After another task ends**, and then select **Revise content**. 4. Set Due to **Time to complete: 2 Days**. 5. Set the assignee to yourself or a colleague representing the editor role. 6. In the Description field, enter: Review @Revised Draft against your original feedback in @Review Notes. Approve if the revisions are satisfactory. Reject and explain what still needs to change if they are not. For the "@" reference to work, type this text directly. Do not use copy/paste. 7. In the Information for approval section, confirm that **Revised Draft** and **Review Notes** are listed. If they’re not, click **\+ Select field** and select **Revised Draft** and **Review Notes**. 8. In the If Rejected section, select **Restart task** and choose **Revise content**. 9. Select **Require comments**. 10. Click **Add approval task**. ### Add One Task to the Final Approval Stage The manager's sign-off is a formal approve/reject decision, which makes this an approval task rather than a standard task. If the manager rejects, the content goes back to the writer with a required explanation. 1. Click **\+ Approval**. 2. Name it Approve content for publication. 3. Set Start to **When the stage starts** 4. Set Due to **Time to complete: 2 Days**. 5. Set the assignee to yourself or a colleague representing the manager role. 6. In the Description field, enter: Review @Revised Draft and @Review Notes. Approve or reject the content for publication. For the "@" reference to work, type this text directly. Do not use copy/paste. 7. In the Information for approval section, click **\+ Select field** and select **Revised Draft** and **Review Notes**. 8. In the If Rejected section, for **Action** select **Restart task**, and for **Task to restart** select **Revise content**. 9. Select **Require comments** so the manager must provide a reason for rejection. The writer can see this comment in the workflow when the task restarts. 10. Click **Add approval task**. ## Test the Blueprint Testing before publishing catches problems when they're still easy to fix, such as–a task that starts at the wrong time, a field that wasn't shared with the right person, or an AI agent instruction that produces inconsistent output. When you start the workflow, each task assignee receives an email notification with everything they need to complete the task directly from their inbox without logging in to Agentforce Operations. It can take several minutes for each email to be delivered. ### Create the Test Workflow 1. Click **\+ Create workflow**. 2. Change the default Workflow name to Test — Content Approval. 3. Click **Create**. ### Test Stage 1: Submission The best way to test is to run the workflow end to end with realistic content, just like a real submission would work. This example includes sample content for you to test with, but you can also test with your own content. 1. In the Submission stage, click **Submit draft content**. 2. In the Content draft text field, copy and paste the following draft content: Title: Getting Started with Automated Approval Workflows Topic summary: An introduction to approval workflows — what they are, why they matter, and how automation reduces delays and manual follow-up. Draft content: Approval workflows are a core part of how teams move work forward. Whether you're reviewing a contract, signing off on a budget, or publishing a piece of content, a clear process makes the difference between a smooth handoff and a bottleneck. Most manual approval processes share the same problems: requests get lost in email, reviewers don't know it's their turn, and no one has visibility into where things stand. Automating the process solves all three. An automated approval workflow routes each request to the right person at the right time, sends reminders when action is needed, and gives everyone involved a live view of status. Teams that automate approvals typically see faster turnaround times and fewer errors from miscommunication. 3. Click **Complete** and click away from the open panel to return to the workflow. ### Test Stage 2: Editorial Review 1. The AI Agent reviews the submission against the task requirements. 1. Since the required information is there, the agent completes the task. 2. Click **Show details** to see the steps it performs and its reasoning. 3. Verify that the AI agent task produces an output. 2. In the Editorial Review stage, click **Review content**. 3. In the Review Notes field, copy and paste the following feedback. Overall the draft is in good shape. Clear tone, good structure. A few things to address before final approval: Add a hook to the opening. The first sentence is solid but generic. Consider leading with a pain point that's more specific to the reader — something like starting with the email chain problem before describing what approval workflows are. "Automating the process solves all three" — this sentence is doing a lot of work without delivering. Either list how it solves each of the three problems or cut this line and let the next paragraph carry the explanation. Missing: a brief description of how the process works. The draft explains the problem and the benefits but never describes what an automated approval workflow actually looks like in practice. Add 1–2 sentences on the basic structure: a request comes in, it routes to the right reviewer, they approve or reject, and the outcome is recorded. "Fewer errors from miscommunication" — vague. Replace with a more concrete outcome, such as fewer missed deadlines or fewer requests falling through the cracks. No call to action or next step. The draft ends abruptly. Add a closing sentence that points the reader toward getting started or learning more. 4. Click **Complete** and click away from the open panel to return to the workflow. 5. Still in the Editorial Review stage, click **Revise content**. 6. In the Revised Draft field, copy and paste the following revision: Title: Getting Started with Automated Approval Workflows Topic summary: An introduction to approval workflows — what they are, why they matter, and how automation reduces delays and manual follow-up. Revised draft: If you've ever dug through your inbox looking for the latest version of a document, or realized a request has been sitting unanswered for a week because no one knew it was their turn, you already know the cost of a manual approval process. Approval workflows are how teams move work forward — and automating them is how teams stop losing track of it. Most manual approval processes share the same problems: requests get lost in email, reviewers don't know it's their turn, and no one has visibility into where things stand. An automated approval workflow solves each of these: requests are routed automatically, reviewers get notified when action is needed, and every stakeholder can see exactly where a request is at any point in the process. Here's how it works in practice: a request comes in, the workflow routes it to the right reviewer based on rules you define, the reviewer approves or rejects it, and the outcome is recorded. If the reviewer misses a deadline, the system sends a reminder or escalates automatically. Nothing falls through the cracks. Teams that automate approvals typically see faster turnaround times and fewer requests going unanswered due to missed handoffs. The more steps an approval process has, the more value automation adds. Ready to build your first approval workflow? Start by mapping out your process: who submits, who reviews, and what "approved" looks like at each step. Once you have that, you have everything you need. 7. Click **Complete** and click away from the open panel to return to the workflow. 8. Still in the Editorial Review stage, click **Approve revised content**. 9. Add a comment Great revisions. No further notes. And click **Approve**. 10. Click away from the open panel to return to the workflow. ### Test Stage 3: Final Approval 1. In the Final Approval stage, click **Approve content for publication**. 2. Add a comment: Approved for next blog publish. Then click **Approve**. In a real testing scenario, always test both outcomes to confirm that the blueprint is configured correctly. 3. Click away from the open panel to return to the workflow, which should be fully complete. 4. If anything doesn't work as expected, such as a stage activating out of order, or a task not activating when expected, return to the blueprint and check the start conditions on the affected stage or task. Then test again. ## Publish Your Blueprint Publishing makes your blueprint available to everyone in the workspace who has permission to create workflows. If your process is sensitive or access needs to be limited, don't publish—keep the blueprint unpublished and share it directly with the people who need it. Publish only when the blueprint is tested and ready for broad use. Publishing requires the Publisher role. If you don't have this role, your workspace Publisher can review and publish the blueprint on your behalf. 1. When the test workflow completes successfully, return to the blueprint. 2. If you have the Publisher role, click the three dots and then click **Publish**. 3. Add a version note: v1.0 — initial content approval workflow. 4. Click **Publish**. If you don't have the Publisher role, your workspace Publisher can review and publish the blueprint on your behalf. You've built, tested, and published your first blueprint.