# Weekly content calendar chase-up from NocoDB to Slack

> Every Monday your team gets one Slack summary of the content pipeline, each writer gets a personal nudge, and this week's posts get draft captions.

- Workflow type: agent
- Services: NocoDB, Slack Bot
- Categories: Marketing, Operations
- Published: 2026-08-07

## What it does

- Reads your whole content calendar every Monday morning and works out what is overdue, what is due this week, and what is at risk of slipping because it is still in an early stage with a near deadline.
- Posts a single summary to your marketing channel, organised by stage, so the whole team sees the state of the pipeline at a glance.
- Sends each owner a private message listing only their own pieces, with a short nudge that names the actual piece and what it needs next.
- Drafts a ready-to-use social promo caption for every piece publishing this week and saves it onto the record, so the copy is waiting when the piece ships.

## What you'll need

- A NocoDB account with a content calendar table that tracks each piece's stage, owner, and publish date
- A Slack workspace where the assistant can post in your marketing channel and send direct messages
- Owner email addresses on the calendar records that match your team's Slack accounts, so the nudges reach the right people
- A free text field on the table to hold the draft promo caption

## Prompt

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.

## How to customize

- Change when it runs. Monday at 8am suits most teams, though Friday afternoon works better if you plan the week ahead.
- Set your own at-risk rule, for example flag anything still in an early stage within five days of its publish date instead of seven.
- Adjust the caption length and tone, point it at a different field, or turn the private nudges off entirely if you only want the channel summary.

## FAQ

### Do I have to use NocoDB's content tracker template?

No. Any table works as long as each row records the piece's stage, who owns it, and when it is meant to publish. Your columns can be named whatever you already call them, and you just say which is which when you set it up.

### Will it overwrite captions my team has already written?

No. It only fills the caption field when it is empty, so anything a person has already written is left alone. If you would rather it always refresh the caption, that is a one line change.

### What happens if an owner is not in our Slack workspace?

Their pieces still show up in the channel summary, and the assistant flags at the bottom that it could not reach that person privately. Nothing is silently dropped.

### Can the whole team see the individual nudges?

No. The channel summary covers the full pipeline and is visible to everyone in that channel, but each nudge is a private message containing only that person's own items.

### Does this work with both NocoDB Cloud and a self-hosted setup?

Yes. It works with either, you just point it at the web address where your NocoDB lives. Self-hosted setups need that address approved for access first.

Use this prompt in General Input: https://www.generalinput.com/prompts/weekly-content-calendar-chase-up-from-nocodb-to-slack