> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/actions-in-rewst/transform-actions/trim-variable-transform-action.md).
# Trim variable transform action
## Use case
You have a string that has been grabbed from an API return, however due to bad formatting the string starts or ends with extra spaces that need removed.
## Overview
Trim whitespace characters from a variable.
## Parameters
| Parameter | Description | Required |
|---|
| Variable Contents | Variable to trim | true |
## Usage
Example: Trimming a string
**Variable Contents:** This is a test starting and ending with 3 spaces each
## Results output
Result of Example:
```
"This is a test starting and ending with 3 spaces each"
```
In the above return the `"` characters were kept to show the spaces being removed. These would not be present in the actual return. Only the original string without whitespaces would be returned.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rewst.help/documentation/automations/actions-in-rewst/transform-actions/trim-variable-transform-action.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.