Catch paused Sendible queues before content stops going out

Every Monday at 8:10am, audit the health of my Sendible publishing setup and log it, so we never discover that a client's content stopped going out a week too late. Use a cron trigger for the Monday 8:10am schedule.

Start by pulling the current state of the account. Use Sendible "Get Social Profiles" to list every connected social profile and profile group, and Sendible "Get Queues" to list every publishing queue along with its posting schedule and its pause state.

Append a dated snapshot to a Google Sheets tracking tab using "Append Values". Write one row per queue with four columns: the audit date in YYYY-MM-DD form, the queue name, that queue's posting times collapsed into a single readable comma separated string, and whether the queue is paused as Yes or No. Always append below the existing rows and never overwrite them, so the tab accumulates a week over week history of the publishing setup. The spreadsheet and the tab name should be easy to change at the top of the workflow.

Then, only if at least one queue came back paused, send a Slack message to the social team channel using Slack "Send a Message". Keep it to a short bulleted list, one bullet per paused queue, naming the queue and the profiles affected so someone knows whose content is at risk. Resolve the affected profile names from the Sendible "Get Social Profiles" results. If a paused queue does not carry an association to specific profiles, name the queue on its own rather than guessing at which profiles it feeds. Do not dump the full queue inventory into Slack; the spreadsheet is the record, and the message exists only to get someone to unpause the queue before the week's content silently fails to publish.

Skip the Slack step entirely when every queue is active. If zero queues are paused, the workflow should finish after writing to the sheet and send nothing at all, so the channel only ever hears about real problems.

Scope note for whoever builds this: Sendible exposes publishing operations only. There is no operation to list already scheduled or published posts, and no analytics or engagement endpoints. Keep this workflow to the queue and profile inventory plus the pause-state alert, and do not add post level or engagement reporting.