n8n Workflow: Send Drafts to Zero Slop Editing API

Send your draft through Zero Slop—and get a safe, human-reviewed edit back

This n8n workflow manually sends your draft text to Zero Slop’s hosted editing API, checks the response for fact preservation and final-check status, and returns an output that instructs a human to review the edit before publishing.

What this workflow does

• Runs on demand when you start the workflow manually.
• Builds a draft payload including your draft text plus metadata such as genre and intended audience.
• Sends the draft to Zero Slop using an HTTP POST request to the endpoint: https://mcp.zero-slop.ai/v1/deslop.
• Evaluates the API response using response fields related to:
  • Fact preservation
  • Whether the output needed no changes or passed final checks after rewriting
• Returns instructions for human review—even when checks pass—so you can compare the original vs. returned text before using it.
• If checks do not pass, it returns the response with guidance to review warnings or keep the original draft instead of publishing automatically.

Use cases

• Editorial workflows where writers want Zero Slop edits but must confirm factual accuracy before publishing.
• Automation engineers and SaaS operators adding a quality gate before content goes live.
• Reducing risk in marketing, documentation, or compliance-sensitive drafts by enforcing review when the API flags issues.

Technical details

• Manual Trigger (runs when started manually)
• if and code nodes to assemble the payload and enforce pass/fail logic
• http request node to call Zero Slop deslop endpoint
• sticky note nodes for workflow guidance

Setup tips: Replace the sample draft and metadata with your approved input, confirm your environment can reach https://mcp.zero-slop.ai/v1/deslop, and adjust the HTTP request timeout for longer drafts. Update the pass/fail criteria to match the specific Zero Slop response fields you want to enforce.