Unily Ingestion - Issue

4 replies
341 views

Hello Everyone

Trying ingest Unily , created connector as per https://help.moveworks.com/docs/content-integration-unily.

But in internal knowledge ingestion , no wizard is coming up(not like we have during service now setup), and not able to ingest, can anyone guide on this the right way

Ingested Knowledge

N

natedogistheillest

Known Participant

Can you confirm that the permissions are set correctly and that you have the correct ClientID and Secret. I havent done this connector but I did find this KBA Unily Access Setup Guide

X

xawam

Participating Frequently

Hi,

With Unily, the ingestion process doesn’t use a wizard like ServiceNow. After creating the connector (as per the documentation), you need to manually trigger the ingestion from the connector settings. Make sure your connector configuration, API keys, and permissions are correct, as this info is crucial to avoid errors. Then check the logs for any issues during ingestion. Once triggered, the content should start populating in the internal knowledge base.

S

Sinclair

New Participant

Hi,

With Unily, the ingestion process doesn’t use a wizard like ServiceNow. After creating the connector (as per the documentation), you need to manually trigger the ingestion from the connector settings. Make sure your connector configuration, API keys, and permissions are correct, as this çin takvimi is crucial to avoid errors. Then check the logs for any issues during ingestion. Once triggered, the content should start populating in the internal knowledge base.

These problems can stem from malformed files, API connection failures, permission mismatches, or incorrect configuration within your Unily tenant. When ingestion fails, dashboards, content feeds, user profiles, or analytics may not refresh as expected.

C

cressidi650

New Participant

Hi,

With Unily, the ingestion process doesn’t use a wizard like ServiceNow. After creating the connector (as per the documentation), you need to manually trigger the ingestion from the connector settings. Make sure your connector configuration, API keys, and permissions are correct, as this tomato apk is crucial to avoid errors. Then check the logs for any issues during ingestion. Once triggered, the content should start populating in the internal knowledge base.

A Unily ingestion issue occurs when content, data, or documents fail to sync correctly from connected systems into the Unily digital workplace platform. These problems can arise due to misconfigured connectors, authentication failures, API limitations, network interruptions, or incorrect data mapping rules.

Sign up

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.

Login or create an account

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.