Event Handlers can trigger external actions on which of the following events?

• A. Contract updated
• B. Documents stored
• C. Contract created
• D. Status changed

Answer: (C)

Event Handlers are designed to fire when a contract hits a specific lifecycle event so you can push data to external systems at that moment. Triggering actions at the moment a contract is created is ideal because the contract record exists with a unique ID and the initial metadata is firmly established. This lets downstream systems initialize correctly—creating related records, starting workflows, or notifying other apps—before any changes or updates occur. It also ensures the action runs once per contract, avoiding duplicates that could happen if you waited for updates or other events.

Other events like updates, status changes, or documents being stored can occur multiple times or under varying conditions, which can complicate external actions—leading to duplicates or inconsistent states unless you add extra safeguards. If you need to respond to those events, you’d typically use different automation approaches or implement idempotent logic, but for a clean, single, reliable trigger, the creation event is the most straightforward and reliable choice.