​Hi ​@CarbonNick 

I’ve seen other users mention issues with Notion Zaps today.

I recommend opening a ticket with Zapier Support: https://zapier.com/app/get-help

​@CarbonNick 

TIP:

• Make sure you are using the updated Notion Zap app integration version: 2.20.0
• Make sure you are using a Notion app account connection that is for the Notion Zap app integration version: 2.20.0
• Make sure you are using both of these in the Notion Zap step

Hey ​@CarbonNick,

Can you share screenshots of Data In and Data Out as well as how each Zap step is configured to have more context?

You may want to delete your existing connection and reconnecting it again so it defaults to latest version of Notion that is v2.20.0. After that, configure the fields again and try clicking on the Retest step to see if it fixes it. Hope it helps!

Thanks all. I raised a ticket with Zapier support and they are investigating. They identified the issue as: 

“a bug where the Update Database Item step in Notion only shows a single field called contents after refreshing fields, and attempts to update other properties fail with the error “Cannot read properties of undefined.” It should instead display all of the editable properties from your Notion database so you can map and update them successfully.”

They are investigating why the editable properties from Notion are not being displayed by the Zapier function. Will update. 
 

Hey ​@CarbonNick, actually, don’t upgrade your Notion integration to the latest version, as it doesn’t work for creating or updating items in multi-source databases. Unless you haven’t yet converted any of your databases to multi-source, in which case it’s fine.

The issue is that, starting with API version `2025-09-03`, API requests need to specify a `data_source_id`, as the `database_id` alone is not sufficient when a single database has multiple databases nested inside it. So if you’ve converted any of your Notion databases already, just keep your Zapier integration on a legacy version for now (you may need to roll updated Zaps back to an earlier version if you’ve already updated them).

Alternatively, while Zapier works on a fix for this breaking change, I built a Custom Agent to allow me to update one particular database that I already upgraded, and set a few property values (including a Relation type property, which the older versions of the Notion integration don’t allow you to update). Creating a Custom Action is a bit fussy because you have to update the JSON to match the schema of the data source you want to work with, but I’m using this for now while I wait for the official fix, which is supposed to be coming next week.

export async function createNotionPage({
  internalAttendees,
  startDate,
  endDate,
  googleCalendarEventId,
  clayContacts,
  description,
  callLink,
  title,
  markdownContent
}: {
  internalAttendees: string;
  startDate: string;
  endDate: string;
  googleCalendarEventId: string;
  clayContacts: string;
  description?: string; // Optional
  callLink?: string;    // Optional
  title: string;
  markdownContent?: string; // Optional markdown content
}): Promise<{ result: object }> {
  // Convert the comma-separated string of user IDs into an array
  const attendeesArray = internalAttendees.split(',').map(id => id.trim());

  // Convert the comma-separated string of page IDs into an array for Clay Contacts
  const clayContactsArray = clayContacts.split(',').map(id => id.trim());

  // Construct the request body with the provided inputs
  const requestBody: any = {
    parent: { data_source_id: "19891b07-11ac-8137-9d62-000b75fab86e" },
    properties: {
      "Internal Attendees": {
        people: attendeesArray.map(id => ({ object: "user", id }))
      },
      "Date": {
        date: { start: startDate, end: endDate }
      },
      "Google Calendar Event ID": {
        rich_text: [{ type: "text", text: { content: googleCalendarEventId } }]
      },
      "Clay Contacts": {
        relation: clayContactsArray.map(id => ({ id }))
      },
      "Title": {
        title: [{ type: "text", text: { content: title } }]
      }
    },
    children: [] // Initialize children for markdown content
  };

  // Add optional properties if they are provided
  if (description) {
    requestBody.properties["Description"] = {
      rich_text: [{ type: "text", text: { content: description } }]
    };
  }

  if (callLink) {
    requestBody.properties["Call Link"] = {
      url: callLink
    };
  }

  // Add markdown content if provided
  if (markdownContent) {
    // Split markdown content into lines and create paragraph blocks
    const markdownLines = markdownContent.split('\n');
    requestBody.children = markdownLines.map(line => ({
      object: "block",
      type: "paragraph",
      paragraph: {
        rich_text: [{ type: "text", text: { content: line } }]
      }
    }));
  }

  // Make the API request to create a page in Notion
  const response = await fetchWithZapier("https://api.notion.com/v1/pages/", {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "Notion-Version": "2025-09-03"
    },
    body: JSON.stringify(requestBody)
  });

  // Throw an error if the response is not ok
  await response.throwErrorIfNotOk();

  // Return the response as a result object
  return { result: await response.json() };
}

Hi ​@CarbonNick,

Ali here from Zapier support. It seems you might be coming across a recently reported bug with the Notion app.

I would recommend reaching out to our support team so they can specifically review your Zap and once they can confirm it is a bug, they can add you to our bug tracker so you can be notified as soon a fix is launched.

Thank you,

Now, are you too gonna switch to the new Notion API?

Hey folks 👋

I just came across this and looked up the bug report that the Support team logged (and added ​@CarbonNick to). Really sorry about the impact and disruption this bug is causing everyone. At this time, there’s no new status update, but I know the team are actively working on the issues that have surfaced following the recent changes to Notion’s API.

Big thank you to ​@DennisWF for posting that workaround - it’s really helpful. 🤗 I’ve added both you and ​@LannyAva to the list of affected users so we can keep you directly in the loop. We’ll reach out via email once there’s a resolution, and I’ll be sure to post updates here as they become available.

Thanks for everyone’s continued patience in the meantime. Hopefully this will be resolved soon 🙏

Hi folks! I got a notification stating that the bug was resolved with an update that just shipped, but I’m still seeing the issue, and I think I know why.

Root Cause

The integration is sending API requests with database_id instead of data_source_id when working with multi-source databases. This stems from changes in Notion's 2025-09-03 API version that introduced multi-source database support.

Technical Details

• The action correctly identifies and displays data sources in the configuration UI
• However, the actual API call uses the wrong parameter format
• Current (broken): parent: { database_id: "xxx" }
• Should be: parent: { data_source_id: "xxx" }

• You can tell this by the error message in the API response, which indicates that the integration is attempting to send a data_source_id as a database_id:

Impact

• Cannot create new items in affected databases using the native integration
• Forces users to either roll back to older integration versions or build custom API actions
• Prevents access to new features like relation property updates

Workarounds

1. Use older versions of the Notion integration (v2.14.5 works, as long as you haven’t converted any of your databases to use multiple data sources)
2. Create custom API actions using the correct data_source_id parameter
3. Duplicate existing Zaps that still use older integration versions

Status

Zapier engineering team has acknowledged the issue and released what they claim is a fix, but the problem persists as of 30 September 2025. The fix appears incomplete—while they renamed the action to "Create Data Source Item," and the Configuration flow displays data_source_id values when selecting a data source, the API request it sends still uses the wrong parameter structure. I’ve notified the support team with my suggested fix.

Within this week please...

Thanks for sharing that info and those potential workarounds here ​@DennisWF! I checked on the bug report you’re right it did get closed and as you’ve noted, there’s an issue relating to the data sources that’s affecting things still. The engineering team are aware of this and are working on rolling out a fix for that as well.

I can’t give any confirmation of whether it will be resolved by end of this week, ​@LannyAva but I’ll definitely follow up here with any further updates. 

I can confirm that the issue is resolved on my end.

Had to reset the trigger and the problematic steps to get everything working again.

Thanks so much for confirming that things are resolved on your side ​@CarbonNick 🤗 I’ve just checked on this end and our engineers recently rolled out a new version of the Notion app, and it sounds like that’s helped to sort things in your case. 🎉

​@LannyAva and ​@DennisWF - are you still getting any errors on your end? 🤞 

​@SamB I appreciate your support with this and I know you’re just the messenger. 

I have to say that I agree with some other people on this thread in that this is a huge issue. I run a Notion & automations consulting firm and all of my work has been put on pause, and all of my clients’ work has been put on pause. 

The single source workaround is not working for me, as none of my databases are multi-source in the first place.

This change was known to be happening for quite a long time before it became an issue, and other automation platforms like Make.com and N8N were more on top of this and even sent out notices letting people know in an advance they may need to reset their automations. 

I don’t want to switch because I prefer Zapier as a platform, but if we’re unable to get some kind of decent resolution soon it’s starting to feel like I don’t have a choice. I also feel like some kind of courtesy compensation for myself and my clients is appropriate. We use Zapier almost exclusively for Notion use cases. As it stands, we’re paying for a tool we literally can’t use until the engineering team rolls out a fix. 

​@SamB it looks like it’s finally working for me! Thanks for keeping us posted throughout this issue.

I have to agree with ​@alvinliang - it’s disappointing how the team appears to have been caught flat-footed on this breaking change in Notion’s API, since Notion started communicating about the change well before it shipped. I imagine Notion must be one of the most widely-used Zapier integrations, so I hope there are plans for some sort of retro to better understand how this was missed and how a similar situation can be prevented in the future.

Thank you for sharing your candid feedback here ​@alvinliang. I completely understand how disruptive this has been for you and your clients, since your business relies heavily on Notion automations. We typically don’t offer refunds due to bugs or disruptions, unfortunately. I know this situation is far from ideal and I’ll be sharing your feedback with our team, especially your point about how other platforms handled similar changes. We want to do better here.

​@DennisWF - that’s great news! I’m so pleased to hear it’s working again for you. We don’t usually share retros for bugs publicly, but I’ll be sure to give this suggestion to the team for consideration. I haven’t seen any official confirmation yet that all issues are fully resolved but I’ll continue to keep this thread updated as soon as I hear any news from engineering. Really appreciate everyone’s patience here.

Thanks, ​@SamB, for keeping us posted throughout. And I didn’t mean to suggest that the retro should be shared publicly. I know that would be super weird. I was just stressing that there should be one, but I’m sure that’s standard procedure anyway, so I was probably just venting 😂. In any case, I think our long international nightmare is finally over!

“What if it’s not” scares 😬

Just created an account to add that the problem was partially fixed today. I can now do a bit of stuff, but it seems that Zapier are kinda spamming Notion’s API at the moment and I often get 401 errors in my zaps. 

It would be nice if the Zapier team and Notion team could work it out together rapidly, it’s going in the right direction but it’s a major disruption of our workflows. And Make have indeed made it work flawlessly already with the new API version. 

Please keep us posted everyday. 

Hi ​@SamB I wanted to add here that we are still unable to get mission critical processes running on the Zapier platform. We currently have 28 zaps affected by this bug, all of which have been down for about a week and half now. 

We are unable to load the Notion app at this point. We’ve tried moving to the new version, reconnecting the app, and we’ve tried building new zaps and starting from scratch but that doesn’t solve the issue either. (The potentiality of having to rebuild all these zaps is far from ideal, btw.) We do not have a dedicated CSM because we are not Ent customers, but I’m having trouble justifying the jump to Ent given the current situation. 

We’re still very much underwater and I’m concerned that the fixes above have not worked for us. Any chance we could get a support call to help us out?

​@AnthonyOrtega basically what I believe is happening is that they can’t communicate efficiently with notion, so when you’re trying to access a large database or whatever, the request gets either stuck or is being shut down by Notion before they get the fields or can push new ones etc. 

I believe you simply have to wait for them to cache all the shit that they’d left behind because they didn’t switch soon enough to the new version. I do believe that it’s the “catching up” that is creating problems (too many requests or too much cache to build or whatever). 

I’ve had the same problem as you, at some point you get a CloudFare error : they’re probably exceeding the rates at which they can speak to Notion. I’m pretty sure they’ll get there at some point, but it does suck that we our work is being penalized by a lack of planning / anticipation on the Zapier side : we’re literally paying so that we don’t have to maintain the API connections ourselves. 

Oof, this is rough. I haven’t observed this error with fetching the data source properties yet, but I’ll keep an eye out. Just out of curiosity, how large are the databases you guys are seeing this with?

​@DennisWF : large for some, smaller for others, I don’t know how this is managed on your side but I saw that a new version shipped between last night and now. Still having problems with the new one. I believe this should be escalated. 

Hmm, wonder why I’m not seeing it - I have tons of Zaps running with Notion DBs. Anyway, I know ​@SamB is watching this ticket closely (I don’t work for Zapier), so hopefully this does get escalated if it’s still affecting folks. 

Hi ​@SamB I wanted to add here that we are still unable to get mission critical processes running on the Zapier platform. We currently have 28 zaps affected by this bug, all of which have been down for about a week and half now. 

We are unable to load the Notion app at this point. We’ve tried moving to the new version, reconnecting the app, and we’ve tried building new zaps and starting from scratch but that doesn’t solve the issue either. (The potentiality of having to rebuild all these zaps is far from ideal, btw.) We do not have a dedicated CSM because we are not Ent customers, but I’m having trouble justifying the jump to Ent given the current situation. 

We’re still very much underwater and I’m concerned that the fixes above have not worked for us. Any chance we could get a support call to help us out?

We encounter exactly the same situation, this is affecting all our main zaps and affecting hundreds of our customers in our main database. We really need a fix...