What caused the JSON serialization and Notion database query errors in my recently duplicated Pipedream project?

This topic was automatically generated from Slack. You can find the original thread here.

Hi Pipedream team! Recently duplicated an old job that was/is using the Notion API. I’m getting errors that I wasn’t getting on the old workflow, I’m guessing maybe some change was made to the Notion integration. Here are the errors:

The first error is related to JSON serialization - seems like Pipedream is no longer wrapping strings with quotes. For example I’m getting errors like Unexpected token 'F', "Feature" is not valid JSON when I pass a custom expression directly as the value for an argument to Notion > Create page from database. Should I be wrapping custom expressions in quotes now? Seems kinda weird that we’d have to do that

Second error is when running the action Notion > Query database I’m seeing this._getNotionClient(...).databases.query is not a function. This seems like an issue with the underlying action code, as if the Notion sdk and action code are out of sync.

Would appreciate help/investigation into these two things, thanks!

Hey , thank you for reaching out.

In order for us to access your workflow, could you access your Pipedream Project > Settings > enable Give Pipedream Support Access option?

Getting the same Notion error

Done , let me know if you can access now. Appreciate the help!

Thanks , the root cause is recent changes in Notion SDK that Pipedream’s using. We’re actively working on this and will let you know as soon as possible.

Thanks for the update - that includes for the first issue right? I saw the issue opened for the second issue but would like to confirm whether the first issue shares the same root cause. Thanks!

Hey , yes it’s the second issue.

For the first issue, could you share the screenshot of your action configuration if possible?

Hmm ok I think it works once I wrap the value in quotes, so let’s ignore that for now. Do you have an ETA for the bug fix?

Our component dev is actively working on it now, should be available in the next few days :pray: