> 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/defang-transform-action.md).

# Defang transform action

## Use case

You have a email with a URL in it similar to something like:\
<https://rewst.io/aprilfools/surprise.html\\>
You would like to defang it and make it not directly usable.

## Overview

Given a URL, this action will 'defang' the url by adding characters to prevent it from being directly usable.

## Parameters

<table><thead><tr><th width="217">Parameter</th><th width="417.3333333333333">Description</th><th data-type="checkbox">Required</th></tr></thead><tbody><tr><td>URL</td><td>URL to defang</td><td>true</td></tr><tr><td>Colon</td><td>If true defang colons.</td><td>false</td></tr><tr><td>Dots</td><td>If true defang all dots.</td><td>true</td></tr></tbody></table>

## Usage

<details>

<summary>Example 1: Defang the url https://rewst.io/aprilfools/surprise.html</summary>

Inputs:

Colon: True

Dots: True

URL: <https://rewst.io/aprilfools/surprise.html>

</details>

## Results output

The expected result of this transform is a defanged url.

Result from Example 1:

```
hXXps[:]//rewst[.]io/aprilfools/surprise.html
```


---

# 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/defang-transform-action.md?ask=<question>&goal=<user_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.