Fulfillment(mapping=None, *, ignore_unknown_fields=False, **kwargs)
By default, your agent responds to a matched intent with a static response. As an alternative, you can provide a more dynamic response by using fulfillment. When you enable fulfillment for an intent, Dialogflow responds to that intent by calling a service that you define. For example, if an end-user wants to schedule a haircut on Friday, your service can check your database and respond to the end-user with availability information for Friday.
For more information, see the fulfillment
guide <https://cloud.google.com/dialogflow/docs/fulfillment-overview>
__.
Attributes | |
---|---|
Name | Description |
name |
str
Required. The unique identifier of the fulfillment. Supported formats: - projects/
- projects/
This field is not used for Fulfillment in an Environment.
|
display_name |
str
Optional. The human-readable name of the fulfillment, unique within the agent. This field is not used for Fulfillment in an Environment. |
generic_web_service |
google.cloud.dialogflow_v2.types.Fulfillment.GenericWebService
Configuration for a generic web service. |
enabled |
bool
Optional. Whether fulfillment is enabled. |
features |
Sequence[google.cloud.dialogflow_v2.types.Fulfillment.Feature]
Optional. The field defines whether the fulfillment is enabled for certain features. |
Classes
Feature
Feature(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Whether fulfillment is enabled for the specific feature. .. attribute:: type_
The type of the feature that enabled for fulfillment.
:type: google.cloud.dialogflow_v2.types.Fulfillment.Feature.Type
GenericWebService
GenericWebService(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Represents configuration for a generic web service. Dialogflow supports two mechanisms for authentications: - Basic authentication with username and password.
- Authentication with additional authentication headers. More information could be found at: https://cloud.google.com/dialogflow/docs/fulfillment-configure.