---
name: Career Ops Notion Plugin
slug: career-ops-notion-plugin-2
category: Automation
description: Career Ops Notion Plugin mirrors the career-ops application tracker to a Notion database and reads matching records back as job leads. Use it to export tracker rows or search Notion for lead URLs.
github: "https://github.com/career-ops-hq/career-ops/tree/main/plugins/notion"
language: JavaScript
stars: 69952
forks: 13232
install: "npx degit https://github.com/career-ops-hq/career-ops/tree/main/plugins/notion ~/.claude/skills/notion"
installs_to: ~/.claude/skills/notion
source_path: plugins/notion/skill.md
collection_size: 8
category_size: 1754
collection_url: "https://dirskills.com/collections/career-ops-hq/career-ops"
added: 2026-09-03T06:03:12.111Z
last_synced: 2026-09-03T06:03:12.111Z
canonical_url: "https://dirskills.com/skills/career-ops-notion-plugin-2"
---

# Career Ops Notion Plugin

Career Ops Notion Plugin mirrors the career-ops application tracker to a Notion database and reads matching records back as job leads. Use it to export tracker rows or search Notion for lead URLs.

**Install:**

```bash
npx degit https://github.com/career-ops-hq/career-ops/tree/main/plugins/notion ~/.claude/skills/notion
```

## README

# notion plugin

Mirrors your application tracker to a Notion database (export) and reads records
back into the pipeline (search). `data/applications.md` stays the source of
truth — Notion is an additive mirror.

## Commands

- `node plugins.mjs run notion export` — push each tracker row (company / role /
  status / score) to the "Applications" database under your Career Ops page.
  Add `--dry-run` to preview without writing.
- `node plugins.mjs run notion search "<query>"` — return Notion records that
  carry a job URL, matching the query, and append them to the pipeline.

## Setup

A "Career Ops" parent page in Notion containing an "Applications" database with
Company / Role / Status / Score / URL properties, shared with your internal
integration. Put `NOTION_ACCESS_TOKEN` + `NOTION_PARENT_PAGE_ID` in `.env`.

## Data it produces

`search` returns `Job[]` ({ title, url, company, location }) for records that
have a job URL; the engine writes them to the pipeline. `export` returns
{ pushed: N } — it never writes local files.