Integrations

Connect your knowledge base

Connect the place where Pageloop reads your articles and publishes updates.

Connect your knowledge base

The Knowledge base integration role chooses where Pageloop reads your articles and publishes updates. Your workspace has one knowledge base assignment. Connecting a tool makes the tool available; connecting another tool does not replace an existing assignment.

If Knowledge base shows Not set, Pageloop has no active publishing destination assigned. A connected tool alone is not enough: choose the tool for this role before relying on Pageloop to read or publish through it. An inactive connection can also appear as Not set; finish setup or reconnect the tool before assigning it.

Set or change the Knowledge base role

You must be an Admin in the Pageloop workspace to connect tools and change integration roles. Other workspace members can view connections but cannot configure them.

  1. Open Integrations from the sidebar, or open Settings → Integrations.
  2. Connect your publishing tool using the section below.
  3. Scroll to Integration roles. On Knowledge base, click Choose if the role is not set, or Change to switch tools.
  4. Select the connected service in Change Knowledge Base, then click Save.
  5. Confirm that the Knowledge base card names the intended service. A Connected status on a tool's card confirms the connection, not the role assignment.

For a repo-backed Pageloop site, the role appears as Pageloop Docs. Creating a docs site fills an empty Knowledge base role automatically. If another service already holds the role, select Pageloop Docs explicitly to use the site as your destination.

Support tickets and proactive suggestions

The separate Ticketing role chooses where Pageloop gets support conversations to look for documentation gaps. You can use one tool for articles and another for tickets. In Integration roles, use Choose or Change on Ticketing, select a connected service, and click Save.

ToolProactive suggestions from support tickets
IntercomYes, with a connection that includes conversation access. An articles-only connection cannot fill the Ticketing role.
ZendeskYes
FreshdeskYes
DevRevYes
SalesforceYes
Pageloop Knowledge Base, Help Scout, Document360, Helpjuice, PylonNo support-ticket source through these knowledge base connections

Assign a supported tool to Ticketing if you want Pageloop to use that tool's support conversations. Leaving Ticketing Not set does not remove your Knowledge base assignment.

Pageloop Knowledge Base

Use a repo-backed Pageloop docs site when your articles live in a repository and Pageloop hosts the published site. There is no separate Pageloop connection tile in Integrations. The steps below use GitHub as the repository provider.

Before you start

  • Have access to Knowledge base in Settings.
  • Have a GitHub repository for your docs and permission to install or configure the Pageloop GitHub App for that repository.
  • For an existing docs site, know the publishing branch and the path to docs.json in the repository.

Connect

  1. In Integrations, find GitHub and click Connect. If GitHub is connected, open its Configure control instead.
  2. Install or authorize the Pageloop GitHub App and grant access to the docs repository.
  3. In the GitHub configuration dialog, select Knowledge base repository and click Save. Product repositories are a separate selection for repositories Pageloop watches for merged pull requests; they do not choose the published docs site.
  4. Open Settings → Knowledge base to create the Pageloop site. Select the repository and complete the setup flow.
  5. Enter Site name, Slug, Branch, and, when shown, Config path. Leave Branch blank to use the repository's default branch. Click Create knowledge base.
  6. If setup opens a pull request, review and merge the pull request in GitHub so the setup files reach the publishing branch.
  7. Return to Integrations → Integration roles and confirm Knowledge base is Pageloop Docs. If needed, change the role.

Confirm it worked: Reopen GitHub configuration and check that Installation health reports Installed and reachable and does not warn that the docs repository is unreadable. Open Knowledge Base to check that the repository's pages have synced, then open the site's published address to check the build. A successful GitHub connection alone does not confirm that the site has built.

Intercom

For the full setup, publishing options, and error messages, see Intercom integration.

Before you start

  • Have access to authorize Pageloop for the Intercom workspace that owns your articles.
  • Know the workspace ID and the workspace's hosting region.
  • If you want support-ticket suggestions, use a connection that grants conversation access, not an articles-only connection.

Connect

  1. In Integrations, find Intercom and click Connect.
  2. Authorize Pageloop in the intended Intercom workspace and return to Pageloop.
  3. In Configure Intercom Integration, confirm Intercom Region and Workspace ID. Check the detected workspace ID rather than replacing it unless it is incorrect.
  4. Click Save Configuration. To revisit these values, open Intercom's Configure control in Integrations.
  5. Assign Intercom to Knowledge base. Assign Intercom to Ticketing separately if you want support-ticket suggestions and the connection includes conversation access.

Confirm it worked: Check that the Intercom card is Connected, reopen configuration to verify the region and workspace ID, and confirm the Knowledge base role names Intercom. Check that your Intercom articles appear in Pageloop after sync.

Zendesk

Before you start

  • Know your Zendesk subdomain: the account name before .zendesk.com.
  • Have a Zendesk account that can authorize access to read and write Help Center articles. The authorization also requests access to read tickets and users for support-driven suggestions.

Connect

  1. In Integrations, find Zendesk and click Connect.
  2. Enter Subdomain, then click Connect. Zendesk uses an authorization flow; you do not enter an API key in this dialog.
  3. Approve Pageloop's requested access in Zendesk and return to Pageloop.
  4. Assign Zendesk to Knowledge base. Assign Zendesk to Ticketing as well if you want support-ticket suggestions.

Confirm it worked: Check that Zendesk is Connected and that the Knowledge base card names Zendesk. Check that articles from the intended Zendesk Help Center appear in Pageloop after sync.

Freshdesk

For full setup steps, settings, publishing behavior, and troubleshooting, see Freshdesk integration.

Before you start

  • Know your Freshdesk subdomain.
  • Get the API key of a Freshdesk agent whose role can publish solution articles without approval. If the agent's role requires publishing approval, Pageloop cannot publish live.
  • If your help center uses a custom domain, have that hostname ready.

Connect

  1. In Integrations, find Freshdesk and click Connect.
  2. Enter Subdomain and API Key, then click Connect. Use Find your API Key if you need help locating the key.
  3. In Configure Freshdesk Integration, enter Custom domain if your help center uses one, then click Save Configuration. You can reopen this dialog with Freshdesk's Configure control.
  4. Assign Freshdesk to Knowledge base. Assign Freshdesk to Ticketing as well if you want support-ticket suggestions.

Confirm it worked: Check that Freshdesk is Connected, verify any saved custom domain, and confirm that Knowledge base names Freshdesk. Check that solution articles appear in Pageloop after sync. Connection success does not override the API key owner's publishing permissions.

Help Scout

Before you start

  • Have a Help Scout Docs API key and an accessible Docs site. This connection uses the Docs API, not the support inbox API.
  • To find the key, open your Help Scout profile's Security and Access section and look for Docs API. The account owner must grant Docs: Create new, edit settings & Collections permission for the key to be available.
  • Decide which site to connect if the account has multiple Docs sites. You can link one site per integration.

Connect

  1. In Integrations, find Help Scout and click Connect.
  2. Enter API Key, then click Continue. The dialog also includes Find your API Key.
  3. If multiple sites are available, select the intended site under Choose a Help Scout site and click Connect site. Pageloop selects and configures the site automatically when only one is available.
  4. Assign Help Scout to Knowledge base.

Confirm it worked: Look for Help Scout connected, check that the card is Connected, and confirm that Knowledge base names Help Scout. Check that articles from the selected Docs site appear after sync. If single-site configuration fails, use Retry without re-entering the saved key.

Document360

For full setup instructions, sync and publishing behavior, and troubleshooting, see Document360 integration.

Before you start

  • Have your help center URL and a Document360 API token for the project.
  • Know which project version contains the articles you want Pageloop to sync.

Connect

  1. In Integrations, find Document360 and click Connect.
  2. Enter Help Center URL and API Token, then click Connect. Use Find your API Token if needed.
  3. Open Document360's Configure control. Under Select a project version to sync, select the intended version.
  4. Click Save Configuration. You can return to Configure to change the version.
  5. Assign Document360 to Knowledge base.

Confirm it worked: Check that Document360 is Connected and that Configure shows the intended project version. Confirm that Knowledge base names Document360, then check that articles from that version appear after sync.

Helpjuice

Before you start

  • Have the full HTTPS URL of your Helpjuice help center on its .helpjuice.com domain.
  • Have your Helpjuice API key.

Connect

  1. In Integrations, find Helpjuice and click Connect.
  2. Enter Help Center URL and API Key. Use Find your API Key if needed.
  3. Click Connect.
  4. Assign Helpjuice to Knowledge base.

Confirm it worked: Check that Helpjuice is Connected, confirm that Knowledge base names Helpjuice, and check that the intended help center's articles appear after sync. To replace the stored key later, open Helpjuice's Configure menu and choose Replace API key.

DevRev

Before you start

  • Know your DevRev subdomain.
  • Have a DevRev personal access token for the account you want to connect.

Connect

  1. In Integrations, find DevRev and click Connect.
  2. Enter Subdomain and Personal Access Token. Use Generate PAT if you need help obtaining a token.
  3. Click Connect.
  4. Assign DevRev to Knowledge base. DevRev can also fill the Ticketing role for support-ticket suggestions.

Confirm it worked: Check that DevRev is Connected, confirm that Knowledge base names DevRev, and check that the intended account's articles appear in Pageloop after sync.

Salesforce

Before you start

  • Enable Salesforce Knowledge and configure at least one Record Type for the Knowledge object.
  • Have the Salesforce instance URL, not the Salesforce Setup URL, and the public URL of your Knowledge site.
  • Prepare credentials for one of the wizard's authentication methods: Client Credentials requires a Consumer Key and Consumer Secret; JWT Bearer requires a Consumer Key, the Salesforce Username Pageloop will act as, and access to upload a certificate to the Salesforce External Client App.
  • Know which fields hold the article body, title, and URL name for each article type.

Connect

  1. In Integrations, find Salesforce and click Connect.
  2. Choose Authentication Method and enter Instance URL and Consumer Key.
  3. For Client Credentials, enter Consumer Secret. For JWT Bearer, enter Salesforce Username, click Generate Certificate, upload the downloaded certificate to your Salesforce External Client App, then use Test Connection.
  4. Click Connect to continue to field mapping.
  5. Set Help Center URL to your public Knowledge site URL. Under Field Mapping by Article Type, expand each article type and confirm Article Body Field, Title Field, and URL Name Field. Set optional summary, author, and category fields if you use them.
  6. Click Save & Finish. Use Salesforce's Configure control to revisit field mappings later.
  7. Assign Salesforce to Knowledge base. Assign Salesforce to Ticketing as well if you want support-ticket suggestions.

Confirm it worked: For JWT Bearer, Test Connection should report Connection successful. After field mapping, look for Configuration saved and an active Salesforce connection rather than Finish setup. Confirm that Knowledge base names Salesforce and check that Knowledge articles appear after sync. If no article types are found, check that Knowledge is enabled and the Knowledge object has a Record Type.

Pylon

For the full setup, syncing, publishing, and troubleshooting guide, see Pylon integration.

Before you start

  • Have a Pylon knowledge base accessible to your API token.
  • A Pylon Admin must create the API token. Copy the token when it is created; Pylon shows the token only once.
  • Decide which knowledge base to connect if your workspace has more than one. You can link one knowledge base per integration.

Connect

  1. In Integrations, find Pylon and click Connect.
  2. Enter API Token, then click Continue. Use Find your API Token if needed.
  3. If multiple knowledge bases are available, select the intended one under Choose a Pylon knowledge base and click Connect knowledge base. Pageloop selects and configures the knowledge base automatically when only one is available.
  4. Assign Pylon to Knowledge base.

Confirm it worked: Look for Pylon connected, check that Pylon is Connected, and confirm that Knowledge base names Pylon. Check that articles from the selected knowledge base appear after sync. If single-knowledge-base configuration fails, use Retry without re-entering the saved token.