wrjlewis

I’m not sure what you mean by the new api. This isn’t using the public api.

Just to check, have you refreshed your cookie and space id? Has this workflow worked for you before?

The issue reported above, relating to changes on Notions side with their API has been fixed with v0.4.2 @mwpark2014 @Hurzt I also noticed that the subtitles in the search results do not appear now if you set isNavigableOnly to True, this is a change made on Notions side. For this reason I have set the parameter to default to False. You can still set this to True but you will lose subtitles in your Alfred search results. @JaredTorres

I’m on holiday so can’t look at this for a week, but I reckon notion have changed their api so we’ll need to update our integration.

I'm having the same issue, I suspect they've changed something on their side and I'll need to update the workflow appropriately

The nest step for this workflow should be implementing against the notion public API, which I don't think the library you linked does. Probably because the oAuth bit is complicated.

I can only presume this was a temporary error/change/something on notion's side. After logging into notion today, re-copying the cookie token, and trying again, its all working.

This error indicates that the response from Notion has changed. Indeed, after checking, notion has changed their response to the calls that the workflow makes. They are returning html and I can see "Please stand by, while we are checking your browser...". It appears Notion is trying to stop automated access to their app, that isn't via their API. This could be a problem for this workflow. I will need to see if there is anything I can do to get this to work again without going through their public API. Or I will need to implement calls to their API properly, but since this involves oAuth, it's quite complex and difficult to do that, in a workflow that doesn't exist as a traditional webapp. This is not good news..

Excellent, is it working now?

Hi You’ll need a token_v2 value in the cookie, at the least. Can you try copying the cookie over again, or checking you have this in your cookie? Thanks

Hmmm this is interesting because a couple of people have reported this now. Can I check you have tried refreshing the cookie? Could you also try setting the env variable showRecentlyViewedPages to False and see if you can search afterwards? If that doesn’t work I think I’ll need to add some more logging of some kind, because I can’t replicate the error.

Hi Could anyone help me find workflows that have implemented some kind of OAuth integration? Notion's public API has got to a point where it is just about useable for what I need it to do, within the notion search workflow I've developed, and it would be great for users not to have to dig out their credentials and store them locally in the current methodology. I understand that implementing OAuth is complicated, even more so since workflows don't operate within a server environment. I imagine the only way to accomplish OAuth is to temporarily spin up a local server to receive the callback and access token, exchange it, and store it locally. Before I bury myself in potentially sub optimal approaches to this, do you know of any workflows that have OAuth integration already, that I could learn from? Or any tips/advice for someone seeking to do so? Thanks

New version (including a migration to Python3) available here: https://github.com/wrjlewis/notion-search-alfred-workflow/releases/latest/download/Notion.Search.alfredworkflow ** Recently Viewed Pages ** Your most recently viewed notion pages are shown when triggering the workflow. Simply type the 'ns' keyword to start the workflow, as you would before you search, and your most recently viewed notion pages are displayed. The workflow has been migrated to Python3 - ensuring compatibility with future versions of MacOS: "Python 2.7 was removed from macOS [12.3]. Developers should use Python 3 or an alternative language instead. (39795874)" Fixed issue with no results in certain circumstances with collections/dbs Fixed issue with null highlight on non-page elements - thanks to @ymszzq Fixed issue retrieving and displaying notion icons in results, due to change in internal notion APIs Fixed issue where externally hosted icons wouldn't show in results Slightly better error handling when no results are returned

interesting and thanks for raising. Is macOS 12.3 still in beta? I presume this is because python 2 is no longer shipped with Mac OS in this version as its deprecated. For the long term fix I’ll need to update the workflow to use python 3, but this is not shipped with Mac OS either as far as I’m aware and running python 3 in a terminal would prompt the user to install developer tools (containing python3). I need to investigate if that would mean the workflow wouldn’t work until a user did this, if anyone here knows please share? It would be great to have no additional steps when using this workflow. For a short term fix, install python 2 if possible.

Ok, in which case just add token_v2 at the beginning, in front of the '='.

Hi When you copy the token_v2 string into Alfred, does it look like this, where Xs are your id? "token_v2=XXXXXXXXX"

Pleased you got it working!

The spaceId isn't in the cookie. Perhaps this will help you locate it, if you're still looking to get it working:

And the space id can be found at step 4 above, by selecting preview instead of Cookies and finding the "spaceId" value in the resulting text.

Hey! If you're still struggling to find the value, because you're right it is a little different in the new safari, I would suggest the following: 1) Type something into the 'Search DorianWorks..' search box 2) In Safari developer (as shown in your screenshot) click on the network tab. 3) Find and click on 'search' in the list. 4) On the right hand side there will be another tab menu, select 'Cookies' 5) The one we care about is at the bottom of the list called 'token_v2'. You want to copy the value into the alfred notion search cookie environment variable so it looks like 'token_v2=XXXXXXXXXXXXXX'. I.e. you'll need to add the '=' in there. Let me know how you get on

I've just updated to Monterey and tested everything is still working, and it seems to be. I'm also on Alfred 4.6 [1266] which added some compatibility for macOS Monterey, so it might be worth double checking you're also up to date on that front.

Hey, yes will definitely be adding this at some point! Just need to find some time to start on it 😁. The only thing stopping me from being too urgent about it, is the fact you need to be an admin in your workspace in order to use the Notion API. Do you use this tool for your personal notion workspace or for your work's notion workspace? Or both? Unless you're admin for your works notion workplace, you won't be able to use the Notion API for that anyway. Notion say they will improve the authentication process, so you don't have to be an admin to use it, in the future, which I think will be key for a lot of people's use.

Glad to hear.

It should work with the Notion app open. What is happening when you try to open a search result with the Notion app open?

Can you explain in more detail what happens when you press enter on a search result in Alfred? Do you receive any errors? Does it open a web browser (or notion app if you have that configured) with the result?