Integrations

Pylon integration

Connect a Pylon knowledge base, check its integration role, and troubleshoot setup and syncing.

Pylon integration

Connect Pylon so Pageloop can read your knowledge base's collections and articles and prepare updates for review. Pylon can hold the Knowledge base role only; it does not supply support conversations through this connection.

For an overview of help-center connections and integration roles, see Connect your knowledge base.

Before you begin

  • Sign in to Pageloop as an Admin.
  • Copy a Pylon API token. You must be a Pylon Admin to create one, and Pylon shows the token only once, so copy it straight away. The Find your API Token link in the connection dialog opens Pylon's guide.
  • Make sure your Pylon workspace has at least one knowledge base accessible to the token. Decide which one to connect if you have several. You can link one Pylon knowledge base per Pageloop integration.

Connect and configure Pylon

  1. Open Integrations from the sidebar, or Settings → Integrations. Find the Pylon card under Knowledge base on the Integrations page and select Connect.

  2. In Connect Pylon, paste your token into API Token and select Continue. Use your own token, such as <your API key>, rather than the sample value shown.

  3. If one knowledge base is available, Pageloop connects it automatically and shows Configuring <knowledge base>…. If several are available, select one under Choose a Pylon knowledge base, then select Connect knowledge base.

  4. Check for Pylon connected with the message “Your Pylon knowledge base is now linked to Pageloop.” The Pylon card reads Connected.

  5. Check Integration roles at the bottom of the page to confirm whether Knowledge base names Pylon. Follow the role check below if another service holds it.

Check the Knowledge base role

Knowledge base is “Where Pageloop reads your articles from and publishes updates to.” Connecting Pylon assigns this role only if no service already holds it.

If another service, such as Pageloop Docs, holds the role, Pylon connects but does not sync. The connection success message does not warn you about the existing assignment, so always check Integration roles after connecting.

To switch from another service to Pylon:

  1. Under Integration roles, select Change on Knowledge base.
  2. In Change Knowledge Base, which says “Pick a connected service to read from and write to.”, pick Pylon.
  3. Select Save and confirm that Knowledge base names Pylon.

There are no settings to configure after connecting Pylon, and the card has no gear button. To switch the linked Pylon knowledge base, disconnect and connect again.

What Pageloop reads and writes

When Pylon holds the Knowledge base role, Pageloop syncs the linked knowledge base's collections and articles every hour. Published content counts as the current version. Pageloop uses a draft only for an article that has never been published.

Proposed changes arrive in the Inbox for a person to review. Nothing reaches Pylon until a person publishes. When publishing an article, choose a collection or Knowledge base root as its destination, then choose Publish or Save as draft in Pylon.

Articles Pageloop creates in Pylon are authored as the person who owns the API token. See Review an Inbox item and Finish an Inbox item for the review and publishing workflow.

Disconnect Pylon

  1. In Integrations, point at Connected on the Pylon card. The control changes to Disconnect; select it.
  2. Review Disconnect Pylon?, which says “Pageloop stops reading from and writing to it.” If Pylon holds the Knowledge base role, the dialog also says “Pylon is your knowledge base integration. That role is left unassigned until you pick another.”
  3. Select Disconnect to confirm, or Keep connected to cancel. Pylon disconnected confirms the disconnection.

Disconnecting does not invalidate the API token in Pylon. Delete the token there if you no longer want Pageloop to have access.

Reconnect a paused or unfinished connection

If Pageloop loses access, for example because the token was deleted or syncing failed several times in a row, the card shows Needs reconnecting. The page says “Pylon needs to be reconnected. Pageloop lost access, so it is paused until you reconnect it.” The card also shows Needs reconnecting if setup was closed before a knowledge base was chosen.

Open the ... menu on the Pylon card, select Disconnect, then select Connect and repeat the connection steps. Check the Knowledge base role again after reconnecting.

Troubleshooting

Connection dialog

MessageWhat to do
“Invalid Pylon API token or insufficient permissions”Check that you copied the intended token and that it has access to the knowledge base. A Pylon Admin must create the token.
“This Pylon workspace has no knowledge bases. Create one in Pylon, then connect again.”Create a knowledge base in Pylon, then connect again.
“No Pylon knowledge bases are accessible with this API token.”Check the token's access to the intended knowledge base in Pylon, then retry with a token that can access it.
“Pylon rate-limited us. Try again in a minute.”Wait a minute, then try again.
“Pylon is already connected. Disconnect the existing connection first if you want to reconnect.”Open the Pylon card's ... menu, select Disconnect, then Connect.
“Couldn’t connect <knowledge base>. Your token is still saved — retry without re-entering it.”Select Retry. You do not need to paste the token again.
“Could not reach Pylon to validate the API token”Try again shortly.

Knowledge base syncing

Message or symptomWhat to do
Pylon is Connected, but its articles are not syncing.Check whether Pylon holds the Knowledge base role. A connection alone does not replace another service's assignment.
Needs reconnecting, or “Pylon needs to be reconnected. Pageloop lost access, so it is paused until you reconnect it.”Disconnect and connect again. Use the same fix if setup was closed before you chose a knowledge base.
“Pageloop can’t sign in to your Pylon help center, so it isn’t syncing.”Disconnect Pylon, then connect again.
“Pageloop stopped syncing your Pylon help center after it failed several times in a row.”Disconnect Pylon, then connect again.
“The last sync of your Pylon help center didn’t finish. Pageloop keeps trying on its own.”Pageloop retries automatically.
“Pageloop paused syncing: most of your Pylon articles were missing from the last read, so it kept them rather than delete them. If you didn’t remove them, contact support.”Contact support if you did not remove the articles. Pageloop kept the articles rather than deleting them.