Lifecycle hooks

Trigger general actions at the start, end, or escalation point of your NLX conversations

This feature is currently available to enterprise tiers only.

What's a Lifecycle hook?

Lifecycle hooks allow you to send or receive data or trigger an event at particular stages (lifecycles) in a conversation session. They are also useful in receiving data from another system and setting Context variables at 'start' lifecycle of a session.

• Lifecycle hooks are only executed during specific points in a conversation: at the start of a conversation, at an escalation point within the conversation, at the end of a conversation, or to stream state modifications made to Data requests. Data requests and Actions, on the other hand, allow you to be granular about when and where to trigger the operation within a flow

• Lifecycles are attached to an application rather than referenced in a flow, which is why you don't encounter them when building flows in the Canvas

To access, click Resources in your workspace menu and choose Lifecycle hooks:

Need more context? See Application lifecycle

---

Requirements

A Lifecycle hook must always employ the following to function:

• static response or external integration

• attached to an application under the Lifecycle tab

---

Lifecycle hooks features

Implementation

---

Lifecycle hook settings

A Lifecycle hook's Settings tab provides a few options:

• Description: Enter or modify an explanation of the resource for better filing and organization in the workspace

• Tags: Add or remove Resource tags for better filing and organization in the workspace

To delete a Lifecycle hook, select the Delete option under Danger zone. If the Lifecycle hook is assigned with an application(s), remove the lifecycle hook, and create a new application build/re-deploy to experience the change.