How to fetch child pages from Notion in a Zapier AI Agent

Hi there ​@LeviM 👋

Ah yes, currently each page would have to be added individually, the child pages aren’t automatically be included.

It would be a great improvement to be able to select whether child pages are included though, so I’d recommend submitting this idea to our Agents team here. That’ll help to get it on their radar for future updates to Zapier Agents! 

In the meantime, is it possible in Notion to create a new page that has the content from other pages embedded within it? Just wondering if you could then connect that page to the agent so that all the content becomes available as it’s all contained on the single page. Do you think that could work?

We’re talking hundreds of pages so that would not be ideal :)

I’ve created the feature request.

Thanks for getting back to me ​@LeviM. Ah yes, if you’ve got hundreds of child pages that’s definitely not ideal. Thanks for submitting that feature request to the team. Hopefully it’s something that can be added soon.🤞 

Not sure what the agent is being used for exactly but the Notion app has a Query Data Source (Advanced) search action available. Perhaps you could add that as a new tool to allow the agent to search across all those pages and obtain the information it needs.

Hope that helps. If you give that a try and get stuck or have any more questions, just let me know! 

​@LeviM is the Notion content that you’re trying to connect to your Agent stored in databases, or are they just pages throughout your workspace? If it’s the former, then you can connect the relevant database(s) to your Zapier Agent as a knowledge source, but this is much harder to do if the content is all in loose pages.

​@DennisWF Thanks! It’s mainly pages referenced in a parent page, not in a database I’m afraid..

​@SamB Thanks for getting back! The idea of the Agent is to be some kind of a Co Pilot for Customer Support so they can ask questions on internal knowledge or processes stored in Notion (eg which colours do we currently sell or how can a customer purchase theft insurance,...). Looking at the suggested search action, I doubt that will be helpful?

​@LeviM is there any reason all those child pages couldn’t be in a database? One way you could do that is create a new database within your existing parent page, and then just drag and drop all your child pages into that new database. Then you could give the Agent access to that database as a single knowledge source. 

Ah, I see ​@LeviM! I was thinking you could set up the search action to allow the agent to decide the query it uses to perform the search, so that it could use a different custom query each time, depending on the question it’s been asked.

But what DennisWF is suggesting would be a good approach, since it should make all the child page content accessible to the agent via the database. That said, the maximum number of synced child pages in a database is currently 100 so you may need to split them across multiple databases as you’ve got hundreds.

Keep us posted on how you get on! 🙂