Notion rebuilds synced databases, starting with GitHub, Jira and Salesforce

What changed

Synced databases bring records from another tool into Notion as a live database. In Notion 3.8 they were rebuilt, launching first with GitHub, Jira and Salesforce:

• Faster, more reliable syncing.
• Live health status for each sync, so you can see when one is failing.
• Your own properties on top of synced records.
• Views and automations on synced data, including triggering Notion automations.

Why it matters

Older synced databases were read-mostly mirrors. Being able to add properties and fire automations turns them into working surfaces: a PM can triage Jira issues with a Notion-only "Priority this week" property, or an account team can annotate Salesforce opportunities without touching Salesforce.

Combined with Custom Agents, synced data is also agent context. An agent can read synced Salesforce opportunities and the related account notes in Notion in one pass.

Practical setups

1. Engineering: sync GitHub pull requests, add a "Release" relation, and build a release notes view.
2. Product: sync Jira issues, add a Notion-only priority and an automation that pings the owner when status changes.
3. Sales: sync Salesforce opportunities and relate them to account pages with meeting notes.

Frequently asked questions

Which tools support Notion's rebuilt synced databases?

At launch on October 13, 2026: GitHub, Jira and Salesforce.

Can you add properties to a synced database in Notion?

Yes. The rebuilt synced databases let you add your own properties, create views and trigger automations.

How do I know if a Notion sync is broken?

Each rebuilt synced database shows a live health status for its sync.

Sources

• Notion 3.8 release notes (Oct 13, 2026)