Email address encoding issues when creating new database items in Notion

Question

I have a Zap that creates new records in a Notion database for every Google Calendar event that matches certain criteria. I am having difficulty correctly adding data to the Content field of the Create Database Item in Notion action.

In particular, if the content includes an email address, these seem to be replaced with unicode encoded content. For example, example@email.com shows up as:

support@zapier.com

I’ve used a Python step to try various encodings as well as playing with Markdown formatting, none of which end up simply writing out the email address into the text of the created page.

Below are a set of examples of what I have tried and haven’t worked. Any suggestions on how to debug this further?

Thanks!

These show up encoded as described above:

example@email.com

(example@email.com)

<example@email.com>

[example@email.com]

These show up as is (not encoded, but not formatted as an email address either)

example%40email.com

example @ email.com

example\@email.com

example\\@email.com

`example@email.com`

``example@email.com``

```example@email.com```

This post has been edited by a moderator to remove sensitive information. Please remember to not share any personally identifiable information when posting as this is a public forum.

icon

Best answer by SamB 21 March 2022, 12:57

View original

SamB · Accepted Answer

Hey there @Ar3m3f!It appears you’ve run into a bug with the Notion integration that was recently discovered. I’ve added you to the list of affected users so as soon as it’s been resolved we’ll contact you right away!That said, I’ve done some testing and it seems that the Update Database Itemaction can correct thisencoding issue for email addresses. So if the Create Database item includesan email it will be displayed like this:But if we then add a Update Database Item action (and use the Custom value option to select the ID field from the previousCreate Database itemaction):It will then update the item and display the email address correctly:I know it’s not a super ideal workaroundas it wouldincuran extra task when the Zap runs, but may be worth using while this bug is still causing issues for the Create Database item action.Hopefully the above suggestionhelps to keep things running for you in the meantime!

Ar3m3f · Answer

Thanks @samB I can confirm this work around corrects the issue, albeit requiring consumption of 2x the number of tasks for each run. Any idea when the bug itself will be fixed?

Sign up

Use your Zapier credentials

Log in to the Community

Use your Zapier credentials

Scanning file for viruses.

This file cannot be downloaded