Overview of Events When Working with Recurring Deals
Events allow applications to respond to changes in almost real-time: receiving notifications about the creation, update, or deletion of recurring deals, as well as when new deals are automatically created based on recurring deal templates.
Detailed information on working with events is described in the article Concept and Benefits of Event Processing.
Quick navigation: all events
How to Receive Events
You can subscribe to recurring deal events through:
- outgoing webhook
- application and the method event.bind
An example of a handler code for the event is described in the article How to Test Your Handler for Processing Bitrix24 Events.
Server Availability for Sending and Receiving Events
The event handler server must be accessible from the outside. To configure the accessibility of the event handler server and application, refer to the article Required network access.
For cloud Bitrix24, no additional configuration is required. For on-premise Bitrix24, configure accessibility on the server or hosting according to the article Required network access.
Overview of Events
Scope:
crmWho can subscribe: any user
|
Event |
Triggered |
|
When a new recurring deal is created manually or via the method crm.deal.recurring.add |
|
|
When a recurring deal is modified manually or via the method crm.deal.recurring.update |
|
|
When a recurring deal is deleted manually or via the method crm.deal.recurring.delete |
|
|
When a new deal is automatically created based on a recurring deal template or via the method crm.deal.recurring.expose |