Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The prehook is a middleware introduced to customize the payload before sending in the request to the intent nodes.

All the intent type requests except for launch, session end, listener event nodes can trigger the prehook nodes based on the configuration.

Pre Hook Request node

Before triggering the intent, the Pre Hook Request node will be triggered.

Name - Custom name given to the node.

Skill - The project name.

Intent - You can choose the intents for which this Pre hook request node should be triggered. The Prehook request node will be triggered for the intents listed in this field irrespective of the state.

Prehook handler

The basic code given below will handle the requests from the Prehook node.

Place the below code in the function node after the Pre Hook Request node.

msg.payload.handleRequest = false;
msg.payload.preHookData = {name: 'arun'};
return msg;

The msg.payload.handleRequest takes boolean values. This property decides if the content from the Prehook Request node should pass through to the corresponding intent.

  • If set to true, the corresponding intent will not get triggered. The Pre Hook Response node will act as a normal Response node.

  • If set to false, the Pre Hook Response node will trigger the corresponding intent(s), that triggered the Prehook Request node, appending the data stored in msg.payload.preHookData.

Pre Hook Response node

Based on the msg.payload.handleRequest property, the Pre Hook Response node will either send the payload to the server or trigger the corresponding intent that triggered the Pre Hook Request node.

For example, if the login intent triggers the Pre Hook Request node,

  1. If the msg.payload.handleRequest is set to true, the

Name - Custom name given to the node.

Prehook usage

For example,

  • you can force an anonymous user to login to the chatbot for answering certain sensitive questions or

  • you can count the number of times the fallback intent is triggered or

  • you can redirect a user to use another flow when a specific intent is triggered.

In the below example, using any intent will invoke the login directive if the user is not logged in.

When the chatbot user triggers any intent, the prehook node is invoked and checks if the user is logged in or not. If the user is already logged in, the chatbot replies with the corresponding response for the intent. If the user is not logged in, the login directive will be invoked.

If an anonymous user, any intent he/she tries will invoke the login directive.

For a logged-in user, the chatbot will answer for the triggered intent.

The example flow is attached below.

Related Articles

  • No labels