Redash

Persyst connects to your Redash instance using its URL and a user API key. An admin then selects the queries to expose and grants them to the relevant people.

Prepare the key in RedashCopy section link

1. Sign in to Redash with the account that will own the integration. Prefer a dedicated account whose groups only allow the required data sources.
2. Open that account’s profile and copy its User API Key.
3. Note the instance’s base URL, such as https://redash.example.com, including the organization path if your installation uses one.

The user key inherits its owner’s permissions. A Query API Key, found on a query page, is unsuitable for this connection: Persyst also needs to list available queries.

Connect the instance in PersystCopy section link

1. In Data sources → Add a source, choose Redash.
2. Enter a connection name, the Redash URL and the user API key.
3. Click Test, then create the connector.
4. Select the approved queries to add to this source.
5. In Access management, grant queries and their tools to the relevant teams or members.

Choose the toolsCopy section link

Reading the latest result and executing a parameterized query are separate uses. Execution must be enabled for the connection, and the corresponding tool must be granted to the member.

The assistant does not receive query SQL and cannot submit arbitrary SQL or create or edit Redash queries. Interpret the latest result alongside its calculation date.

Verify usageCopy section link

Ask an authorized member: “List my Redash queries, then read the latest weekly tracking result and include its calculation date.” They should find only the queries granted to them.

Renew credentialsCopy section link

The web form does not yet offer key replacement on an existing connection. Prepare the new key with the Redash owner, then contact the Persyst team to arrange replacement while preserving queries and grants. Verify a read before removing the old access in Redash.

Reference: Redash API authentication and key types.