> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/core/events/topics.md).

# How event topics work

Reference for Mechanic event topics — Shopify webhook events, scheduled events, user-triggered events, and custom event topics.

To make events easy to identify, each event has a **topic**. Tasks signal their interest in specific event topics using [**subscriptions**](/core/tasks/subscriptions.md).

A topic looks like "shopify/customers/create", and it has three parts:

* The **domain** describes the source of the event. Shopify events have "shopify" as their domain, and events generated by Mechanic itself use "mechanic".
* The **subject** describes the type of resource the event describes. Events that are about customers have "customers" as their subject, and events that are about orders have "orders".
* The **verb** describes what has just occurred. Events that are about creating resources generally have "create" as their verb, and events that are about deleting resources generally have "delete".

{% hint style="info" %}
[Looking for the event topic list? Start here.](/platform/events/topics.md) Need Shopify topics? Jump to [Shopify](/platform/events/topics.md#shopify).
{% endhint %}

## User-defined topics

The User event domain is for custom, user-generated events, having any subject and verb (e.g. "user/foo/bar"). As with all events, a User event topic must use the standard three-part topic form, but only the "user/" prefix is mandatory.

Mechanic allows developers several ways to generate custom User events:

* The [Event action](/core/actions/event.md) can be used with any User event topic
* [Mechanic webhooks](/platform/webhooks.md) may be configured to generate events using any User event topic
* [Custom Shopify webhooks](/platform/shopify/custom-webhooks.md) deliver Shopify webhook events onto a User event topic, with optional filtering and payload customization. For these events, `event.topic` is the `user/...` topic and `event.shopify_topic` stores the source Shopify topic; on native Shopify deliveries, those two values match.


---

# 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://learn.mechanic.dev/core/events/topics.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.