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
Required. The unique identifier of the fulfillment. Supported formats: - ``projects/
The human-readable name of the fulfillment, unique within the agent. This field is not used for Fulfillment in an Environment.
Configuration for a generic web service. This field is a member of `oneof`_ ``fulfillment``.
Whether fulfillment is enabled.
The field defines whether the fulfillment is enabled for certain features.
Inheritancebuiltins.object > proto.message.Message > Fulfillment
Feature(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Whether fulfillment is enabled for the specific feature.
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.