Integrations · Notion

Clipy for Notion: publish screen recordings as Notion pages

Notion is where many teams keep their docs, specs and bug databases. Clipy writes the recording into Notion as a readable page, with the moments that matter as images, or as a row in the database your team already triages from.

Quick answer

Clipy publishes a screen recording to Notion as a page or a database row: connect Notion once and share the pages and databases Clipy may use, then choose Copy for agents → Publish to Notion on a recording you own. It carries the AI summary, key points, action items, key-moment screenshots, errors and an agent-context link.

What Clipy creates

Clipy creates a Notion page under the parent you pick, or a row in a database you pick. It contains:

  • The recording title (editable before sending) and an optional note you add.
  • The watch link, which plays for anyone the recording is shared with.
  • The agent-context link (the same URL ending in .arec), with one sentence telling coding agents what it holds.
  • The AI summary and the requested changes it found (a checklist on Linear and ClickUp, subtasks on Asana, a list on Jira, monday.com, Confluence and Notion).
  • Up to 8 key moments, each with a link that opens the video at that second (frames are embedded as images on Confluence and Notion pages).
  • Up to 15 captured problems when the recording has browser evidence (the Chrome extension's opt-in console and network capture, or a browser Clipy drove): uncaught errors, console errors and failed network requests.
  • The environment from the same capture: page, browser, OS, window size, language and time zone.

Set it up

  1. Open Settings → Integrations in Clipy and choose Connect Notion. Approve the consent screen and pick the pages and databases Clipy may use.
  2. On a recording you own, open Copy for agents → Publish to Notion.
  3. Pick the parent page or database, adjust the title and publish. Clipy shows a link to the new page.

Let an agent file it

Once you have connected Notion, an agent with write access can send a recording for you. On Clipy's hosted MCP server the tools are list_integrations, list_integration_targets and send_recording_to_integration. Over REST, with an API key:

# 1. Which tools are connected?
curl -H "Authorization: Bearer $CLIPY_API_KEY" https://clipy.online/api/v1/integrations

# 2. Where can it go?
curl -H "Authorization: Bearer $CLIPY_API_KEY" https://clipy.online/api/v1/integrations/notion/targets

# 3. Send it (needs a key with recordings:write)
curl -X POST https://clipy.online/api/v1/recordings/<recording-id>/send \
  -H "Authorization: Bearer $CLIPY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"destination":"notion","targetId":"<id from step 2>","requestKey":"<uuid>"}'

A repeated requestKey returns the item already created instead of a duplicate. See the MCP guide and the REST API.

Permissions and privacy

  • Clipy only sees the pages and databases you share with it on the Notion consent screen.
  • Clipy creates pages and database rows. It never edits, moves or deletes existing Notion content.
  • Key-moment images load from Clipy's CDN, so they add nothing to your Notion storage. Disconnecting in Clipy deletes the token; you can also remove Clipy under Notion → Settings → Connections.

Good to know

  • In a database, Clipy fills the title and writes the report into the page body; other properties follow the database's defaults.
  • Frames load from Clipy's CDN, and each moment heading links to that second of the video.
  • The recording's owner sends it, so every issue, task, item or page comes from the person who recorded it. Workspace members open the links.
  • It links to the recording, so the video keeps the recording's own sharing setting: a private recording opens only for people it is shared with. The summary, key-moment captions, frame links and errors are written into it, so anyone who can see it in that tool can read them.
  • Each send is a snapshot of the recording at that moment.

Questions

Can I turn every recording into a Notion doc automatically?
Yes. An agent connected to Clipy's MCP server with write access can call send_recording_to_integration with destination notion, and a webhook on summary.ready can trigger that from your own automation.
Can AI agents read the recording from the page?
Yes. The page carries the summary, key moments and the recording's .arec link, which any agent can open for the full transcript and evidence.

See every tool Clipy works with on the integrations page.