WebsDocs WebsDocsConnector Hub Connector support

Secure platform authorization · Controlled publishing

WebsDocs Connector

Connect an approved WebsDocs product to the website platform you already use—without sharing your platform password or manually rebuilding the widget integration.

Choose a WebsDocs product See the client process
Client initiated Platform authorized Encrypted credentials Verified installation

Six client connection paths

Publish through the platform your business already controls.

Availability is shown from the live Connector Hub configuration. Individual connections begin only after a signed-in client requests them from a WebsDocs product dashboard.

WP Ready to connect

WordPress

Clients install and authorize the WebsDocs Connector plugin. The plugin publishes the approved widget loader without manual theme editing.

Connection
Plugin Authorization
Installation
Plugin
S Ready to connect

Shopify

Clients authorize the WebsDocs Shopify application and enable its approved theme app embed for their selected storefront.

Connection
Application Oauth
Installation
Theme App Embed
Wi Configuration in progress

Wix

Clients install the WebsDocs Wix application and approve its embedded script extension for their selected website.

Connection
Application Install
Installation
Embedded Script Extension
Sq Ready to connect

Squarespace

Clients receive an approved loader snippet and place it through Squarespace Code Injection with administrator permission.

Connection
Application Authorization
Installation
Code Injection
Wf Configuration in progress

Webflow

Clients authorize Webflow access and select the site where the approved custom-code installation should be published.

Connection
Application Oauth
Installation
Custom Code Api
GTM Ready to connect

Google Tag Manager

Clients authorize Google Tag Manager, select their account, container and workspace, and approve creation and publication of the WebsDocs widget tag.

Connection
Google Oauth
Installation
Custom Html Tag

Platform availability can depend on the client’s subscription, administrator permissions and support for plugins, applications or custom code.

Platform-by-platform instructions

How clients use each connector

Every connection begins from the client’s WebsDocs product dashboard. The website URL, product Site ID and approved loader are carried into the platform-specific authorization flow.

WPPLUGIN AUTHORIZATION

WordPress

Client needsWordPress administrator accessHTTPS websiteA plan or host that permits plugin uploads
  1. Enter the WordPress website URL and choose Connect WordPress in WebsDocs.
  2. Download the WebsDocs Connector ZIP from the provided installation page.
  3. In WordPress Admin, open Plugins → Add New Plugin → Upload Plugin, then install and activate it.
  4. Open the authorization link and choose Authorize WebsDocs Connector.
  5. Return to WebsDocs and verify. The plugin injects the approved loader and Site ID on the public website.

Remove: Deactivate and delete the WebsDocs Connector plugin, then ask WebsDocs support to close the associated connection record if required.

SAPPLICATION OAUTH

Shopify

Client needsShopify store-owner permissionPermanent myshopify.com domainTheme app-embed access
  1. Enter the storefront URL, choose Connect Shopify, and provide the permanent store-name.myshopify.com domain when requested.
  2. Shopify displays the WebsDocs application permissions. Review them and approve installation.
  3. The connector stores the product Site ID and approved loader settings as application data.
  4. Shopify opens the Theme Editor. Enable the WebsDocs app embed and save the theme configuration.
  5. Return to WebsDocs and verify that the approved loader is visible on the storefront.

Remove: Disable the theme app embed and uninstall the WebsDocs application from Shopify.

WiAPPLICATION INSTALL

Wix

Client needsWix site-owner permissionPublished Wix sitePermission to install applications
  1. Enter the Wix website URL and choose Connect Wix in WebsDocs.
  2. Wix opens the WebsDocs application installation screen. Select the intended site.
  3. Review the requested application permissions and approve installation.
  4. The Wix embedded-script extension receives the approved loader configuration for that Site ID.
  5. Publish the Wix site if Wix requests publication, then return to WebsDocs and verify.

Remove: Uninstall the WebsDocs application from the Wix site dashboard and republish the site if required.

SqCODE INJECTION

Squarespace

Client needsSquarespace site-owner permissionHTTPS websiteA plan that permits Code Injection
  1. Enter the Squarespace website URL and choose Connect Squarespace.
  2. Copy the complete approved loader snippet shown by WebsDocs.
  3. In Squarespace, open Settings → Advanced → Code Injection.
  4. Paste the snippet in the Footer area and save. Do not change its loader URL, Site ID or data attribute.
  5. Open the public website, then return to WebsDocs and verify the installation.

Remove: Delete the WebsDocs loader snippet from Squarespace Code Injection and save.

WfAPPLICATION OAUTH

Webflow

Client needsWebflow workspace administratorCustom-code permissionPermission to publish the selected site
  1. Enter the Webflow website URL and choose Connect Webflow.
  2. Review and authorize the WebsDocs application permissions for reading sites and managing custom code.
  3. If more than one site is available, select the intended Webflow site in the WebsDocs dashboard.
  4. The connector registers the approved hosted loader, adds its Site ID attribute and publishes the selected site.
  5. Return to WebsDocs and verify that the public site contains the expected loader.

Remove: Remove the WebsDocs custom-code script from Webflow, publish the site and revoke the WebsDocs application authorization.

GTMGOOGLE OAUTH

Google Tag Manager

Client needsGoogle account with GTM accessContainer edit and publish permissionThe intended website container
  1. Enter the website URL and choose Connect Google Tag Manager.
  2. Review Google’s consent screen and approve the displayed Tag Manager permissions.
  3. Back in WebsDocs, select the intended GTM account, container and workspace.
  4. The connector creates an All Pages trigger, the WebsDocs custom HTML tag and a new container version, then publishes that version.
  5. Return to the website and verify the approved loader and Site ID through WebsDocs.

Remove: Remove or pause the WebsDocs tag in GTM, publish a new version and revoke WebsDocs access in Google Account permissions if desired.

Important client safety

Authorize only from a signed-in WebsDocs dashboard and the official connector.websdocs.com domain. Never send platform passwords, OAuth client secrets, access tokens or one-time authorization links through email or support tickets.

Client-controlled setup

How a WebsDocs connection works

  1. 01

    Start in WebsDocs

    The client enters the intended website URL and chooses a supported platform from their product dashboard.

  2. 02

    Authorize at the platform

    The platform displays its own login and consent experience. WebsDocs never asks the client to send us their platform password.

  3. 03

    Approve the installation

    The connector installs or prepares the approved loader using the product Site ID and the platform’s supported publishing surface.

  4. 04

    Verify and operate

    The Connector Hub checks the intended public site, records installation evidence and reports the connection state to the client dashboard.

Google API data and platform permissions

Access is limited to the connection the client requests.

For Google Tag Manager, WebsDocs Connector requests permission to manage containers, create container versions and publish the client-approved widget tag. It does not request Gmail, Drive, Calendar or general Google Account content.

Authorization tokens are encrypted before storage. Connection records retain the selected platform identifiers, installation status and verification evidence needed to operate and support the connector.

RequestedGTM container publishing

Account, container and workspace selection plus the permissions required to install and publish the approved tag.

Not requestedPasswords or unrelated Google data

Clients authenticate with Google or their selected platform. WebsDocs does not receive the platform password.

Client controlRevoke or remove access

Clients can remove the installation through their platform and revoke Google access from their Google Account permissions.

Privacy Policy Terms of Service Contact WebsDocs

Client FAQ

Before you connect

What is WebsDocs Connector?

WebsDocs Connector is the shared, client-authorized publishing service used by RTD Voice, RTC Chat, ASG and IA to install an approved WebsDocs widget on a supported website platform.

Do I give WebsDocs my platform password?

No. Sign-in and consent take place with the selected platform. WebsDocs receives only the authorization result and permissions needed for the requested installation.

What does the WordPress plugin install?

The plugin stores the approved Site ID and loader settings, injects the WebsDocs product loader on the public website and provides a signed endpoint for installation verification.

What does Google Tag Manager access?

After Google authorization, the client selects the GTM account, container and workspace. The connector uses the approved GTM scopes to create and publish the WebsDocs custom HTML tag.

Can I connect more than one product?

The Connector Hub supports RTD Voice now and is designed as the shared connection authority for RTC Chat, ASG and IA. Each product and website connection retains its own Site ID and status.

Can access be removed?

Yes. Remove the plugin, app, tag or custom code through the platform and revoke connected-app access where applicable. Contact WebsDocs support for help with the associated connector record.

Why does my platform show additional requirements?

Some plans restrict custom plugins, applications or code injection. The client must have administrator access and a platform plan that permits the selected installation method.

Where can I get help?

Use the WebsDocs Support Center for setup, authorization, verification or removal assistance. Never include passwords, OAuth secrets or private access tokens in a support ticket.

Ready when your website is ready

Start the connection from your WebsDocs product dashboard.

Choose the website and platform you control. The Connector Hub will guide the supported authorization, installation and verification steps.

Explore WebsDocs products Open a support ticket