How we handle GDPR data-subject requests on a deadline
Legal
The social-scheduler agent we run on Kortix — a daily agent that reads our Notion content calendar, drafts platform-appropriate posts for upcoming content, launches, and announcements, and holds them in Slack with the scheduled date for a human to approve and publish.
Our content calendar lives in Notion: what's shipping, what's launching, what we're announcing, and when. Turning each of those rows into an actual LinkedIn post, a tweet, and an Instagram caption is a separate manual step that happens later, usually the day of, sometimes not at all. The calendar says what should go out; nobody had turned it into copy yet.
We run a social-scheduler agent on Kortix that closes that gap every day. It reads the content calendar in Notion, drafts platform-appropriate posts for anything launching or publishing soon, and holds every draft in our marketing Slack channel with its scheduled date. It never posts anywhere itself — a person reviews, edits, and publishes.
A content calendar tells you what and when, not the actual words that go on each platform. Writing the LinkedIn version, the X version, and the Instagram caption for every launch and announcement is a distinct task that someone has to remember to do, usually under time pressure right before the scheduled date.
The common fixes don't hold up. A scheduling tool queues posts, but someone still has to write them first. A shared doc of "posts to write" depends on someone checking it daily and drafting ahead of the date, not the day of. And because drafting keeps sliding to "later," launches and announcements regularly go out with no social post at all, or one written in five minutes right before it's needed.
On Kortix, a daily cron triggers an agent. It spawns a fresh session that reads our Notion content calendar for anything launching, publishing, or being announced in the days just ahead, drafts a platform-appropriate post for each one — LinkedIn, X, and Instagram get different lengths, tone, and structure — and posts the batch to our marketing Slack channel, each draft labeled with its scheduled date. Nothing is scheduled or published automatically; the drafts sit in Slack until someone approves them.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the drafting skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily social post drafting agent in this workspace.
Create the agent agents/social-scheduler.md. Its job is to draft social posts from our Notion content calendar. It may use the Notion connector and post to Slack. It has no connector to any social account.
Create the skill skills/social-post-drafting/SKILL.md with these rules:
Add a cron trigger daily-social-draft to kortix.yaml. It runs the social-scheduler agent every day at 07:00 with the prompt "Load the social-post-drafting skill and draft posts for every Content Calendar entry in the next 7 days."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your content calendar and Slack. Do not connect any social account: the agent drafts, and a person publishes. Credentials are brokered server-side and never enter the agent's machine.
Reads upcoming content calendar entries and their briefs.


Supplies linked briefs and assets for richer drafts.
Holds each batch of drafts in the approval channel.
Merge the change request, then start a session with the social-scheduler agent and send this prompt. Read the drafts against your own voice before you let the schedule take over.
Run one draft pass on the Content Calendar database in Notion.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: daily-social-draft name: Daily social post drafting on: cron: "0 0 7 * * *" run: agent: social-scheduler prompt: Load the social-post-drafting skill and draft posts for every Content Calendar entry in the next 7 days.The agent has no connector to LinkedIn, X, Instagram or any other social account, so it cannot publish. Its only write to Notion is the Kortix Drafted checkbox. A person reviews each draft in Slack, edits it and publishes it with the tool the team already uses.
Each run ends with one message in #marketing. This is what a run looks like in the session:
Found 4 entries in the next 7 days and drafted 9 posts for 3 of them. Skipped 1 entry with no brief. The drafts are in #marketing with their scheduled dates.
Once it works, paste any of these into the same session.
For each entry, also draft a two-sentence blurb for our weekly newsletter, in the same batch.
Read the published posts I paste here and update the skill's tone rules so new drafts match them.
If no entry is scheduled in the next 7 days, post a short note to #marketing instead of staying silent.
The agent drafts copy that will eventually represent the company publicly, so what it can do on its own is narrow:
Launches and announcements that used to get a rushed post the day of, or none at all, now show up in Slack days ahead with a draft ready for each platform. The agent turns the calendar into copy; the team still decides what actually goes out.