Using the WebUI — workflows (/workflows)
Any screen not listed here does not exist. Headings quote the screen's own wording.
Part of the workspace guide. Other topics:
conversations, the input box, and sign-in: references/webui.md;
documents, files, tables, memory, channels, and apps: references/webui-workspace.md;
editing a file in place (「編集」): references/webui-file-edit.md;
SIROE pages, blocks, and boards: references/webui-siroe.md;
settings, administration, models, and triggers: references/webui-settings.md;
external service connections: references/webui-connections.md;
/office: references/webui-office.md;
/meetings: references/webui-meetings.md;
/calendar: references/webui-calendar.md.
「ワークスペース」 — workflows
| Where | What you can do |
|---|---|
/workflows |
「ワークフロー」 (sidebar 「エージェント」 group). A workflow is a fixed sequence of steps (ステップ) that runs exactly as written — unlike a skill, the model does not decide the order. Cards show the name, 「公開中」 or 「下書き」, the last run's status, and which 自動実行 types start it. Check cards and press 「まとめてゴミ箱へ移す」 to move several to the trash (only ones you created, or any as an admin; the confirmation says how many). A workflow is visible only to its creator at first (公開範囲 「自分のみ」); its 公開範囲 can be widened to 「グループ」 or 「テナント全体」 from the editor's header (below), or by asking in chat (「このワークフローを営業グループにも見せて」, 「自分だけに戻して」; an approval card asks first). Others see a workflow only when its 公開範囲 reaches them; manager-or-above see all. Each card shows its 公開範囲 (「自分のみ」, 「グループ」, 「テナント全体」) and its labels: pressing a label narrows the list to workflows carrying it (several labels narrow to those carrying all), and the box above the cards (「請求書、日報」) narrows by words in the name or description. The card's 「…」 (or a right-click) has 「開く」「表示名を変更」「説明を変更」「アイコンを変更」「ラベルを変更」; the four changes are for the creator and admin-or-above, others see them greyed out with the reason. Clicking a card opens its editor; clicking its 「最後の実行: …」 line opens that run's screen (handy for a run waiting for approval or a failed one). When empty, four buttons: 「新規作成」 (creates an empty draft named 「新しいワークフロー」 with one blank step to fill in, and opens its editor right away — no dialog), 「テンプレートから作る」 (4 templates: 「テーマを Web で調べて Markdown にまとめる」 (researches a theme on the web and writes it up as Markdown with sources; nothing is saved as a file)、「質問に AI が答える」「Webhook を受けて振り分け」, and 「ミーティングの議事録を通知先へ送る」, which starts when a meeting's minutes are finalized), 「スキルから作る」 (turns a skill's procedure into steps; the skill's detail has the same as 「ワークフローを作る」), and 「チャットで作る」 (opens a new chat with 「〜のワークフローを作って」 in the input box; in any chat, 「さっきの作業をワークフローにして」 turns what was just done into a workflow). When the AI in a chat creates or edits a workflow, the chat shows a card for the saved version: the name, 「バージョン N を作りました」 or 「バージョン N に更新しました(追加 1・変更 1)」, and a read-only canvas of the steps where steps added or changed since the version before carry 「追加」 / 「変更」 (removed ones are listed under it as 「削除: …」); a save that changed nothing says only 「変更はありません。」, and 「開く」 on the card opens the editor (not shown in the editor's own side chat). Only the latest card per workflow stays in the conversation. If a step needs a service that is not connected, the AI shows 「連携できるサービス」 with 「追加」 before saving. Once some exist, 「作成」 at the top has those four plus 「ボットから作る」 (creates one step that hands the run's 依頼 to the bot — the 依頼 is typed when running, and the bot's example prompts go into that field's description; disabled bots are not offered). The meeting template asks for the 通知先 and 「タイトルに含む語」, then 「作成して有効にする」 creates the workflow, publishes it and turns its trigger on in one step (visible to the creator only; widen it later in 自動実行 settings). Pressing 「作成して有効にする」 counts as approving the publish. The other three templates just create a draft. In the editor's step list, 「つなぐ」 has 「通知先へ送る」: pick a 通知先 registered in 「設定」→「通知」, write the 「本文」 (the only part Slack and other chats show); 「一緒に送る値(任意)」 is folded by default — open it to add JSON fields that a webhook receiver such as your own server gets alongside the 本文 (Slack ignores them). It sends one message and calls no model. Anything created starts as a draft. A person can run the draft from the workflow's screen, and chat can run it after an approval card; unattended starts (自動実行, another conversation, a workflow called from another workflow) always use the published version. The workflow's 「実行」 tab has one run button: once published, pick 「公開バージョン」 (the default) or 「下書き」 first, and the button reads 「公開バージョンで実行」 or 「下書きで実行」 (the saved draft; unsaved edits block it); the fields come from the picked version's input. Below it, 「最近の実行」 lists past runs, each labelled with what started it (「手動」, 「定期実行」, 「外部から起動」, 「出来事で起動」, 「チャットから」, 「別のワークフローから」, 「アプリから」, 「公開フォームから」, or 「ステップのテスト」). A field that takes a file shows 「ファイルを選ぶ」: the picked file is uploaded at once to the person's own files and shown as a name chip with an × to remove it (「別のファイルを選択」 picks another); a field that takes several files shows 「ファイルを追加」, up to 20 in all (beyond that: 「ファイルは 20 件まで選択できます」); the run button stays disabled while a file is uploading or a required file is not picked. A file the person cannot open, or one hidden from AI, is refused when the run starts. In a trigger's 「ワークフローに渡す入力」 and on the 公開フォーム the same field is a plain text box, with no file picker. Below come 「最近の実行」 and the picked run's per-step record (status, time, 入力 / 出力 / error, and for a code step the console.log and print lines under 「ログ」; a too-large output says 「一部だけ表示しています」; repeated steps fold into one row). A 「承認・入力を待つ」 step shows a card there and on the run's screen (「実行の画面を開く」; it is titled with the workflow's name, shows the status and 「中止」 / 「やり直す」 at the top, and 「編集に戻る」 goes back; a waiting step is marked 「待機中」 on its canvas) with 「承認」 / 「却下」 (reason optional). A 「承認・入力を待つ」 step with 承認者 picked is decided by those approvers, not on this screen: the card reads 「承認依頼で待っています(〇〇さんほか)」 with no buttons, the approvers get an approval-request email and approve or send it back from the email or their own 「受信トレイ」, and the wait does not go to the starter's 「受信トレイ」. In any run except one a 公開フォーム started (the run button, 「このステップを試す」, 「やり直す」, 自動実行, another workflow, chat), when the AI in an 「エージェントに任せる」 or 「スキルを実行」 step tries an action that needs approval, the same approval card as in chat (「承認して実行」 / 「拒否」) shows on the run's screen, only for the person who started the run; it also reaches their 「受信トレイ」 as 承認待ち and as a push notification, both opening the run's conversation, where the same card can be answered; the step waits up to 20 minutes, and a refusal or timeout does not fail the step (the AI carries on without that action). Runs a 公開フォーム started and an 「エージェントに任せる」 step with a ボット picked still refuse such an action without asking — put it in its own step instead.Files a step made and the browser a step drives show only for the person who started the run: on the run's screen, 「キャンバス」 / 「成果物」 above the canvas swaps it for the same 成果物 list as chat (open a file to view and edit it), and while a step drives a browser a 「ブラウザ」 choice appears with the live view (it switches there by itself when a browser starts during the run); in the 「実行」 tab, the picked run has 「成果物を開く」 and 「ブラウザを見る」, which open the same view full screen. On a wide screen the run's step record sits in a column right of the canvas, headed 「実行の記録」; 「キャンバスに重ねる」 there makes it a card at the canvas's bottom right (top-left corner resizes, top edge moves), and 「右の列に戻す」 puts it back. A 「影武者を呼び出す」 step likewise shows 「〇〇さんの影武者の答えを待っています」 (just 「影武者の答えを待っています」 when the owner's name cannot be looked up) with the question and no buttons; the run moves on once the bot's owner confirms the answer. 「中止」 while running, 「やり直す」 after (same version and input). A failed run also has 「失敗したステップからやり直す」: steps that succeeded are not run again (their record says 「前の実行の結果を使いました」), so an email already sent is not sent twice; a step whose output was too large to keep whole runs again. Only the creator and manager-or-above can run, decide, or cancel; others still see those buttons, greyed out, and pressing one shows why. The person who started a run gets its approval wait in 「受信トレイ」. Testing one step: on the editor's step tab, below the settings, 「このステップを試す」 runs only the selected step of the saved version. The JSON box lists the names the step reads (earlier steps' outputs and input); the values written there stand in for them, then 「試す」 (blocked while there are unsaved edits). The run shows below and stays in 「最近の実行」 labelled 「ステップのテスト」; it does not count as the card's last run, and outside actions (sending email etc.) really happen. A step can carry a メモ (sticky note): in the editor's step tab, 「メモを追加」 opens a 「メモ」 box with bold / italic / strikethrough / bullet buttons, six colors (黄・青・緑・橙・紫・灰), and 「ファイルを添付」 (or paste / drop a file, up to 20 MiB each): an image (PNG・JPEG・GIF・WebP, shrunk before upload) shows inside the note, and a sample file (Word / Excel / PowerPoint / PDF / text such as csv・md・json / HTML) becomes a link with its name that downloads it; a pasted URL becomes a link. The note shows as a sticky to the right of the step on the canvas (also on the run's screen and the chat card, read-only); pressing the sticky selects its step. 「メモを外す」 removes it. Up to 4,000 characters; images from outside URLs are refused on save. The note is part of the version (editing it makes a new version to publish) and runs ignore it. Files attached to a note can be opened by anyone who can see the workflow; they do not appear in 「ファイル」 or its search, and are deleted with the workflow after it has sat in the trash past the retention period |
/workflows/ — the header |
Steps are drawn on a canvas. A wide screen lists the step kinds left of it (with a search box): press one to add it after the selected step (or at the end), or drag it onto a 「+」 spot; narrow screens use 「ステップを追加」. The top node shows the trigger (「手動で実行」 if none) and opens the 「トリガー」 tab. 「保存」 saves a new version. On the canvas, a step can be dragged: while dragging, the 「+」 spots it can go to light up, and dropping it on one moves the step there (into a group's head too); the layout stays automatic, so a step cannot be left at a free position. The buttons at the canvas's bottom left zoom in / out, fit the whole flow, and 元に戻す / やり直す; a minimap at the bottom right pans the view (hidden on narrow screens). On a wide screen, the border between the canvas and the right-hand panel can be dragged (or moved with ←/→) to change their widths; the width is remembered on that device and shared with a run's screen. While the editor is open, the left sidebar folds into its icon column (it opens again on leaving, unless the person opened or closed it themselves meanwhile). Keys: with a step selected, Backspace or Delete removes it (a toast says 「⌘Z で元に戻せます」); ⌘Z undoes, ⇧⌘Z (or Ctrl+Y) redoes, ⌘S saves, Esc clears the selection; 「+」 / 「-」 zoom, 「0」 resets to 100%, Shift+1 fits the whole flow. While typing in a field, these keys act on the field instead (⌘S still saves). Undo reaches back only to the last save. Each step's 「設定」 (variables, value fields, connected-service actions, the AI's tools, code, containers, HTTP secrets, files) and the step kinds (カテゴリ分類, ファイルの加工, 承認・入力を待つ, 影武者を呼び出す) are in references/webui-workspace-workflows-steps.md. 「チャットで頼む」 opens a chat beside the canvas — your most recent conversation about this workflow, or a new one when there is none — in place of the tabs (input box: 「このワークフローについて頼む(/ でスキル指定)」) — the AI there edits this workflow, and the canvas shows the result; before the first message it lists three example requests that drop into the input box when pressed; press the button again to close it (the open chat stays in the URL as ?chat=). The header shows the 公開範囲 (e.g. 「自分のみ」); pressing it opens a selector to change it to 「自分のみ」, 「グループ」 (pick the group) or 「テナント全体」. Widening asks first (「公開範囲を…にする」 → 「変更する」): the people it then reaches can read the steps and the run records, while who can run and edit does not change. The workflow's トリガー (its 自動実行) move to the same 公開範囲 too, widening or narrowing — except one whose creator is not in the chosen group, which keeps its own; a notice says how many changed. Changing a trigger's own 公開範囲 does not move the workflow; when the trigger is wider, its edit form says that people outside the workflow's range cannot see the workflow or its run records. Only the creator and admin-or-above can change it; others see the selector greyed out with the reason. 「その他の操作」 also has the card's four changes (「表示名を変更」「説明を変更」「アイコンを変更」「ラベルを変更」). 「…」 (「その他の操作」) has 「スキルとして書き出す」: it shows a draft skill (name, description, procedure) made from the latest saved version. Nothing is saved from that window — to keep it, press 「チャットで頼む」 there, ask 「このワークフローをスキルにして」, and approve the AI's proposal. A skill is read by the AI, so the order is no longer guaranteed. Only the creator and manager-or-above can export; others see the item disabled with the reason. It also has 「ゴミ箱へ移す」 (creator and admins only, after a confirmation): the workflow leaves the list and its triggers stop starting it; 30 days later it is deleted with its versions and publish history, and it cannot be restored. A tenant can have up to 200 workflows outside the trash; at the limit, creating (from the screen or chat) is refused until one is moved to the trash. The same menu has 「外部公開」 — a 公開フォーム anyone can fill in without signing in: 「公開する」 turns the published version into a form and shows its URL (/wf/<公開 ID>) with a copy button. The dialog warns 「URL を知っている人は誰でも実行でき、費用はあなたに付きます」 — every submission runs as the person who published it, and is billed to them. The dialog's 「結果をフォームに表示する」 switch (off by default) chooses whether the visitor sees the result: off, a visitor sees only 「受け付けました」; on, the form stays on screen after sending, shows 「処理しています」, and then shows the last step's output as is (never the intermediate steps, inputs, or error details). A run that waits for a person's approval or input, or takes over 5 minutes, ends with a note that the result cannot be shown on that screen; closing the screen loses the result. Switching it while public keeps the same URL; too many submissions in a row are refused for a while (about 10 a minute from one place, 200 a day per workflow). While open, the header shows 「外部公開中」; 「公開を取り下げる」 in the same dialog, confirmed with 「取り下げる」, closes it; the URL then shows 「このフォームは見つかりません」, and publishing again issues a different URL. Moving the workflow to the trash closes its 公開フォーム too. The item is disabled without a published version, and for anyone but the creator and admin-or-above. Requests from a local agent (samuraiapp CLI or MCP) appear as yellow cards above the canvas: an agent may write the doc directly, but publishing and running a draft (including testing one step or retrying on a draft) wait for a person — 「手元のエージェント(CLI / MCP)が、バージョン N の公開を求めています」 (or 「試し実行」「ステップ「x」のテスト」「やり直し」) with 「却下」 and 「承認」. Approving publishes that version, or starts the run in the approver's name; the card leaves either way. Only people who can edit may decide a publish, only people who can run may decide a run; others see the buttons greyed out with the reason. A newer request of the same kind replaces an older one |
/workflows/ — 「バージョン」 tab |
Every save is a version (「バージョン N」), listed newest first with 「公開中」 / 「最新」, who made it (「手で編集」 / 「AI が編集」 / 「取り込み」 / 「テンプレートなどから作成」), and when. Only the newest 50 saves are kept; older versions are deleted automatically, except the published one and any a kept run record used. 「差分」 on a row lists the steps added / removed / changed / moved since the version before. Publishing: write an optional 「公開のメモ(任意)」 and press 「バージョン N を公開」 — the latest version becomes the one that unattended starts use; the memo shows on that row as 「公開のメモ: …」. Unsaved edits block it (save first), and when the latest is already published the memo field and the button are not shown — only a line saying it is published. 「バージョン N に戻す」 on an older row saves that version's steps as a new latest version (after a confirmation) — nothing is deleted, and the published version does not change until you publish again. Only the creator and admins can publish or revert; others see the buttons disabled with the reason |
/workflows/ — 「トリガー」 tab |
Start this workflow automatically. Four buttons: 「定期実行を追加」 (a time or repeat, Japan time, at most once an hour), 「外部トリガーを追加」 (a URL other systems call; the secret is shown only once, right after creating — copy it then), 「サービス連携を追加」 (an event in a connected service such as Gmail or GitHub), and 「アプリ内の出来事のトリガーを追加」 (an event inside the app: 「ミーティングの議事録が確定した」; the form's first step 「どの出来事で動かすか」 narrows it by the meetings' range, 「タイトルに含む語」, and 「ラベル」). A trigger runs the published version — with nothing published, it starts no run. Below, 「このワークフローのトリガー」 lists this workflow's triggers (「・停止中」 when stopped); 「詳細」 opens it in 自動実行 settings, where it is edited, stopped, or deleted; a workflow trigger's run writes no conversation — a run that succeeded gets a check mark beside 「実行済み」 once it ends, and the right side shows 「ワークフローを開く」 instead of a chat, since the record is in the workflow's 「最近の実行」. The creator and manager-or-above can add a 定期実行 or an アプリ内の出来事; 外部トリガー and サービス連携 need manager-or-above. Others see the buttons disabled with the reason. If the published version declares inputs, the add form has a step 「ワークフローに渡す入力」 with those fields; a required field must be filled to register (「〜を入れると登録できます」), and a trigger that misses one is refused. An 外部トリガー or サービス連携 sends what arrived as the input event, so that field is not asked |
「コーディング」 — /coding
| Where | What you can do |
|---|---|
/coding |
「コーディング」 (「エージェント」 group, beta). Give the AI a GitHub repository and an instruction; it codes in its own container and opens a pull request. First, 「GitHub を接続」 installs the GitHub App. Write the 「指示」, pick 「リポジトリ」 and 「ベースのブランチ」, then 「作業を始める」 (⌘ + Enter). Tasks below show status (準備中・作業中・確認待ち・完了・PR 作成済み・失敗・停止), branch and lines changed. A task (/coding/$taskId) shows the conversation beside 「ターミナル」 (each command, output and exit code; 「中断」 when it ended without one) and 「差分」. A message sent while it works becomes an extra instruction. 「停止」 stops it; 「PR #N を開く」 opens the PR. The header's coin button shows the estimated cost, split into 「モデル」 and 「サンドボックス」 (the container, incl. the wait until it sleeps). Not available in the demo |