Mirror a planner database into Notion

Connect a planner database to a Notion page, understand which side is authoritative, and disconnect a single mirror without removing Notion entirely.

The planner can mirror a database into a Notion page so your team can work in either place. This is currently the most complete Notion integration in the product — other Notion features are lighter-touch by comparison.

Before you start

You need a Notion connection on the active account. If you have not connected Notion yet, follow Connect Notion first. The planner uses your existing Notion connection, so you only authorize Notion once per Instagram account.

Set up the mirror

Open the planner database you want to mirror.
Click the Notion sync button in the planner toolbar.
Pick a Notion parent page — the place inside your Notion workspace where Wysestats should create the mirrored database. You can search by page title or paste a Notion page URL.
Confirm and click Create Notion database.

Wysestats creates a fresh database inside that Notion page, copies your existing planner rows into it, and starts keeping the two sides in sync. You will see a toast confirming the connection and an initial sync running in the background.

Which side is authoritative

The planner inside Wysestats is authoritative for this database. When the same row is changed in both places, the Wysestats version wins. This keeps the planner's read model — what filters and views inside the app use — consistent with what reports and other features rely on.

In practice this means:

New rows added inside Wysestats appear in Notion shortly after.
Edits made in Notion are mirrored back into Wysestats. If the same row is changed in both places before the next sync runs, Wysestats keeps its version of that row and the Notion edit is discarded.
Deleting a row inside Wysestats removes it from the Notion mirror. Deleting or archiving the matching page inside Notion archives the row in Wysestats.

Conflicts are resolved at the row level, not field by field — if any part of a row changes on both sides between syncs, the whole Wysestats row wins. To avoid surprises when working with a teammate, treat the planner as the primary editing surface and Notion as a reference and lightweight-edit view.

What is mirrored:

Rows, including title, dates, status, and the values of supported columns.
Column structure (renames, additions, removals on the Wysestats side).

What is not mirrored:

Computed columns and post-preview cells stay inside Wysestats — they are derived from data the planner owns.
Comments left inside the Notion mirror are not pulled back.

Manage the mirror

Reopen the Notion sync dialog from the planner toolbar at any time. You will see the connection status, the parent page it lives under, and when the last sync finished. From here you can:

Reconnect if Notion access expired.
Disconnect the mirror for this single database — the Notion page itself stays where it is, with whatever content is currently in it. The Wysestats side stops pushing or pulling changes.

Disconnecting one planner database does not remove the broader Notion connection on your account. To remove Notion entirely from the active account, do that from your account's connection settings — see Connect Notion for how those connections are managed.

When something looks off

If the connection card shows a red Needs attention badge, the most recent sync attempt failed. The card includes a short message about the failure. The most common cause is that someone removed Wysestats's access to the parent page inside Notion. Reconnecting from the same dialog will restart the flow and re-establish access.

For more recovery steps, see Notion sync issues.