Sync X (Twitter) Bookmarks to Notion Daily with AI Tags

Build me an agent workflow that turns my X (Twitter) bookmarks into an organized Notion knowledge base. The judgement on summarization, tag selection, category, and thread detection is what makes this an agent workflow rather than a code one.

Trigger: a cron schedule that runs every morning at 7am in my local timezone.

On each run, the agent should do the following:

1. Call X (Twitter) Get Bookmarks to fetch the authenticated user's currently saved bookmarks. Paginate through all results.

2. Call Notion Query a Data Source against my Bookmarks database to read the tweet URLs (or tweet IDs) that are already filed. Use this list to compute the set of new bookmarks that have not been processed yet. Do not reprocess bookmarks that already exist in Notion.

3. For each new bookmark, the agent should:

a. If the bookmark response is missing the full tweet text, author handle, or other context the agent needs, call X Get Tweet on the tweet ID to fetch the full body and author.

b. Write a one or two sentence summary of what the tweet actually says or argues.

c. Choose one or more topical tags from a short configurable list (default starter list: AI, startups, design, frameworks, research, marketing, engineering, personal). The list of tags should be easy for me to edit in the workflow instructions.

d. Pick exactly one Category from a fixed configurable list (default: How-to, Opinion, Resource, Announcement, Thread, Other).

e. Decide whether the tweet is part of a thread worth unrolling, and set a Thread boolean accordingly. Signals to use: the tweet replies to itself, is numbered (1/, 2/), or ends with 🧵.

4. Call Notion Create a Page in my Bookmarks database with these properties: Title (a short agent-written title, not the full tweet), Summary, Tags (multi-select), Category (select), Author (the author's @handle), Tweet URL, Saved Date (the bookmark or tweet timestamp), and Thread (checkbox).

5. In the page body, include two sections: the original tweet text exactly as posted, and a short Notes block where the agent can add why this is worth coming back to (one to three bullets is fine). If Thread is true, add a line that says 'Worth unrolling — open original for full thread.'

Error handling: if Get Tweet returns 404 (deleted) or 403 (restricted), still create the Notion page with whatever metadata is available from the bookmarks response, mark Category as Other, and note 'Original tweet no longer accessible' in the body.

Database assumption: I will share the existing Notion Bookmarks database ID and column schema when configuring the workflow. The agent should be tolerant of small column-name variations and ask me to confirm the mapping on first run if anything looks ambiguous.

Additional information

What does this prompt do?

Pulls your saved X bookmarks once a day so nothing slips through the cracks.
Reads each new bookmark and writes a one or two sentence summary, then tags the topic and category for you.
Flags long threads so you know which ones are worth coming back to and unrolling later.
Files every new bookmark as a fresh entry in your Notion database with the original post, author, and link preserved.

What do I need to use this?

An X account with at least a few bookmarks already saved.
A Notion workspace with a Bookmarks database, shared with your General Input connection.
A short list of topic tags and categories you want the agent to choose from.

How can I customize it?

Change the time of day, or run it weekly instead of daily if you bookmark less often.
Swap the tag and category lists for ones that match how you actually think about your reading.
Add extra Notion properties like reading status, priority, or a favorite toggle, and tell the agent how to fill them in.

Frequently asked questions

Will it duplicate bookmarks I already have in Notion?

No. Before adding anything, the agent checks your Notion database for the tweet link and skips bookmarks it has already filed.

Can it process bookmarks I saved months ago?

Yes. The first run will work through your existing bookmark list and file each one. After that, daily runs only pick up the new ones.

What happens with long threads?

The agent marks the Notion entry as a thread so you know there is more context to read. You can open the original on X whenever you want the full conversation.

Do I need to write any code?

No. Connect your X and Notion accounts once, point the agent at your Bookmarks database, and it handles the reading, tagging, and filing on its own.

Can I change the Notion fields it fills in?

Yes. Use your own database with whatever columns you already have, and tell the agent how to map summary, tags, author, and link in plain English.