Work your whole Agorapulse social inbox from one console

I run community management across several social profiles and I want one console I can keep open all day to work my Agorapulse social inbox, instead of clicking between profiles and losing track of what is still unanswered. Build me an app that is a working queue, not a report.

When the app loads, resolve the account tree once and cache it for the session: Get Manager Organizations to find every organization my API key belongs to, then Get Organization Workspaces for each organization, then Get Workspace Profiles for each workspace. That gives me the full set of connected social profiles, and the queue works across all of them rather than one at a time.

The main view is the queue. Use Find Inbox Items across each resolved workspace to pull every open inbox item, and merge them into one list sorted oldest first, so the thing that has been waiting longest is always at the top. Show each row with the profile it came from, the item type (comment, message, mention or review), the author, a snippet of the message, and how long it has been waiting in plain language like "3h 40m". Give me filters for profile, item type and age. Anything past my two hour first response target gets a clear visual flag on the row, and the count of flagged items is visible at the top of the screen at all times.

Page the queue politely. Agorapulse inbox list endpoints return an object shaped { items, offset }, where offset is a cursor you pass back on the next request, and the page size limit is between 1 and 25. Fetch pages sequentially using the returned offset until the queue is filled or the cursor runs out. The rate limit is 500 requests per 30 minutes across the whole API, so do not poll in the background. Load on open, then refresh when I press a refresh button, and show me when the data was last fetched. Track roughly how many requests the session has used and back off gracefully rather than hitting the limit, and handle a 429 response by pausing and telling me instead of failing silently.

Clicking a row opens the item detail. Load the full thread with Get Conversation Messages so I can read the whole exchange in order, not just the snippet. From that screen I can reply inline with Reply to Inbox Item, choosing public or private reply where the channel supports both, and the reply box should make it obvious which one I am about to send. When an item needs a specialist, let me escalate it with the Slack Bot Send a Message action: I pick a channel, the app posts the profile, item type, how long it has been waiting, a link or reference back to the item and the thread summary, and the escalation is recorded on the item so I can see it was handed off and to where.

The app keeps its own triage state per inbox item, stored in the app's own storage and keyed by the Agorapulse item id, because Agorapulse does not hold these fields. Persist an owner, a tag, a snooze-until timestamp, and a first-response timestamp that is stamped automatically the first time I send a reply to that item from this app. Let me set owner, tag and snooze from both the queue row and the detail view. Snoozed items drop out of the active queue until the snooze expires, but still count toward backlog totals so nothing quietly disappears. Let me filter the queue to just the items I own.

Add a scorecard view built on that stored state. Show a "backlog older than 24 hours" count as the headline debt metric, broken down per profile, and a response time scorecard per profile covering median and average time to first response, the share of items answered inside the two hour target, and how many items are still open with no reply at all. Let me pick a date range. Then let me export that log to Google Sheets with Append Values, appending one row per item with the profile, item type, when it arrived, when it was first answered, the elapsed time, whether it met the target, the owner and the tag, so I can hand the sheet to a client in the weekly review.

Make the two hour first response target and the 24 hour backlog threshold configurable settings rather than hardcoded numbers, since different clients promise different things. Keep the whole thing fast and dense enough to live in a browser tab all day: the queue is the home screen, and I should be able to go from opening the app to sending a reply in a couple of clicks.