> For the complete documentation index, see [llms.txt](https://docs.fuul.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fuul.xyz/fuul-mcp-server/managing-triggers/editing-triggers.md).

# Editing Triggers

A **trigger** defines the on-chain or off-chain action that qualifies a user for a reward — for example, a token swap, a liquidity deposit, or a custom off-chain event. Each trigger is associated with a contract (for on-chain events) and configured with expressions that determine how volume, revenue, and currency are extracted from the event.

{% hint style="info" %}
This guide covers editing existing triggers. To create new triggers or delete existing ones, see [Creating & Deleting Triggers](/fuul-mcp-server/managing-triggers/add-and-remove-triggers.md).
{% endhint %}

{% hint style="warning" %}
Changes made via MCP are saved as **drafts**. They do not take effect in production until you go to **app.fuul.xyz → Incentives → Publish**.
{% endhint %}

## 1. Find your project and triggers

> "Find my project called Fuul and list our current configured triggers"

## 2. Edit trigger name and description

You can update the display name and description of any trigger:

> "Rename the \[trigger name] trigger to \[new name]"

> "Update the description of \[trigger name] to \[new description]"

| Field         | What it controls                                       |
| ------------- | ------------------------------------------------------ |
| `name`        | Display name shown in the dashboard and incentives hub |
| `description` | Human-readable description of what the trigger tracks  |

## 3. What you cannot change via MCP

### Contract address

The `token_address` and `chain_id` of an existing trigger **cannot be modified via MCP** (or from the dashboard). If you need to point a trigger to a different contract, you must delete the existing trigger and create a new one with the correct address. See [Creating & Deleting Triggers](/fuul-mcp-server/managing-triggers/add-and-remove-triggers.md) for the full replace-trigger flow.

## 4. Publish to production

After editing, **draft changes are not live until published**:

1. Open [app.fuul.xyz](https://app.fuul.xyz)
2. Navigate to your project → **Incentives**
3. Click **Publish**

All trigger changes will take effect immediately after publishing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fuul.xyz/fuul-mcp-server/managing-triggers/editing-triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.