Build a Content Approval Workflow in Agentforce Operations

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

1. Click + Create, and then select Blueprint.
2. Select From scratch.
3. Replace Untitled blueprint with Content Approval.

Add Stages

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 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.

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

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.