Operations · document 14

Integrations

In the workspace: /connectors

Availability

Included on Advanced

This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.

What it is for

Provider credentials live here, once per account, and nowhere else. This is where you connect Google, Bing, Yandex and IndexNow so that the pages which read or submit on your behalf have something to work with. Credentials are stored encrypted and are never displayed again after saving, which is why this page shows you a connection state rather than a secret.

How to use it

Open the connector you need. Each one states what it will be able to do once connected, before you connect it.
Follow the provider sign-in. You are authorising your own account at that provider; this platform never asks for a provider password.
Match the property to a project where the connector asks for it. A provider account can hold many properties, and only a matched one is read.
Verify ownership of the project separately, on the project page. Reading a provider account and submitting instructions for a hostname are different permissions.

Reading the result

A connector is connected, matched, or neither, and the state is shown as a badge rather than a percentage because there is nothing in between. Connected means the credential works; matched means a property at that provider has been tied to one of your projects. Reading data needs the first; submitting anything needs both, plus a verified project.

What it cannot tell you

A connection is your authorisation and it can be withdrawn at the provider without telling this platform, so a connector that worked yesterday can fail today and the honest report of that is an error rather than a stale figure. Credentials are per account, not per project: connecting once serves every project you own, and disconnecting removes that access everywhere at once.

What it keeps

The credential, encrypted with AES-256-GCM, and never shown again after it is saved. Disconnecting clears the stored tokens and the synchronised property list; resetting clears the credential itself as well. Every one of those actions is recorded, because a change to what this platform may do on your behalf should never be silent.