Setting up Helpjuice as a Source

Connecting Helpjuice to Guru makes your existing help center content searchable and accessible across your workspace. Your team can find answers from your Helpjuice knowledge base without leaving their workflow, and Guru's AI can use this content to provide intelligent responses.


πŸ‘₯

Access Required

Guru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.

Helpjuice Access: You need an admin-level API key from your Helpjuice account to authenticate the connection.


Setting up Helpjuice as a Source

  1. In Guru, go to Manage.
  2. Select Sources, then click Add Source.
  3. Choose Helpjuice from the list of integrations.
  4. Enter your Helpjuice API key (admin-level token).
  5. Provide your Helpjuice subdomain.
  6. Select your language preference from the list of available languages.
  7. Choose your permission settings:
    • Respect Helpjuice permissions: Guru will honor the access levels set in Helpjuice
    • Manage permissions in Guru: Control access using Guru Groups regardless of Helpjuice settings
  8. Select which article types to sync (Public, Internal, or both).
  9. Add a display name for the Source (optional) and click Connect Source.
  10. Assign which Guru Groups should have access to this content.

The initial sync will begin immediately and may take several minutes depending on the size of your Helpjuice knowledge base.

✍

Note

For native permissions to work properly, user email addresses must be visible to your organization in both Helpjuice and Guru.


What gets synced from Helpjuice

Article ContentMetadataAccess Levels
Article titleArticle URLPublic articles
Full article bodyCategory informationInternal articles
Formatting and structureLanguage settingsDeep links to articles

❗

Important

Private articles are not synced. The Helpjuice API does not provide access control information for Private articles, so Guru cannot determine who should have access to them. Only Public and Internal articles will sync to Guru.


Permission options explained

When setting up your Helpjuice Source, you have two options for managing who can access the synced content:

Respect Helpjuice permissions: Guru will mirror the access levels from Helpjuice. Users will only see content they have permission to view in Helpjuice. This requires that user email addresses match between both systems.

Manage permissions in Guru: You control access entirely through Guru Groups, independent of Helpjuice permissions. This is useful if you have limited Helpjuice seats but want broader access to knowledge in Guru.


Frequently asked questions about Helpjuice

Why aren't my Private articles syncing? The Helpjuice API doesn't expose access control details for Private articles, so Guru cannot determine which users should have access to them. Only Public and Internal articles will sync to your Guru workspace.

Can I sync content in multiple languages? Yes, you can select your preferred language during setup. Guru supports 50 popular languages for Helpjuice content. If your language isn't listed, contact Guru support to have it added.

How often does Guru sync with Helpjuice? Guru periodically syncs content updates from Helpjuice to keep your information current. You can also manually trigger a sync from the Source settings.

What happens if I change permissions in Helpjuice? If you selected "Respect Helpjuice permissions" during setup, Guru will sync these permission changes during the next refresh. If you're managing permissions in Guru, changes in Helpjuice won't affect access in Guru.

Can I filter which Helpjuice content syncs to Guru? Currently, you can choose to sync Public articles, Internal articles, or both. More granular filtering options, including category-level syncing, are being developed.

My team is seeing content from other departments. How can I fix this? This may happen if permissions are too broad or if articles cover multiple topics. Consider restructuring large articles in Helpjuice into smaller, focused pieces, or use Guru Groups to control access more precisely.