# How agencies can audit client social queues with the DunSocial CLI

> Use structured CLI output to check each client’s scheduled queue separately, flag gaps or duplicates, and prepare a review report.

- Published: 2026-08-06
- Last updated: 2026-08-06
- Author: DunSocial
- Topics: cli, how-to

---

A queue audit is a read operation, which makes it a good first agency automation. The script can collect IDs, platforms, statuses and times while a person still decides whether a gap or collision needs action.

Run one client credential set at a time and label the output before combining it into a report.

Search phrases: audit social media queue CLI, agency content calendar report, DunSocial posts list JSON, client social scheduling audit, multi workspace social report.

## What you will do

- Export scheduled posts as JSON.
- Keep client data separated during collection.
- Flag operational questions without silently rescheduling content.

## Before you start

- Node.js 20 or newer and the DunSocial CLI installed with `npm install -g dunsocial`.
- A selected workspace and the DunSocial account IDs returned by `dun accounts list`.
- Browser login for a laptop, or a workspace-bound token stored in a secret manager for automation.

## Step by step

### 1. Select one client context

Load the workspace-bound token and expected workspace ID from your secret manager. Confirm identity before reading posts.

### 2. Export the queue

Use stable JSON output rather than parsing the human table.

```
dun posts list --status scheduled --json > client-scheduled.json
```

### 3. Check operational rules

Flag duplicate copy, identical timestamps, empty campaign days, missing media expectations and posts outside the approved campaign range. Do not treat every gap as a problem.

### 4. Prepare a human review report

Include workspace name, post IDs, platform, scheduled time and the question that needs a decision. Keep client copy out of reports shared beyond the account team.

## Check before you finish

- `dun workspace current` shows the intended workspace before a write command.
- The command uses DunSocial account IDs rather than social @handles.
- The new item appears in DunSocial with the expected CLI source, copy and time.

## Where to go next

After the account owner decides, reschedule or cancel by the existing post ID rather than creating replacement duplicates.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/audit-client-social-media-queues-with-the-dunsocial-cli. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login