Google Dialogflow Fulfillment
This page shows how to write Terraform for Dialogflow Fulfillment and write them securely.
The Fulfillment in Dialogflow can be configured in Terraform with the resource name
google_dialogflow_fulfillment. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
display_name- (Required) The human-readable name of the fulfillment, unique within the agent.
enabled- (Optional) Whether fulfillment is enabled.
features- (Optional) The field defines whether the fulfillment is enabled for certain features. Structure is documented below.
generic_web_service- (Optional) Represents configuration for a generic web service. Dialogflow supports two mechanisms for authentications: - Basic authentication with username and password. - Authentication with additional authentication headers. Structure is documented below.
project- (Optional) The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
features block supports:
type- (Required) The type of the feature that enabled for fulfillment.
- SMALLTALK: Fulfillment is enabled for SmallTalk.
Possible values are
- SMALLTALK: Fulfillment is enabled for SmallTalk. Possible values are
generic_web_service block supports:
uri- (Required) The fulfillment URI for receiving POST requests. It must use https protocol.
username- (Optional) The user name for HTTP Basic authentication.
password- (Optional) The password for HTTP Basic authentication.
request_headers- (Optional) The HTTP request headers to send together with fulfillment requests.
In addition to the arguments listed above, the following computed attributes are exported:
id- an identifier for the resource with format
name- The unique identifier of the fulfillment. Format: projects/<Project ID>/agent/fulfillment - projects/<Project ID>/locations/<Location ID>/agent/fulfillment
Explanation in Terraform Registry
By default, your agent responds to a matched intent with a static response. If you're using one of the integration options, 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. To get more information about Fulfillment, see: