Weekly content calendar chase-up from NocoDB to Slack

Every Monday at 8am, review my content calendar in NocoDB and get the week moving. Use the NocoDB List Table Records operation to pull every piece from my content calendar table, paging through the results until you have the full list, and read each record's title, stage, owner, and publish date. My column names may differ from those labels, so match on meaning rather than on exact names.

Sort the pieces into three groups. Overdue means the publish date has already passed and the piece still is not published. Due this week means the publish date falls between today and the end of Sunday. At risk means the piece is still sitting in an early stage such as idea, brief, or first draft while its publish date is within the next seven days, so the work left does not realistically fit the time remaining. Ignore anything already published, cancelled, or archived.

Post one summary to the marketing channel in Slack using the Slack Bot Send a Message operation. Organise it by stage rather than by person. Lead with the counts for overdue, due this week, and at risk, then list the individual pieces under each stage with their owner and publish date. Use Slack formatting so it is easy to skim, and keep it short enough to read without scrolling far.

Then message each owner privately. Group the pieces by owner first so every person receives exactly one direct message, never one message per item. Use the Slack Bot Look Up User by Email operation to turn the owner recorded on the record into a Slack user, then Open a Conversation to get their direct message channel, then Send a Message to deliver the nudge. Each direct message should list only that person's own items and give a short, specific nudge that names the actual piece and what it needs next, for example moving a particular draft into review, rather than a generic reminder to check the calendar. If an owner cannot be matched to a Slack user, skip their direct message and note that person at the bottom of the channel summary instead.

For every piece scheduled to publish this week, draft a short social promo caption of roughly one or two sentences, written in our voice and ready to post when the piece ships. Write it back onto the record using the NocoDB Update Table Records operation, into the promo caption field. Only fill that field when it is currently empty, so you never overwrite copy someone has already written, and never modify records outside this week's publishing set.

If the table is empty, or nothing is overdue, due, or at risk, still post a short all clear to the marketing channel so the team knows the check ran, and skip the direct messages that week.