Require assistance with the external_content ingestDocument api

[Ashley]

Good Afternoon,

I need some guidance with AI Search, I have put together a rest message that returns results from our SharePoint Knowledge base, this is all working fine with it returning the unique document id, title, url etc but I need to get this into AI Search so it is searchable within Virtual Agent.

I have created the external content schema table and search profile etc:
https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/ai-search/task/create-ext-content-schema-ais.html

I have used the external_content/storeContent rest api to create the content pointer which is then used in the external_content/ingestDocument rest api.

Doing all this makes it searchable within Virtual Agent but the schema table I created remains empty and the url its using is pointing to the ServiceNow instance and not too the SharePoint site so ofc it fails to open.

The documentation around the api's is lacking in some areas and wondered if anyone else had any success ingesting external content that is searchable? wondering if I am doing the mapping wrong.

Any help and I would be grateful

Kind Regards

Ashley

[Feddy]

Thanks for your input. Our external source is not other instance but QuickHelp API.
What would be the trigger for flow designer or how the REST Message API will be consumed during AI search?

[Ashley]

Good Morning,

I figured for flow designer it wouldn't be another instance but it does a pretty good job providing the steps for setting up the 2 api's you need.

1st being the binary content which returns the content header sys_id which is then used in the ingest document api (2nd) that points to the schema table you created making it available in AI Search.

I expect flows might be easier for you to configure, trigger will be whatever QuickHelp API does i.e. it creates an incident which is flagged as coming from them or maybe it creates an Article with its contents emailed to the instance, which then triggers the flow with the 2 api's within it that ingests the content making it searchable within AI Search as a hyperlink.

AI Search does not use the Rest Message during it search, the api's simply make an index reference for ai search to use.

This can be deleted using Rest API Explorer > API Name = AIS External Content Ingestion API

Kind Regards

Ashley

[Feddy]

We have referred below link to set up our existing search source. we have used the same data fetch script and replaced our authorization key. It doesn't have any trigger point .

https://support.quickhelp.com/support/solutions/articles/6000220804-quickhelp-servicenow-search-integration

We would like to know if the same can be achieved using integration hub/flow designer or REST Message. Any input on this would be much appreciated