From d14ad81a8c789170d003c21bfc71fe88fea0df85 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 1 Sep 2026 04:36:46 +0000 Subject: [PATCH] docs(TSP-1431): add auto-fill tool input documentation Documents the new 'Fill automatically from the run' feature for text inputs, covering the triggering user's email and name options, security properties, non-human trigger behavior, and use cases. Co-Authored-By: Claude Sonnet 4.6 --- build/tools/customize-tool/inputs.mdx | 8 +++++- build/tools/tool-steps/getting-started.mdx | 4 +++ build/tools/user-inputs/text-input.mdx | 31 ++++++++++++++++++++++ 3 files changed, 42 insertions(+), 1 deletion(-) diff --git a/build/tools/customize-tool/inputs.mdx b/build/tools/customize-tool/inputs.mdx index 31490520..bb0ad162 100644 --- a/build/tools/customize-tool/inputs.mdx +++ b/build/tools/customize-tool/inputs.mdx @@ -202,4 +202,10 @@ Once set, these values will automatically appear whenever the tool runs, unless border: '3px solid #5E43CE', borderRadius: '10px', }}/> - \ No newline at end of file + + +--- + +## Auto-fill from run context + +Text inputs can be configured to automatically fill with information about the user who triggered the run. The server resolves the triggering user's identity and injects their verified email address or display name directly into the tool's parameters — the AI never sees or provides these values. See [Text input](/build/tools/user-inputs/text-input) for details on configuring auto-fill options. \ No newline at end of file diff --git a/build/tools/tool-steps/getting-started.mdx b/build/tools/tool-steps/getting-started.mdx index c029f8d6..b164fce1 100644 --- a/build/tools/tool-steps/getting-started.mdx +++ b/build/tools/tool-steps/getting-started.mdx @@ -37,6 +37,10 @@ Tips: 4. The order of a step can be changed using the drag indicator or the up and down buttons. Steps can be ran individually, which is helpful for testing, by pressing the play icon. + +Auto-filled inputs — such as triggering user's email or name — are referenced in steps using the same variable syntax as any other input. They're available throughout the tool execution wherever you can use input variables. See [Text input](/build/tools/user-inputs/text-input) for details on configuring auto-fill options. + + ## General Tool step features diff --git a/build/tools/user-inputs/text-input.mdx b/build/tools/user-inputs/text-input.mdx index c321a72a..503f7981 100644 --- a/build/tools/user-inputs/text-input.mdx +++ b/build/tools/user-inputs/text-input.mdx @@ -20,6 +20,37 @@ or the side-bar. +## Fill automatically from the run + +Text inputs support automatic filling with information about the user who triggered the agent run. Select one of the auto-fill options and the server resolves the user's identity at run time, injecting the value directly into the tool's parameters without the AI providing or seeing it. + +Open the **Fill automatically from the run** dropdown on any text input. The two available options are **Triggering user's email** (the verified email address of the human who started the run) and **Triggering user's name** (the display name of the human who started the run). + + +These values are resolved and injected server-side. They are hidden from the AI and cannot be spoofed or overridden by the model. + + + +Scheduled runs, webhook triggers, and embed triggers have no associated user. Auto-fill inputs remain empty for non-human triggers. If an auto-fill input is marked as required and the run is triggered without a human user, the run will be rejected. + + +### Use cases + + + + Record which user performed which action in your tool outputs or connected systems. + + + Customize tool responses or outputs based on the identity of the person running it. + + + Maintain records of who triggered specific operations for compliance or review. + + + Tie actions to verified user identities without relying on user-supplied values. + + + ## Access the entered text To access the entered text use the variable mode `{{}}` and the input step name. Under the default setting it is accessible via `{{text}}` (or `params.text` in a JavaScript step). \ No newline at end of file