PERSYSTDocs
Connectors

Connectors

Choose your source’s guide, starting with connections requiring credentials.

These guides explain who prepares access with the provider, how to connect a source in Persyst and how to open it to the right people. Share them with your technical owner, even without a Persyst account.

API keys and reader accounts

ConnectorWhat to prepare
AircallAPI ID and API token, then phone lines to share
BatchREST API Key and Project Key
RedashInstance URL and user API key
PostgreSQLDedicated reader account, network and approved tables or views; setup prompt included
ClickHouseDedicated SQL user, reader profile and HTTPS endpoint; setup prompt included
SILAEClient ID, Client Secret and API subscription key
SellsyPrivate API V2 access with Client ID and Client Secret, then OAuth authorization
PurchaselyRead-only Management API key (:view scopes) and its expiry date, then apps
AWS servicesIAM role and External ID; only available in the enabled pilot

The PostgreSQL and ClickHouse guides include a copyable prompt for preparing reader access on your actual schema.

Authorization-based connections

These paths open the provider’s authorization screen:

After connecting

Assign resources and tools in Access management. A guide’s presence does not mean that connector is enabled or granted in your organization.

Passwords, keys and tokens belong in Persyst forms. Do not paste them into conversations with your assistant.

On this page