VLClean Plain comparisons of self-hosted media tools

How to see what has been requested already in Slack workspaces in 2026

Learn how Slack workspace media hosts can find past movie and show requests, check their status, and compare ways to keep a searchable request history.

By VLClean ·

VLClean is published by the makers of Askarr and Watcharr, which are compared here alongside other tools.

To see what has already been requested, review the request history or shared record used by the workspace and look for each title's current status. Check whether the record you use shows each title's status. Askarr’s plans include a request history with live status. [1] A webhook from Radarr and Sonarr reports back so the site shows when a title was added and downloaded. [1]

OptionHow to find past requestsStatus details to checkCost details
AskarrSearch for a movie or show, or paste a TMDB, IMDb, or TVDB link to find the title. [1][1]Plans include request history with live status, and the site shows when a title was added and downloaded. [1][1]Free costs $0 and allows 10 requests a month. [1] Plus costs $3.99 a month for 50 requests a month. [1] Pro costs $6.99 a month for unlimited requests. [1]
Slack conversation searchSearch relevant workspace conversations for a title or its request message.Check the surrounding conversation for a recorded outcome. Features beyond this method are not established here.not published
Shared request listSearch the chosen list for the title or its entry.Check whether the selected service records request outcomes and status changes.not published
Request form and response recordSearch the available form response record for the submitted title.Check whether the chosen service retains past responses and allows outcomes to be recorded.not published

What you need before you start

Before reviewing past movie and show requests, decide where requests are collected and what information needs to be visible. A request history, shared list, or form response record can provide a starting point, depending on the method already in use. Check whether the record identifies each title clearly and whether it shows what happened after someone submitted it.

Make sure the person reviewing requests can access the relevant record. If requests arrive through Slack messages, decide how to distinguish a new request from a follow-up about an existing title. Searching for a title is more useful when the same movie or show can be recognized across conversations and records.

Radarr and Sonarr are helper programs used to find and add movies and shows to a library. Have them ready if they are part of the existing process for adding requested titles. Decide who reviews requests and who can confirm whether a title was added or downloaded.

If the current method does not provide a clear history, consider whether a dedicated request website or a shared record would make past requests easier to review. Check the available status details before moving to another method.

Step by step

  1. Find the place where requests are recorded. Start with the request website, shared list, form responses, or Slack conversation used by the workspace. Use the existing method before creating a second record that could split the history.
  1. Search for the title. Enter the movie or show name into the available search field or search the relevant conversation or record. If the title is known by another name, check whether the record supports that name as well. Askarr lets someone paste a TMDB, IMDb, or TVDB link to find a title. [1]
  1. Open the matching request. Confirm that the record refers to the intended movie or show. If several entries appear to refer to the same title, check their details before treating them as separate requests. Do not assume that a mention in a conversation means a request was formally submitted.
  1. Read the recorded status. Look for information that explains what happened after the request was submitted. A submitted request and a title that has been added are different stages, so use the recorded status rather than assuming the request is complete. Askarr plans include a request history with live status. [1]
  1. Check whether the title was added or downloaded. If the request method provides these details, use them to distinguish an outstanding request from one that has progressed. Askarr uses a webhook from Radarr and Sonarr to report back so the site shows when a title was added and downloaded. [1]
  1. Review the surrounding records when the status is unclear. Check the original request, any follow-up messages, and the current record before deciding whether the title still needs attention. If the available information does not confirm the outcome, leave it as unconfirmed rather than marking it complete without evidence.
  1. Keep the history useful for future searches. Use the existing process to record the outcome of requests and clarify how people should check the status of a title. If the current method does not preserve a searchable history, compare alternatives that explicitly describe their history and status features.

Tools that can do it

Askarr is a hosted website that works with your existing Radarr and Sonarr. [1] Its plans include a request history with live status, and the site shows when a title was added and downloaded. [1][1] You request a movie or show on Askarr, and your own Radarr and Sonarr add it. [1] To connect the request workflow, you add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [1] Nothing is installed; you add Askarr as an import list in Radarr and Sonarr. [1]

Slack conversation search can be considered when requests are mentioned directly in workspace conversations. Search for the title or the message used to request it, then check the surrounding discussion for a recorded outcome. Confirm whether the workspace has a consistent way to mark completed requests, because a conversation mention alone does not establish the current status.

A shared request list can serve as a central place to review titles if the chosen list records submitted requests and their outcomes. Before choosing one, check whether it supports searching by title, preserving past entries, and showing status changes. The available facts here do not establish the features of any particular shared-list service.

A request form with a response record can provide a way to collect titles and review submitted entries. Check whether the chosen form keeps responses available for later searches and whether the outcome of each request can be recorded. The available facts here do not establish the features or fees of a particular form service.

These options serve different purposes. Choose according to where requests are already collected, what history needs to be retained, and whether the current status must show that a title was added or downloaded.

Common mistakes to avoid

Avoid treating every mention of a movie or show in Slack as a submitted request. A conversation may discuss a title without asking for it to be added. Check the actual request record before counting it as a request.

Avoid relying only on a title's name when reviewing previous requests. Check the matching details so a similar title or a follow-up conversation is not mistaken for a separate request.

Avoid assuming that a submitted request means the title has been added or downloaded. Review the status information provided by the chosen method, and leave the outcome unconfirmed when the available record does not establish it.

Avoid splitting requests across several places without a clear rule for finding the history. If people use Slack messages, a shared list, and a separate request website, decide which record is used to check the current status.

Avoid choosing a tool based only on how requests are submitted. Check how it preserves request history, how someone searches for an existing title, and whether it reports changes after submission. For a workflow that uses Radarr and Sonarr, also check how the request method communicates with those programs and what information it displays about the result.

Frequently asked questions

How can Slack workspace media hosts see previous movie requests?

Start with the place where movie requests are recorded, such as the relevant Slack conversation, a shared list, or a request website. Search for the title and open the matching record. Check the recorded status to determine whether the request is still outstanding or has progressed. Askarr plans include a request history with live status. [1]

Can Askarr show which movies and shows were added?

Askarr uses a webhook from Radarr and Sonarr to report back so the site shows when a title was added and downloaded. [1] Its plans also include a request history with live status. [1] Check the relevant request record to review the information available for a title.

How can an existing request be found in Askarr?

You request a movie or show on Askarr, and your own Radarr and Sonarr add it. [1] A TMDB, IMDb, or TVDB link can also be pasted to find the title. [1] Check the displayed status before deciding whether another request is needed.

Does Askarr work with existing Radarr and Sonarr libraries?

Askarr is a hosted website that works with existing Radarr and Sonarr. [1] You add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [1] A webhook from those programs reports when a title was added and downloaded so the site can display the status. [1]

What should be checked before choosing a request history tool?

Check whether the chosen method keeps previous requests searchable, identifies the correct title, and shows the status information needed to review outcomes. If Radarr and Sonarr are part of the existing workflow, check how requests move into those programs. Askarr plans include a request history with live status, and the site shows when a title was added and downloaded. [1][1]

The Free plan costs $0 and allows 10 requests a month. [1]

Try Askarr

Sources

  1. Askarr's own description of itself (the product of this site's publisher)

Related comparisons