Keep your shared Notion information up to date

A visible record may no longer be a current one

If your team uses Notion to follow work from another tool, check whether recent changes are still arriving. This is a useful habit for any shared tool, especially when people or AI helpers use that information to decide what happens next.

Notion says its older database connections for GitHub, Jira, Asana, and GitLab stopped updating on October 30. These connections copied records into Notion and kept them refreshed. The existing databases stay in Notion, but their information no longer refreshes through those older connections. The cutoff applies to those older database connections.

Read the announcement: Notion: Sync data from other tools to Notion.

Choose a replacement that fits your work

Notion now maintains replacement database connections for GitHub, Jira, and Salesforce. GitHub and Jira require a Business plan or the Mobile Business add-on. Salesforce requires an Enterprise plan. You also need access to the source information, and your organization may require an administrator to approve the connection.

For Asana and GitLab, Notion points to guides for building custom connections. Those involve software that your team needs to set up and maintain. If somebody is building this for you, ask who will look after it when permissions or the source tool change.

Treat the new connection as a fresh setup

The replacement connection creates new databases. Nothing moves from an older sync automatically. Keep the existing records while you work out what needs carrying over, including your own notes and the places where people link to that information.

These connections bring changes from the source tool into Notion. To change a copied value, edit it in the original tool. Updates run in the background and may take time, so a recent check does not guarantee that every change has arrived.

Check a simple example before sharing widely

Start with a harmless record that you are allowed to use for practice. The goal is to understand where the information comes from and whether the people using it can trust that it is current.

1. Identify whether your team uses one of the older connections.
2. Choose the replacement and check the required plan and permissions.
3. Compare one recent source change with the new Notion record.
4. Review the connection status and any instructions it gives you.
5. Check sharing permissions before inviting more people to the database.

Give the connection a clear owner

Notion warns that a person with access to a synced database may see records they cannot open in the source tool. Source permissions are not copied to each viewer in Notion. Review who can see the new database, rather than assuming access will match automatically.

For people learning to build with AI, this is practical experience worth having. A useful answer starts with suitable information. For a business commissioning a tool, ask who checks its connections and how people will know when information needs attention. That makes the handover clearer and gives your team a way to keep the tool useful.