Creating an event

Define an application event, its data, and the available ways to react.

Open the application Events section.

How to add an event

An event tells Senler what happened in your application, such as an order payment or a closed deal. An agent can react to it, and a plugin event can also start an automation. The project user connects the required response; creating an event in the application does not start processing by itself.

Events can be declared by Website integration and Plugin applications.

1. Open the form

Open Events and select Add. The new event page opens.

2. Name the event for the user

In the user presentation block, enter the title and short description on the Russian tab, then enter the English title and description on the English tab. The user sees the version matching the interface language.

3. Set the system name

Enter the system name that the application sends through the API, for example payment.paid.

In Where the event is available, select at least one option:

• Agent reaction — the user can add the event to their agent;
• Automation start — for a plugin, the event appears among triggers for For dialogs automations.

Both options can be enabled. The separate agent description is shown only when agent reaction is enabled.

If the fact needs different wording for the agent, enable a separate technical description and enter the agent text.

4. Describe the event data

If the event carries data, in the Event data block, select Add field.

In each field card, enter a name, use the type field to select a type option. On the Russian and English tabs, enter the Russian and English description, then enable Required when needed. The remove action removes an unnecessary field. Leave the block empty when the event has no additional data.

5. Save the event

Select Save. Cancel returns to the list without changes.

Editing and deletion

On the Events page, select Add for a new event or choose an existing event from the list. Use the edit action to change names, descriptions, or the data schema. After changing the schema, make sure the application sends data in the new format.

When an event is no longer used, choose the delete action. Check the event in the confirmation before confirming its deletion. It is immediately removed from every agent subscription, and new calls using that system name are rejected. It also becomes unavailable to automations. Check workflows that used the event and replace their trigger.