ConversationFulfillment
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
The JSON representation defines the implementation of conversation fulfillment.
Key fields include name (unique conversation name), url (HTTPS endpoint), httpHeaders (map of HTTP parameters), and fulfillmentApiVersion (API version).
The url field specifies the HTTPS endpoint for conversation data exchange via POST requests, supporting various endpoint types like API.AI and Google Cloud Functions.
Optional httpHeaders allow including custom HTTP parameters in the POST requests sent to the endpoint.
The HTTPS endpoint for the conversation (HTTP is not supported). This can be an API.AI endpoint, a Google Cloud Function endpoint or a self-hosting HTTPS endpoint. Google sends a POST request to exchange data with 3P.
httpHeaders
map (key: string, value: string)
Map of HTTP parameters to be included in the POST request.
An object containing a list of "key": value pairs. Example: { "name": "wrench", "mass": "1.3kg", "count": "3" }.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[],[]]