> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ergoly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Events

> Everything that makes a worker act. Each one ends with an answer back where it came from.

An **event** is something that happens in a channel. Every event starts the worker working on one thing, and when it is done, the answer goes back to where the event came from. These are all of them.

<table>
  <colgroup>
    <col width="166" />

    <col width="381" />

    <col width="317" />
  </colgroup>

  <thead>
    <tr>
      <th>Event</th>
      <th>What starts</th>
      <th>Where the answer goes</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>A mention</td>
      <td>An @-mention in a channel the worker is set up in.</td>
      <td>A thread under the message.</td>
    </tr>

    <tr>
      <td>A message</td>
      <td>A message with no mention, in a channel where the worker is set to answer everything. With listening on, it reads but does not reply.</td>
      <td>A thread, or nowhere.</td>
    </tr>

    <tr>
      <td>A DM or group DM</td>
      <td>Any message, from someone it may talk to.</td>
      <td>The same DM.</td>
    </tr>

    <tr>
      <td>A queued message</td>
      <td>A message sent while it was busy, handled once it is free.</td>
      <td>A thread under that message.</td>
    </tr>

    <tr>
      <td>A button press</td>
      <td>Someone presses Approve, Reject, or another button the worker posted.</td>
      <td>The same thread, with the decision recorded.</td>
    </tr>

    <tr>
      <td>A scheduled task</td>
      <td>A task fires on its schedule.</td>
      <td>The channel or person the task names; otherwise only the task's log.</td>
    </tr>

    <tr>
      <td>A task change</td>
      <td>A task is handed to the worker, commented on by a person, or changes state.</td>
      <td>The task's log, and Slack if the task says so.</td>
    </tr>

    <tr>
      <td>A hook delivery</td>
      <td>Another system posts to the worker's hook.</td>
      <td>The channel or DM the hook names.</td>
    </tr>

    <tr>
      <td>Its first day</td>
      <td>A newly built worker sends its first DM to the person who created it.</td>
      <td>That DM.</td>
    </tr>
  </tbody>
</table>

Not events: an email arriving (receiving is not live), a trigger from a connected tool (not available yet), or someone opening control.

> [!NOTE]
>
> **Worth knowing.** A worker works on one event at a time. A second event in the same place waits; events in different places, for different clients, run on different copies and do not wait for each other.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.