> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/v2-1/essentials/events.md).

# Events & Listeners

## Emitting Events

You can emit events from [Actions](/v2-1/essentials/actions.md), [Templates](/v2-1/essentials/templates.md), and JavaScript.

### Actions

Using the `emit` method:

```javascript
function someAction() {
    emit( "taskAdded" );
}
```

You can provide arguments to all listeners by passing an array as the second argument.

```javascript
function someAction() {
    emit( "taskAdded", [
        "some task",
        now()
    ] );
}
```

{% hint style="info" %}
When emitting events, arguments must be passed as an array to ensure proper positioning both within CFML and JavaScript.
{% endhint %}

### Templates

Using the `$emit()` method:

```markup
<button wire:click="$emit( 'taskAdded' )">
```

### JavaScript

Using the global `cbwire.emit()`:

```xml
<script>
    cbwire.emit( 'taskAdded' );
</script>
```

## Listeners

You can register event listeners on a Wire by defining `listeners`.

```javascript
component extends="cbwire.models.Component"{
    
    listeners = {
        "taskAdded": "clearCache"
    };

    function clearCache(){}
}
```

{% hint style="info" %}
The `clearCache` method will be invoked when a `taskAdded` event is emitted.
{% endhint %}

{% hint style="warning" %}
JavaScript keys are case-sensitive. You can preserve the key casing in CFML by surrounding your listener names in quotations.
{% endhint %}

### JavaScript

Listening to events that you emit in your [Actions](#actions) can be done using `cbwire.on()`.

```html
<script>
    cbwire.on( 'taskAdded', task => {
        console.log( 'A task was added. ');
    })
</script>
```


---

# 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://cbwire.ortusbooks.com/v2-1/essentials/events.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.