Myujth

I am very confused by google documentation on dialogflow and actions for google. It looks like I need to mix and match between the two in order to implement some behaviors, like saving state between turns of a conversation. For example, I have a dialog flow intent handler that looks like this

function showCard(agent) {
 let conv = agent.conv();
 if(!conv) console.log('There is no conv!'); // only assistant will have a conversation
 let n = 0;
 if(conv)

// do some magic to generate a Card and simple response into _speakText

agent.add( _speakText );

if( conv ) 
 if( !conv.user.storage ) conv.user.storage = ;
 conv.data.cardNumber = n;
 conv.user.storage.cardNumber = n;
 console.log(`set cardNumber to $n`);

It looks like neither conversation or user data ever gets persisted. So how do I save state through the dialogflow API? What am I missing?

Is my confusion in that dialogflow examples demonstrate a different handler for requests/responses over actions on google? (Should I yank out everything related to dialogflow agents?)

--- edit ---

 const WebhookClient = require('dialogflow-fulfillment');
 ...
 exports.dialogflowFirebaseFulfillment = functions.https.onRequest((request, response) => {
 const agent = new WebhookClient( request, response );

OR

 const dialogflow = require('actions-on-google');
 ...
 const app = dialogflow();
 exports.dialogflowFirebaseFulfillment = functions.https.onRequest(app);

You can save the data in the session with the conversationToken. You can access to conversationToken through the conversational interface “conv.data” and then type the names of the parameters that you want to store. For example:

Through it you can save the data that you require to be kept in the same session of your Action. This also applies when you send a conversation from one device to another (newSurface). But if you close your action, the session data will be lost.