Customer Success Operations · AI Automation

n8n · AI Knowledge
Base Automation

Turning resolved support cases into reusable customer knowledge — automatically.

  • n8n
  • Zoho Desk
  • AI
  • Knowledge Management
  • Customer Success Operations
01 · The automation

From closed ticket to
review-ready knowledge.

ONE WORKFLOW / 12 STEPS
Ticket closes→Qualify→Check existing KB→Draft→Human review

The workflow identifies reusable knowledge, checks whether it already exists, and creates a draft for review.

</> Learn the tech behind this workflow

  1. Trigger

    POST · Webhook

    Zoho Desk sends a POST request to the n8n webhook when a ticket closes, passing its ticket ID.

  2. Get ticket details

    GET · Zoho Desk API

    Use the ticket ID to retrieve the ticket’s metadata from Zoho Desk.

  3. Get conversation

    GET · Zoho Desk API

    Retrieve the conversation and resolution history behind the support case.

  4. Prepare context

    JavaScript · JSON

    Clean and structure the ticket data into focused context for the AI.

  5. Identify knowledge

    OpenAI · Structured output

    Evaluate whether the resolution contains reusable knowledge and return a structured decision.

  6. Route the decision

    IF

    Useful knowledge → continue. One-off resolution → stop.

  7. Search existing KB

    GET · API

    Search the knowledge base for articles related to the identified solution.

  8. Check for duplicates

    OpenAI · Semantic comparison

    Compare meaning, not just keywords, to check whether the solution is already documented.

  9. Route again

    IF

    Already documented → stop. A knowledge gap → continue to drafting.

  10. Generate the draft

    OpenAI

    Turn the resolved case into a clear knowledge-base article draft.

  11. Log for review

    Google Sheets · Append

    Append the draft and ticket reference to the knowledge tracker.

  12. Notify the reviewer

    Gmail

    Email the reviewer so they can check the draft before publication.

02 · The business view

Your team solves it. The system remembers.

01 / RESOLVE

Ticket resolved

The agent closes the case. Knowledge capture begins.

02 / QUALIFY

Worth documenting?

Keep reusable solutions. Skip one-off requests.

03 / CHECK

Already documented?

Find the gap before creating another article.

04 / CREATE

Draft the answer

Turn the resolution into a useful first draft.

05 / APPROVE

Human review

A person checks the answer before it goes live.

Human approval required before publishing.

Before · Manual

Solved. Then forgotten.

Agents remember, check, write, track, and send for review.

After · Automated

Closed. Then captured.

The workflow prepares the draft. A human makes the final call.

Solve once.
Reuse the knowledge.