# Dialogflow Detection Action

This action will parse any user text through Dialogflow engine. This operation is global and can be activated anywhere during the conversation or the current behavior.

![](/files/-LfFpoevOq4fiDg2BsPP)

### Settings

The action uses the following settings:

| Setting                      | Description                                                                                                                        | [Parsed](/actions-and-operations/dynamic-parsing.md) |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| API Version                  | Choose either V1 or V2, depending on the version of your Dialogflow Agent.                                                         | :no\_entry:                                          |
| API Access Token             | The API Token required to integrate your Version 1 Dialogflow Agent or the full Google Auth Json authorization file contents.      | :white\_check\_mark:                                 |
| Project Id                   | The Dialogflow Project Id                                                                                                          | :white\_check\_mark:                                 |
| Language                     | The language of your agent. Make sure to select the same language you've configured on your agent.                                 | :white\_check\_mark:                                 |
| Intent Name                  | The full name of the intent that will trigger this action. Use an asterisk (\*) to trigger on any intent                           | :white\_check\_mark:                                 |
| Detection Confidence         | The minimum confidence required to trigger this action                                                                             | :no\_entry:                                          |
| Display intent reply in chat | If enabled, MyLINK Connect will display a message bubble witht the text you've specified as possible intent reply on Dialogflow.   | :no\_entry:                                          |
| React to Page Comments       | Enable or Disable real-time [Facebook post integration](/basic-concepts/publishing/channels/facebook.md#page-posting-integration). | :no\_entry:                                          |
| Specific Post Id             | Contains the full Facebook post id to be watched. If left empty, the trigger will fire for any post on your page.                  | :white\_check\_mark:                                 |

### Remarks

This action is optimized to use Dialogflow only once per user input. Even using multiple Dialogflow Detection actions will result in a single Dialogflow API Call. Every Dialogflow API call will count as an [additional chatbot message](/basic-concepts/your-account/messages-count.md#integrations).

The Language field is [fully parsed](/actions-and-operations/dynamic-parsing.md) to be dynamic so you can set your Dialogflow language dynamically at runtime. 

Any integration issue that Connect encounters during Dialogflow calls can be found inside each conversation [Execution Diagram](/actions-and-operations/execution/execution-diagram.md) or inside the chatbot preview [Execution Diagram](/actions-and-operations/execution/execution-diagram.md).

### Trigger

On Intent Detected. This action will trigger any child operation as soon as the user input is matching the selected intent with at least the specified confidence.

### Variables

This action produces the following variables after being triggered:

| Variable             | Description                             |
| -------------------- | --------------------------------------- |
| df\_detected\_action | The action detected during last input   |
| df\_detected\_intent | The intent detected during last input   |
| df\_reply            | The intent reply received by Dialogflow |

Every [entity](/artificial-intelligence/nlp/entities.md) specified in the detected [expression ](/artificial-intelligence/nlp/expressions.md)will be translated to a runtime variable named after the entity name.

### Availability

Channel specific availability follows the table below:

| Channel          | Availability                                                           |
| ---------------- | ---------------------------------------------------------------------- |
| Facebook         | Fully Available.                                                       |
| WhatsApp         | Fully Available.                                                       |
| Telegram         | Fully Available.                                                       |
| Web              | Fully Available.                                                       |
| Alexa            | **Not Available. Out of AI Detection is not supported inside skills.** |
| Google Assistant | Fully Available.                                                       |
| Slack            | Fully Available.                                                       |
| API              | Fully Available.                                                       |

This action can be used only at [Bot Global level](/actions-and-operations/execution.md#global-and-local-actions) or [Behavior level.](/actions-and-operations/execution.md#global-and-local-actions) 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mylinkconnect.com/actions-and-operations/input/global-detection/xenioo.bots.actions.dialogflow.operations.dialogflowglobaloperation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.