Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Questo documento descrive il formato webhook per la comunicazione tra Actions on Google e un servizio di fulfillment che definisce un'interfaccia utente conversazionale personalizzata.
È importante capire in che modo Actions on Google e il tuo fulfillment comunicano
tramite i formati webhook Actions on Google:
Per partecipare alle conversazioni con Actions on Google, il tuo fulfillment implementa un webhook in grado di rispondere alle richieste HTTP da Actions on Google.
Quando gli utenti richiamano l'Azione, il fulfillment riceve un elemento HTTP POST con un payload JSON che descrive la richiesta dell'utente.
A sua volta, il tuo fulfillment è responsabile della lettura dei parametri dal payload della richiesta, della generazione di una risposta in formato JSON appropriata e dell'invio di una risposta all'assistente con questa risposta.
Tipi di richiesta
Questa tabella riassume i tipi di richieste che il webhook potrebbe ricevere
dall'assistente:
Tipo
Descrizione
Esempi JSON
Richieste di chiamata
Espressioni dell'utente che avviano la conversazione con il fulfillment o attivano azioni sul link diretto (ad esempio "Parla con Personal Chef per trovare ricette per la cena").
Se utilizzi Dialogflow, queste richieste corrispondono agli intent definiti nella sezione Discovery delle impostazioni di integrazione dell'Assistente Google.
Se utilizzi l'SDK Actions, queste richieste corrispondono agli intent definiti nel pacchetto Action.
Espressioni degli utenti nella stessa sessione dopo l'inizio della conversazione con il fulfillment. Nel formato webhook di conversazione, queste sono le
risposte di testo non elaborate dell'utente corrispondenti agli intent actions.intent.TEXT
richiesti dal fulfillment nel turno precedente.
Richieste inviate dall'assistente al fulfillment quando il webhook ha richiesto un intent help nel passaggio precedente della conversazione per gestire parti della conversazione (ad esempio, actions.intent.OPTION e actions.intent.PERMISSION).
In uno scenario di interazione tipico di Actions on Google, gli utenti pronunciano una frase per richiamare un'azione. Per fornire una risposta, Actions on Google trova il fulfillment che corrisponde all'azione richiamata dall'utente e invia la richiesta lì.
Dopo che Actions on Google ha stabilito che il tuo fulfillment è una corrispondenza adatta per la chiamata dell'utente, avvia una sessione di conversazione inviando una richiesta HTTP che contiene un payload JSON con le informazioni della richiesta dell'utente all'endpoint di fulfillment. Il fulfillment analizza la richiesta e restituisce una risposta contenente un payload JSON. Actions on Google converte il payload in output vocale
e multimediale sottoposto a rendering per gli utenti.
Figura 1. Actions on Google che richiamano il fulfillment tramite
l'SDK Actions.
Per scoprire di più sul formato del payload JSON quando Actions on Google richiama il tuo fulfillment tramite l'SDK Actions, consulta Formato webhook di conversazione.
Richieste e risposte Dialogflow
Quando crei azioni, puoi facoltativamente utilizzare Dialogflow per semplificare l'attività di creazione delle interfacce di conversazione. In questo scenario, Dialogflow funge da proxy tra Actions on Google e il tuo fulfillment. Anziché inviare la richiesta HTTP/JSON
direttamente al tuo endpoint di fulfillment, Actions on Google la invia
a Dialogflow.
Dialogflow aggrega il payload JSON contenuto nella richiesta originale nel formato webhook di Dialogflow e inoltra la richiesta risultante al fulfillment Dialogflow.
Al contrario, quando il fulfillment invia una risposta a Dialogflow, il payload JSON della risposta deve essere conforme al formato webhook di Dialogflow. Il fulfillment analizza i parametri della richiesta JSON Dialogflow e genera una risposta nel formato webhook Dialogflow. Dialogflow converte quindi la risposta dal fulfillment in un messaggio di risposta comprensibile dall'assistente.
Figura 2. Actions on Google che richiama il fulfillment tramite Dialogflow.
Per scoprire di più sul formato del payload JSON quando Actions on Google richiama il tuo fulfillment tramite Dialogflow, consulta Formato webhook di Dialogflow.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Mancano le informazioni di cui ho bisogno","missingTheInformationINeed","thumb-down"],["Troppo complicato/troppi passaggi","tooComplicatedTooManySteps","thumb-down"],["Obsoleti","outOfDate","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Problema relativo a esempi/codice","samplesCodeIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-07-28 UTC."],[[["\u003cp\u003eActions on Google communicates with your fulfillment service through webhooks, sending JSON payloads that describe user requests.\u003c/p\u003e\n"],["\u003cp\u003eYour fulfillment service needs to process these requests, generate appropriate JSON responses, and send them back to the Assistant.\u003c/p\u003e\n"],["\u003cp\u003eThere are two main webhook formats: Dialogflow webhook format and Conversation webhook format, depending on whether you use Dialogflow or Actions SDK.\u003c/p\u003e\n"],["\u003cp\u003eWebhooks can handle different request types like invocation requests, conversation requests, and helper results, each with specific JSON structures.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow can act as a proxy between Actions on Google and your fulfillment, handling the communication and format conversions.\u003c/p\u003e\n"]]],["Actions on Google uses webhooks to communicate with fulfillment services, sending HTTP POST requests with JSON payloads. Fulfillment services must parse these requests and respond with appropriately formatted JSON. There are two main webhook formats: Dialogflow and Conversation, corresponding to whether Dialogflow acts as a proxy. Webhook requests can be invocations, conversation turns, or helper results. The fulfillment reads parameters from the request payload and sends a reply back to the Assistant.\n"],null,["# Actions on Google webhook formats (Dialogflow)\n\nThis document describes the webhook format for communicating between Actions on Google\nand a fulfillment service that defines a custom [conversational user interface](/assistant/df-asdk/design).\n| **Note:** If you have a Node.js backend server, we strongly encourage you to use the [Actions on Google Node.js client library](/assistant/df-asdk/reference/nodejsv2/overview) to simplify creating your webhook. The client library provides a wrapper for the webhook format. If you prefer to roll your own backend implementation without using the client library, your backend is responsible for consuming and processing the JSON messages sent by Actions on Google via HTTP POST.\n\nIt's important to understand how Actions on Google and your fulfillment communicate\nthrough the Actions on Google webhook formats:\n\n- To participate in conversations with Actions on Google, your fulfillment implements a [webhook](https://en.wikipedia.org/wiki/Webhook) that can respond to HTTP requests from Actions on Google.\n- When users invoke your Action, your fulfillment receives an [`HTTP POST`](https://en.wikipedia.org/wiki/POST_(HTTP)) with a JSON payload that describes the user's request.\n- In turn, your fulfillment is responsible for reading the parameters from the request payload, generating an appropriate JSON formatted response, and sending a reply to the Assistant with this response.\n\n| **Key Terms:**\n|\n| - **Dialogflow webhook format:** JSON payload format when Actions on Google invokes your fulfillment through [Dialogflow](//dialogflow.com/).\n| - **Conversation webhook format:** JSON payload format when Actions on Google invokes your fulfillment through the [Actions SDK](/assistant/df-asdk/actions-sdk).\n\nRequest types\n-------------\n\nThis table summarizes the types of requests that your webhook might receive\nfrom the Assistant:\n\n| Type | Description | JSON Examples |\n|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Invocation requests | User utterances that initiate the conversation with your fulfillment or trigger deep-link Actions (for example, *\"Talk to Personal Chef to find dinner recipes\"* ). - If using Dialogflow, these requests correspond to the intents defined in the **Discovery** section of the **Google Assistant** integration settings. - If using the Actions SDK, these requests correspond to the intents defined in your [Action package](/assistant/df-asdk/reference/action-package/rest/Shared.Types/ActionPackage). | - [Dialogflow webhook](/assistant/df-asdk/reference/dialogflow-webhook-json#simple-invocation-request-example-df) - [Conversation webhook](/assistant/df-asdk/reference/conversation-webhook-json#simple-invocation-request-example-conv) |\n| Conversation requests | Utterances by users in the same session once the conversation with your fulfillment has started. In the conversation webhook format, these are the raw text responses from the user corresponding to `actions.intent.TEXT` intents that your fulfillment requested in the previous turn. | - [Dialogflow webhook](/assistant/df-asdk/reference/dialogflow-webhook-json#simple-conversation-request-example-df) - [Conversation webhook](/assistant/df-asdk/reference/conversation-webhook-json#simple-conversation-request-example-conv) |\n| Helper results | Requests sent by the Assistant to your fulfillment when your webhook has requested a [helper intent](/assistant/df-asdk/helpers) in the previous turn of the conversation to handle parts of the conversation (for example, `actions.intent.OPTION` and `actions.intent.PERMISSION`). | - [Dialogflow webhook](/assistant/df-asdk/reference/dialogflow-webhook-json#helper-result-example-df) - [Conversation webhook](/assistant/df-asdk/reference/conversation-webhook-json#helper-example-conv) |\n\nConversation requests and responses\n-----------------------------------\n\nIn a typical Actions on Google interaction scenario, users utter a phrase to invoke an\nAction. To provide a response, Actions on Google finds the fulfillment that matches the\nAction invoked by the user and sends the request there.\n\nOnce Actions on Google establishes that your fulfillment is a suitable match for the\nuser's invocation, it starts a conversation session by sending an HTTP request\nthat contains a JSON payload with the user's request information to your\nfulfillment endpoint. Your fulfillment parses the request and returns a response\nthat contains a JSON payload. Actions on Google then converts the payload into rendered\nspeech and multimedia output for users.\n**Figure 1.** Actions on Google invoking your fulfillment through the Actions SDK.\n\nTo learn more about the format of the JSON payload when Actions on Google invokes your\nfulfillment through the Actions SDK, see [Conversation webhook format](/assistant/df-asdk/reference/conversation-webhook-json).\n\nDialogflow requests and responses\n---------------------------------\n\nWhen you create Actions, you can optionally use Dialogflow to simplify the\ntask of building conversational interfaces. In this scenario, Dialogflow acts as\na proxy between Actions on Google and your fulfillment. Instead of sending the HTTP/JSON\nrequest directly to your fulfillment endpoint, Actions on Google sends it to\nDialogflow.\n\nDialogflow wraps the JSON payload contained in the original request into the\nDialogflow webhook format, and forwards the resulting request to your Dialogflow\nfulfillment.\n\nConversely, when your fulfillment sends a response to Dialogflow, the JSON\npayload of the response must comply with the Dialogflow webhook format. Your\nfulfillment parses the parameters from the Dialogflow JSON request, and\ngenerates a response in the Dialogflow webhook format. Dialogflow then converts\nthe response from your fulfillment into a response message that the Assistant\nunderstands.\n**Figure 2.** Actions on Google invoking your fulfillment through Dialogflow.\n\nTo learn more about the format of the JSON payload when Actions on Google invokes your\nfulfillment through Dialogflow, see [Dialogflow webhook format](/assistant/df-asdk/reference/dialogflow-webhook-json)."]]
