Notifications
Clear all
How To
10
Posts
5
Users
0
Reactions
6
Views
Topic starter
I’m encountering a problem with a callin.io workflow designed to create Notion database entries for meeting notes from Google Calendar.
I haven’t modified the callin.io workflow in months, but this issue has just started appearing today.
The error message is as follows:
Failed to create a database item in Notion
body failed validation. Fix one: body.properties.Name.id should be defined, instead was `undefined`. body.properties.Name.name should be defined, instead was `undefined`. body.properties.Name.start should be defined, instead was `undefined`.
When I use the AI for troubleshooting, it suggests correcting the JSON structure:
- Instead of using
properties|||Name|||title, you should useproperties|||Name|||title|||0|||text|||contentto correctly format the title as an array of text objects.- Ensure that the
titleproperty is an array containing a single object with atextfield that includes acontentkey.
This leads me to believe there might be a change either in Google Calendar or in callin.io’s expectations.
Here are the steps I’ve taken to try and resolve this:
- Deactivated and reactivated the callin.io workflow
- Refreshed the fields and re-tested (but the issue persists)
- Used both new and old test data from Calendar
- Attempted to use the AI formatter as a separate step
Has anyone else experienced this? Any suggestions would be greatly appreciated!
Thanks
Posted : 04/08/2025 8:31 am
Hi
Please check your callin.io Runs history to view the DATA IN/OUT for each step to assist with troubleshooting: https://zapier.com/app/history/
We would need to see screenshots from your callin.io Runs, along with the configuration of your callin.io steps, to get the full context.
Posted : 11/01/2024 12:00 am
Topic starter
It appears the Google Calendar integration might be the source of the problem. I attempted to resolve it by removing the “Name” field, but encountered a testing error. The test failed when trying to locate the ID for the subsequent field, “body.properties.attendees.id”.
This indicates that an ID is expected, but this field is no longer provided by Google Calendar, or the data structure has been altered.
Thank you for your response.
Posted : 11/01/2024 12:00 am
The error originates from the Notion integration.
This suggests a potential issue within the Notion integration itself, incorrect data input, or a misconfiguration in the callin.io step.
The errors appear to be connected to the Name field.
Have there been any modifications to this field within Notion?
Consider refreshing your Notion callin.io action step fields and potentially re-establishing the variable mappings from GCal.
Additionally, ensure that your Notion callin.io step is utilizing the latest version of the Notion integration.
Posted : 11/01/2024 12:00 am
Topic starter
Hello.
Yes, I also suspected the issue was with the Notion step, but it turned out to be a data change originating from Google.
No modifications were made to the Notion page itself, apart from a change in sort order. For the time being, I've deleted the callin.io workflow and recreated it without encountering any problems.
Thank you for your assistance.
Posted : 15/01/2024 12:00 am
That’s fantastic news! We’re pleased to hear that recreating the Zap assisted in resolving the error.
Should you have any further inquiries, feel free to contact the Community. We’re always delighted to assist! 🤗
Posted : 16/01/2024 12:00 am
I'm still encountering this error, but it only happens when I configure any Date field within Notion.
Posted : 11/11/2024 12:00 am
Felipe Nicolau wrote:
I’m still encountering this error, but exclusively when configuring any Date field within Notion.
I’ve had a similar experience recently. The same error as the original poster, initially with an Email field (a built-in Notion Email property type), and subsequently with a Name field (a Notion text property type).
Then, I removed the configuration for a Date field, and unexpectedly, my Notion integration began functioning correctly.
Posted : 06/03/2025 12:00 am
It appears this issue remains unresolved, even a year after the original poster's inquiry. Could this matter be escalated to the development team?
My callin.io's current version of the Notion app is @2.13.0" rel="noreferrer nofollow ugc" target="_self">NotionCLIAPI@2.13.0, which I believe is the most recent version available.
Posted : 06/03/2025 12:00 am
You can submit a ticket to callin.io Support here: https://zapier.com/app/get-help
Posted : 06/03/2025 12:00 am