From 940f4c9a13153310556be39f7fdcf610e4d4d7f6 Mon Sep 17 00:00:00 2001 From: Nikita Date: Wed, 5 Aug 2026 01:40:14 +0200 Subject: [PATCH 1/2] docs: fix four stale UI labels found by walking Getting Started MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Walking the platform for the Getting Started rework (#1071) turned up four places where these pages describe an interface that has moved on. Each was verified live in a project on 2026-08-04, not inferred. **flows/** — scheduling is no longer a "Set Schedule" button. It is the flow's **Schedules** tab → **Create Schedule** → **Set Up Schedule**, with predefined intervals or a custom one. Also documented what the old text could not: a flow can hold several schedules, they fire independently, and each has a toggle so you can pause one without deleting it. (flows-legacy/ still says Set Schedule and is left alone — that is correct for the legacy builder.) **management/notifications/** — split by flow type instead of describing only the legacy path. A Conditional Flow's **Notifications** tab is edited in place, with three cards: Success, Errors, Processing. There is no "Edit Notifications" button and no warning notification — Conditional Flows express that through conditions. The legacy instructions are kept, labelled as such. Also renamed the second of two sections both titled "Flow Notifications". **components/extractors/storage/http/** — the UI says **Add Row** in a **Rows** section, not "Add Table"; the field is **Table name** seeded from the row name, not "Table Name" from a configuration table name; **Incremental load**, not "Incremental Load". Added that **Read Header** already defaults to reading the file's header, which is the setting most readers want and never have to change. **kai/** — the button reads **Kai Agent** with a *Beta* pill, not **KAI**. Found while writing #1071; kept out of that PR because these belong to their own sections. --- .../components/extractors/storage/http/index.md | 15 ++++++++------- src/content/docs/flows/index.md | 4 +++- src/content/docs/kai/getting-started.md | 2 +- src/content/docs/kai/index.md | 2 +- .../management/notifications/notifications.md | 15 ++++++++++++--- 5 files changed, 25 insertions(+), 13 deletions(-) diff --git a/src/content/docs/components/extractors/storage/http/index.md b/src/content/docs/components/extractors/storage/http/index.md index b196481ca..a536af4cf 100644 --- a/src/content/docs/components/extractors/storage/http/index.md +++ b/src/content/docs/components/extractors/storage/http/index.md @@ -12,16 +12,17 @@ This data source connector loads a single CSV file from an HTTP/HTTPS URL and st ## Configuration [Create a new configuration](/components/#creating-component-configuration) of the **HTTP** connector. -Enter a base URL -- the prefix for all downloaded CSV files from a given website +Open **Base URL and Connection Options** and enter a base URL -- the prefix for all downloaded CSV files from a given website *(for example, `https://help.keboola.com`; you can then test the extraction on our sample tables)*. ![Screenshot - Base URL](/components/extractors/storage/http/http-1.png) The base URL can also contain folder specification if the same folder is used for all files downloaded using this base URL. -## Add Tables -To create a new table, click the **Add Table** button and assign a name. -It will be used to create the destination table name in Storage and can be modified. +## Add Rows +Each file you download is a configuration row. Click **Add Row** in the **Rows** section, +assign a name, and click **Create**. The name seeds the destination table name in Storage and +can be changed afterwards. ![Screenshot - Create table](/components/extractors/storage/http/http-2.png) @@ -42,9 +43,9 @@ want to load one of our tutorial tables, enter its path, e.g., `/tutorial/opport ![Screenshot - Save Settings](/components/extractors/storage/http/http-4.png) -- The initial value in **Table Name** is derived from the configuration table name. You can change it at any time; however, +- The initial value in **Table name** is derived from the row name. You can change it at any time; however, the [Storage bucket](/storage/buckets/) where the table will be saved to cannot be changed. -- **Incremental Load** will turn on [incremental loading to Storage](/storage/tables/#incremental-loading). The result of the +- **Incremental load** will turn on [incremental loading to Storage](/storage/tables/#incremental-loading). The result of the incremental load depends on other settings (mainly **Primary Key**). - **Delimiter** and **Enclosure** specify the CSV settings. @@ -52,7 +53,7 @@ incremental load depends on other settings (mainly **Primary Key**). ![Screenshot - Header & Primary Key](/components/extractors/storage/http/http-5.png) -There are three options for determining column names: +The **Read Header** option defaults to *Read the header from the file(s) header*. There are three options for determining column names: - **Set header manually** --- This option enables the **Set Headers** input to manually specify all columns in the table. - **Read from the file(s) header** --- This option assumes that each file has a header on the first line. diff --git a/src/content/docs/flows/index.md b/src/content/docs/flows/index.md index f58028f20..7040b01ac 100644 --- a/src/content/docs/flows/index.md +++ b/src/content/docs/flows/index.md @@ -362,7 +362,9 @@ You can also create the notification inside of condition as a New Phase, name it ## Schedule and Automate -Click on **Set Schedule** in your flow and select when you want the flow to run. You can select predefined intervals or set your own. Another option is to use triggers to initiate the run. +Open the flow's **Schedules** tab and click **Create Schedule**, then choose when the flow runs — a predefined interval (**Every 15 minutes**, **Every hour**, **Once a day**, **Once a week**, **End of month**) or your own under **Set Your Own** — and confirm with **Set Up Schedule**. Another option is to use triggers to initiate the run. + +A flow can hold several schedules. They work independently, and the flow runs whenever any of them fires. Each one has a toggle, so you can pause a schedule without deleting it. **Scheduling:** Commonly, flows are set to run at specific times. To avoid busy periods in a shared environment, consider scheduling slightly off-peak for smoother execution. diff --git a/src/content/docs/kai/getting-started.md b/src/content/docs/kai/getting-started.md index 864ca32a7..306e5098b 100644 --- a/src/content/docs/kai/getting-started.md +++ b/src/content/docs/kai/getting-started.md @@ -19,7 +19,7 @@ Every user can see the Kai button in their project (on supported stacks). To ena ## Opening Kai -Click the **KAI** button in your project's top navigation bar, or use keyboard shortcuts: +Click the **Kai Agent** button (marked *Beta*) in your project's top bar, or use keyboard shortcuts: | Shortcut | Action | |----------|--------| diff --git a/src/content/docs/kai/index.md b/src/content/docs/kai/index.md index cf8434b49..55b55c788 100644 --- a/src/content/docs/kai/index.md +++ b/src/content/docs/kai/index.md @@ -39,7 +39,7 @@ Kai is Keboola's embedded AI assistant—a context-aware data engineering co-pil ## Getting Started -Kai is now in **Public Beta** and available to all users. Look for the **KAI** button in your project's navigation bar. +Kai is now in **Public Beta** and available to all users. Look for the **Kai Agent** button, marked *Beta*, in your project's top bar. - **Organization Admins** can enable Kai directly from the chat screen - **Other users** can request access from their Organization Admin or [contact Keboola Support](mailto:support@keboola.com) diff --git a/src/content/docs/management/notifications/notifications.md b/src/content/docs/management/notifications/notifications.md index e3d5aa0e4..b8ca28e33 100644 --- a/src/content/docs/management/notifications/notifications.md +++ b/src/content/docs/management/notifications/notifications.md @@ -22,7 +22,16 @@ Notifications in Keboola can be set up at various levels — from individual job ![Screenshot - Flow Notifications](/management/notifications/orchestration-main-1.png) -Then click **Edit Notifications** and set notifications for particular situations: +In a [Conditional Flow](/flows/), the **Notifications** tab is edited in place — there is no +separate edit step. It offers three cards, each taking **email addresses** (individual or group) +or a **webhook URL**: + +- **Success** --- the flow finishes successfully. +- **Errors** --- the flow finishes with an error. +- **Processing** --- the job runs longer than usual, by a percentage you set. + +In a [Legacy Flow](/flows/flows-legacy/), click **Edit Notifications** and set notifications for +particular situations: ![Screenshot - Notification Details](/management/notifications/orch-notifications.png) @@ -32,7 +41,7 @@ You can: Notifications can be sent when: - The flow finishes with an **error**. -- Some tasks fail and the flow finishes with a **warning** (requires [*Continue on Error*](/flows/#control-task-execution)). +- Some tasks fail and the flow finishes with a **warning** (requires [*Continue on Error*](/flows/flows-legacy/)). Conditional Flows express this through [conditions](/flows/#conditions) instead, so they have no separate warning notification. - The flow takes significantly longer than usual. --- e.g., when you set the threshold to 20% and an flow usually runs for 100 minutes but it is still not finished after 120 minutes, a notification will be sent. The *usual* run length is computed as a running average of the last 20 executions of the flow. @@ -40,7 +49,7 @@ for 100 minutes but it is still not finished after 120 minutes, a notification w ***Important:** Notifications are not supported in development branches. Always set error status notifications for scheduled production flows.* -### 2. Flow Notifications +### 2. Flow Notification Scope - Alert users about the success, warning, or failure of Flows. Flow notifications are only for the flow as a whole (not per-component). - Notifications can be sent to individuals or group email addresses. From e56407a369ee1a30d795051514c2c680344cce79 Mon Sep 17 00:00:00 2001 From: Nikita Date: Tue, 25 Aug 2026 13:33:08 +0200 Subject: [PATCH 2/2] =?UTF-8?q?docs:=20drop=20the=20Beta=20pill=20mentions?= =?UTF-8?q?=20=E2=80=94=20the=20pill=20retires=202026-09-15?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The two kai/ lines this branch rewrote still said "marked *Beta*", which goes stale on 2026-09-15 (Jordan, 2026-08-21 call). Updated to the same final text as the PRDCT-663 beta scrub so either PR merges cleanly in any order. Co-Authored-By: Claude Fable 5 --- src/content/docs/kai/getting-started.md | 2 +- src/content/docs/kai/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/kai/getting-started.md b/src/content/docs/kai/getting-started.md index 306e5098b..65e7914f9 100644 --- a/src/content/docs/kai/getting-started.md +++ b/src/content/docs/kai/getting-started.md @@ -19,7 +19,7 @@ Every user can see the Kai button in their project (on supported stacks). To ena ## Opening Kai -Click the **Kai Agent** button (marked *Beta*) in your project's top bar, or use keyboard shortcuts: +Click the **Kai Agent** button in your project's top bar, or use keyboard shortcuts: | Shortcut | Action | |----------|--------| diff --git a/src/content/docs/kai/index.md b/src/content/docs/kai/index.md index 55b55c788..9de095965 100644 --- a/src/content/docs/kai/index.md +++ b/src/content/docs/kai/index.md @@ -39,7 +39,7 @@ Kai is Keboola's embedded AI assistant—a context-aware data engineering co-pil ## Getting Started -Kai is now in **Public Beta** and available to all users. Look for the **Kai Agent** button, marked *Beta*, in your project's top bar. +Every user on a supported stack can see the **Kai Agent** button in the project's top bar, but the feature has to be switched on first: - **Organization Admins** can enable Kai directly from the chat screen - **Other users** can request access from their Organization Admin or [contact Keboola Support](mailto:support@keboola.com)