# Creating reactors

## Creating a reactor <a href="#event_type_name" id="event_type_name"></a>

To create a new reactor, navigate to the Reactors screen in the Loyalty Console and click the **Create** button.

<figure><img src="/files/0QziaDcNwaN0MmurGOOA" alt="" width="375"><figcaption><p>Create reactor screen in the Loyalty Console</p></figcaption></figure>

#### When creating a reactor, you’ll need to configure the following:

1. **Name & description:** Provide an internal name and brief description for the reactor’s purpose. These are for internal use only and won’t be visible to end-users. Reactor names do not need to follow the naming convention of event types.
2. **Event trigger:** Select the [event type](/product/loyalty-engine/events/event-types.md) that should trigger the reactor by clicking the cog icon in the Event Trigger block.\
   &#x20; ![](/files/Y2A4sPU3jWRmuUpBkZw2)
3. **Start & end date:** Set the time period during which the reactor will process incoming events.
   1. You can modify the start date/time until the reactor becomes active, but once the end date has passed, the reactor cannot be edited or reactivated.
   2. If needed, you can use the clone function to recover a previous configuration.
4. [**Activation limits**](/product/loyalty-engine/reactors/activation-limits.md)**:** Specify how many times the reactor can trigger, either per user or across all users in the program.
5. [**Conditions**](/product/loyalty-engine/reactors/conditions.md)**:** Define any criteria the event or user must meet for the reactor to trigger the specified reacti
6. [**Reactions**](/product/loyalty-engine/reactors/reactions.md)**:** Select the actions that should occur when the reactor is successfully triggered.

{% hint style="danger" %}
Once a reactor is created, any future edits will result in the original reactor being ended and a new reactor being created.

**This resets the activation history,** meaning users who previously triggered the reactor can activate the newly created one again if activation limits are in place (e.g., one activation per user).

See [Managing reactors](/product/loyalty-engine/reactors/managing-reactors.md#editing-a-reactor) for more information.
{% endhint %}

{% hint style="info" %}
To create more advanced reactors that require multiple events to occur before triggering, refer to our tutorial [Create advanced or multi-event reactors using Audiences](/product/loyalty-engine/reactors/reactor-tutorials/create-advanced-or-multi-event-reactors-using-audiences.md).
{% endhint %}

***

## FAQs

#### Can a reactor be triggered by multiple event types?

This effect can be achieved by following our tutorial [Create advanced or multi-event reactors using Audiences](/product/loyalty-engine/reactors/reactor-tutorials/create-advanced-or-multi-event-reactors-using-audiences.md).

#### Are there any considerations or mitigations to avoid potential abuse or misuse?

There may be members who seek to find and exploit loopholes in your loyalty program setup. For example a promo code reactor giving members 500 points when they enter the promo code is open to abuse if you don't set a [reactor subject activation limit](/product/loyalty-engine/reactors/activation-limits.md#subject-activation-limit).

The Loyalty Engine offers a number of features which can be used to deter malicious members, such as [activation limits](/product/loyalty-engine/reactors/activation-limits.md#activation-limits), [reactor](/product/loyalty-engine/reactors/conditions.md) & [reward availability](/product/loyalty-engine/rewards-and-points/rewards/reward-availability.md) constraints and [points earning & spending caps](/product/loyalty-engine/rewards-and-points/points/points-earn-spend-and-balance-caps.md).

You can learn about more about these features, and techniques to reduce the likelihood of fraud and abuse, in our [Preventing fraud & abuse guide](/product/loyalty-engine/rewards-and-points/reward-tutorials/preventing-fraud-and-abuse-guide.md).


---

# Agent Instructions: 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:

```
GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/reactors/creating-reactors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.