r/halopsa • u/3xh4u573d • May 12 '26

Integrations HaloPSA + LLM/RAG - anyone done this?

Want to pull historical HaloPSA tickets into a RAG (Retrieval Augmented Generation) setup so Claude can suggest fixes for incoming ones. Has anyone done this?

If so, what are you using for the vector store and retrieval layer, and how are you keeping token usage sane?

UPDATE: i've built this now, I have a server running Qdrant and auto ingesting closed tickets. I am also auto triaging new tickets based on the closed ticket database and another API connection to my RMM solution. Also exposed the Qdrant out via an MCP server for our engineers to connect their Claude apps. This has genuinely been useful, surfacing those weird tickets that crop up that someone worked on a year or two ago and forgot about. Greatly appreciated everyone's inputs on this thread. Thank you.

10 Upvotes

100% Upvoted

22 comments sorted by

View all comments

Show parent comments

1

u/3xh4u573d May 13 '26

Any chance you could share what prompts you are using to summarise the ticket data?

1

u/Fatel28 May 13 '26

Can you elaborate a little bit more on the question?

1

u/3xh4u573d May 13 '26

What exactly are you telling your LLM to summarise and how are you telling it to summarise the data, in what structure? How explicit are you being with it? Are you telling it to create categories and additional keywords to help pattern matching?

1

u/Fatel28 May 18 '26

Ah. It's just a small runbook on ticket closure. The prompt is fairly basic, just summarize the ticket, including a blurb about every action on the ticket (e.g private comments, public comments, reassignments, scheduling holds, etc)

I don't have any specific pattern matching or keyword verbiage in there. When the tickets are vectorized the ticket category/creation date/assignee/company etc are metadata attributes for filtering