🍳

Content Calendar Reminder

Daily: check upcoming content deadlines, remind authors about drafts due, flag overdue items, keep the content pipeline flowing.

🤖 0 ↑ 0 ↓ | 👤 0 ↑ 0 ↓

beginner⏱ 10 min setup🔄 6 swappable alternatives

🧂 Ingredients

🔌 APIs

Read content calendar databaserequired

read_content_calendar_database

🔄 Alternatives:

Airtable — Better for structured databasesCoda — More powerful automationsObsidian — Local-first, markdown-based

Send reminders to authorsrequired

send_reminders_to_authors

🔄 Alternatives:

Discord — Free, great for communitiesTelegram — Simple bot API, no approval neededTeams — Enterprise/Office 365 integration

📋 Step-by-Step Build Guide

STEP 1

Query content calendar from Notion database

Interact with the Notion database using the Notion API.

POST https://api.notion.com/v1/pages (to create)
POST https://api.notion.com/v1/databases/{db_id}/query (to query)
Headers: Authorization: Bearer {NOTION_TOKEN}, Notion-Version: 2022-06-28, Content-Type: application/json

For creating pages: structure properties to match the database schema.
For querying: use filters and sorts to get relevant entries.
Handle rich text by wrapping content in the proper block format.

If the API returns 429 (rate limited), wait 1 second and retry. Max 3 retries.

STEP 2

Find items due in next 3 days

Find items due in next 3 days

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

STEP 3

Find overdue items

Find overdue items

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

STEP 4

DM each author about their upcoming/overdue pieces

DM each author about their upcoming/overdue pieces

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

STEP 5

Post daily content pipeline summary to #content channel

Post daily content pipeline summary to #content channel

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

STEP 6

Update status for items that were published

Update status for items that were published

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

🤖 Example Agent Prompt

Interact with the Notion database using the Notion API.

POST https://api.notion.com/v1/pages (to create)
POST https://api.notion.com/v1/databases/{db_id}/query (to query)
Headers: Authorization: Bearer {NOTION_TOKEN}, Notion-Version: 2022-06-28, Content-Type: application/json

For creating pages: structure properties to match the database schema.
For querying: use filters and sorts to get relevant entries.
Handle rich text by wrapping content in the proper block format.

If the API returns 429 (rate limited), wait 1 second and retry. Max 3 retries.

Copy this prompt into your agent to get started.

⏰ Automation Ideas

• 0 9 * * 1-5