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

# System event block

> Share activity data with external systems.

*30 July 2026 · Orchestration*

Campaigns in Nexus can already react to what customers do. With the **System event block**, they can now also react to what happens to your activities themselves. When an offer, challenge or game is created, updated, published or unpublished, its details can be sent to an external system automatically.

## Examples

* An offer is published → your CRM receives its details, and the launch email goes out on time
* Offers are created or updated → an external campaign calendar stays in sync, without manual exports
* An activity is unpublished → a connected system is told to stop dependent communications

![A flow that starts with a System event block for an updated offer, connected to an Outbound API block named Send Offer data to CDP](https://mintcdn.com/lobyco-4c9fb3ad/8XKQyo6M7ttG0QMR/images/release-notes/2026-07-30-system-event-block-01.png?fit=max\&auto=format\&n=8XKQyo6M7ttG0QMR\&q=85\&s=47cb2b08ef39ae9e606919fe7434f7d3)

***

> **Available on request.** The System event block is designed for technical setups: it is visible to administrator users only and is enabled per client environment. Reach out to your Integration team if you'd like to use it.

[Read the full guide: System event block](https://help.lobyco.com/business-documentation/campaigns/orchestration-canvas/block-reference.md#system-event)


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