google_dialogflow_fulfillment

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:

Example Usage - Dialogflow Fulfillment Basic

resource "google_dialogflow_agent" "basic_agent" {
  display_name = "example_agent"
  default_language_code = "en"
  time_zone = "America/New_York"
}

resource "google_dialogflow_fulfillment" "basic_fulfillment" {
  depends_on = [google_dialogflow_agent.basic_agent]
  display_name = "basic-fulfillment"
  enabled    = true
  generic_web_service {
            uri      = "https://google.com"
            username = "admin"
            password = "password"
            request_headers = { 
          name = "wrench"
            }
    }
}

Argument Reference

The following arguments are supported:


The features block supports:

The generic_web_service block supports:

Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

Timeouts

This resource provides the following Timeouts configuration options:

Import

Fulfillment can be imported using any of these accepted formats:

In Terraform v1.5.0 and later, use an import block to import Fulfillment using one of the formats above. For example:

import {
  id = "{{name}}"
  to = google_dialogflow_fulfillment.default
}

When using the terraform import command, Fulfillment can be imported using one of the formats above. For example:

$ terraform import google_dialogflow_fulfillment.default {{name}}

User Project Overrides

This resource supports User Project Overrides.