Failed to create a Notion page error

Hey there!

I am getting the following message when pulling an Upwork Job into Notion:

“Failed to create a Notion page. Notion API failed to create a page in database 0974a54525bf4b3595138b3a23621895. Please check sharing settings in Notion and make sure that Bardeen has access to the database and pages you are trying to work with”

I made sure Bardeen is properly connected to Notion and has access to the pages I want to insert the data.

Any idea what may be still causing this issue?

Thanks,
Felix

1 Like

Hi Felix!

Would you be able to share the detailed error? You can get it from the Activities dropdown next to your avatar (top right), and then going in the Errors tab.
You can either send a crash report (using the little paper airplane icon) and then paste the report code here, or directly copy-paste the error details.

Thanks!

1 Like

Thanks for your help! Here I share the error details:

{
“clientErrorCode”: “NotionCreatePageError”,
“userHint”: “Notion API failed to create a page in database 0974a54525bf4b3595138b3a23621895. Please check sharing settings in Notion and make sure that Bardeen has access to the database and pages you are trying to work with.”,
“trackError”: “default”,
“clientErrorHistory”: [
{
“clientErrorCode”: “NotionCreatePageError”,
“clientErrorDetails”: {
“databaseId”: “0974a54525bf4b3595138b3a23621895”
},
“message”: “Failed to create a Notion page.”,
“stack”: “Error: Failed to create a Notion page.\n at o.from (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/background.js:70:12758)\n at Object.from (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/background.js:77:4365)\n at pN.addPage (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:55:45696)\n at async Promise.all (index 0)\n at async hA.handle (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:55:76972)\n at async chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:86750\n at async by.invokeFunction (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:86558)\n at async by.invokeSequence (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:77953)\n at async by.invokePlaybook (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:79452)\n at async Zw.execute (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:96941)\n at async Zw.executeWithResult (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/136.js:389:97496)”,
“userHint”: “Notion API failed to create a page in database 0974a54525bf4b3595138b3a23621895. Please check sharing settings in Notion and make sure that Bardeen has access to the database and pages you are trying to work with.”,
“fingerprint”: [
“NotionCreatePageError”
]
},
{
“clientErrorCode”: “Notion add page: object_not_found (404)”,
“clientErrorDetails”: {
“type”: “ApiError”,
“code”: “object_not_found”,
“module”: “Notion”,
“operation”: “add page”,
“message”: “Notion failed to add page: Could not find database with ID: 0974a545-25bf-4b35-9513-8b3a23621895. Make sure the relevant pages and databases are shared with your integration. (404)”,
“raw”: {
“body”: {
“object”: “error”,
“status”: 404,
“code”: “object_not_found”,
“message”: “Could not find database with ID: 0974a545-25bf-4b35-9513-8b3a23621895. Make sure the relevant pages and databases are shared with your integration.”
}
},
“status”: 404,
“headers”: {
“cf-cache-status”: “DYNAMIC”,
“cf-ray”: “7e291af35adf2f8f-MAD”,
“content-encoding”: “gzip”,
“content-type”: “application/json; charset=utf-8”,
“date”: “Thu, 06 Jul 2023 16:08:16 GMT”,
“etag”: “W/"d9-zdCnpZ8Ocj3kg+F2OzMbchBKXp8"”,
“server”: “cloudflare”,
“vary”: “Accept-Encoding”,
“x-powered-by”: “Express”
}
},
“fingerprint”: [
“Notion add page: object_not_found (404)”
],
“message”: “Notion failed to add page: Could not find database with ID: 0974a545-25bf-4b35-9513-8b3a23621895. Make sure the relevant pages and databases are shared with your integration. (404)”,
“userHint”: “A request to the service API failed. Please check the error details”
}
],
“fingerprint”: [
“NotionCreatePageError”,
“Notion add page: object_not_found (404)”
]
}

Thanks. I’m going to report this internally. We’ll debug it further, and I will let you know when we have any update.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.