> For the complete documentation index, see [llms.txt](https://docs.fullwhere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullwhere.com/documentation/documentation-en/automations/workflows.md).

# Workflows

Configure your rules to manage customer interactions according to your business logic

{% hint style="success" icon="list-check" %}
**IN BRIEF**

Workflows are the heart of orchestrating your customer interactions in Fullwhere.

They allow you to define automation logic, such as:

* set up automatic alerts
* automatically assign interactions to users
* generate AI responses
* manage the sending of automatic responses.
  {% endhint %}

{% hint style="info" icon="lightbulb" %}
Fullwhere workflows rely on a visual engine allowing you to freely connect Condition and Action nodes.

This great flexibility allows you to reproduce your internal logic in Fullwhere workflows to best customize the management of your customer interactions.
{% endhint %}

{% hint style="info" icon="shield-check" %}
**ACCESS RIGHTS**

To edit the Workflows in your Fullwhere workspace, you must be a supervising member with Administrator rights.
{% endhint %}

Go to Automations > [Workflows](https://app.fullwhere.com/automation/workflows) from the main navigation bar on the left of your screen.

## Your Workflows <a href="#h_9997e105e2" id="h_9997e105e2"></a>

The Workflows in your Fullwhere workspace are displayed in the Workflows table.\
You can easily find a workflow using the text search bar or the filters *Status* and *Created by*.

The Workflows table displays the following information in columns:

<table><thead><tr><th width="264.765625">Name</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Name assigned to your workflow</td></tr><tr><td>Status</td><td>Active / Inactive</td></tr><tr><td>Created by</td><td>User in your account who created the workflow</td></tr><tr><td>Creation date</td><td>Creation date of your workflow</td></tr><tr><td>Modification date</td><td>Date of the last modification made to your Workflow</td></tr></tbody></table>

To create a Workflow, click the "Create a workflow" button at the top right of your screen.\
To edit an existing Workflow, click the row corresponding to your Workflow in the table.\
To delete a workflow, click the three small dots at the end of the row in the workflows table and click Delete.

## The trigger

When you create a Workflow, the first step is to configure its trigger.\
The trigger lets you set up conditions that define the interactions that will trigger this workflow, and therefore for which the various actions of your workflow can be executed.

To define your trigger, click the blue card "Trigger - Incoming interaction".

In the panel opening on the right, you can add a Note to your trigger; it will be visible on your workflow graph. Adding a Note can be useful to indicate to your teams the conditions defined in your trigger.

Once your trigger is defined, you can configure the next steps of your workflow by adding nodes.\
Click the ⊕ button on the output of the trigger. A drop-down menu opens. You can search or select the type of node to add there.

The menu groups the following nodes:

* **Logical conditions** : *If / Else*, *Filter* and *Switch*
* **AI conditions** : *AI If / Else* and *AI filter*
* **Actions** : select directly the action to execute, such as *Notify users* or *Generate an AI response*.

## The conditions

Condition nodes route your customer interactions according to specific fields and values. For example, you can use the Note, the Text, or the interaction keywords.

[Access the list of available logical conditions.](#liste-des-conditions-logiques)

### The conditions *If / Else*

**The If / Else conditions let you define a condition and determine what happens when it is met or not met.**

After adding the node, click it to configure one or more conditions. You can add a Note, visible on the graph, to easily identify the node.

When an interaction passes through this node, its conditions are evaluated. It takes the output "<mark style="color:$warning;">`True`</mark>" if they are met, or the output "<mark style="color:$warning;">`False`</mark>" otherwise.

Click "**⊕ True**" or "**⊕ False**" to open the add menu. Search for or select the node to add. Each output can lead to a different step in the workflow.

### The *Filters*

**Filters allow only interactions that meet your conditions to pass through.**

After adding a filter, click it to configure one or more conditions. You can add a Note, visible on the graph, to easily identify the node.

A filter has a single output. Interactions that meet the conditions continue to the next nodes. Other interactions do not continue execution of this workflow path.

Click ⊕ to open the add menu. Search for or select the node to add after the filter.

### Switch conditions

**Switch conditions let you handle multiple cases in a defined order. Use them when a If / Else condition is not enough to distribute your interactions across several branches.**

Add a case, give it a name, then configure its conditions. Each case has its own output. Click ⊕ to open the add menu and select the next node.

The cases are evaluated in the order shown. By default, as soon as a case is met, the conditions or actions that follow it are executed and the other cases are not taken into account. Enable the option **Continue to the next case if the conditions are met** : in this case, several paths can be used during the same execution.

The output **Default**, optional, is used when no case matches. You can also connect one or more next steps to it.

## AI conditions

AI conditions let you route or filter your customer interactions based on scenarios expressed in natural language.

### The conditions *AI If / Else*

**AI If / Else conditions let you define a scenario and determine what happens when it matches or does not match an interaction.**

After adding the node, click it to configure it.

In the panel opening on the right, you can add a Note to your AI condition node; it will be visible on your workflow graph, allowing you to easily recognize your condition node.

In the "Prompt" section, define in natural language the scenario that the AI must check.

When a customer interaction passes through an AI If / Else Node, it is compared to your prompt using an LLM. If the LLM considers that the interaction matches the prompt, it takes the output "<mark style="color:$warning;">`True`</mark>". Otherwise, it takes the output "<mark style="color:$warning;">`False`</mark>".

{% hint style="info" %}
In the case of conversation-type interactions (WhatsApp, Email, etc.), the last received message as well as the conversation history will be sent to the LLM.
{% endhint %}

Click the "**⊕ True**" or "**⊕ False**". The drop-down menu allows you to search for or select the node to add for each branch.

### The *AI filters*

**AI filters allow only interactions that match a scenario described in natural language to pass through.**

After adding an AI filter, click it to configure it. In the "Prompt" section, define in natural language the scenario that the AI must check.

The AI filter has a single output. Interactions that match the prompt continue to the next nodes. Other interactions do not continue execution of this workflow path.

Click ⊕ to open the add menu. Search for or select the node to add after the AI filter.

## The actions

Following your trigger, a logical conditions node or an AI conditions node, you can add one or more action nodes.

Click the ⊕ button corresponding to the desired output. In the section **Actions** of the drop-down menu, search for or directly select the action to add.

These nodes define actions that will be automatically applied to the customer interactions for which they are executed.\
Actions can be of different types and can each be configured according to your needs.

Once you have added an action node to your Workflow, click it to configure it.

In the panel opening on the right, you can add a Note to your AI condition node; it will be visible on your workflow graph, allowing you to easily recognize your action node.

Then select the type of action you want to configure:

### Notify users

The "Notify users" action lets you send a notification by email or in the [notification center](https://docs.fullwhere.com/documentation/documentation-en/notifications/the-notification-center.md) Fullwhere to users of your choice.

{% stepper %}
{% step %}

#### Recipients panel

The recipients panel lets you configure the users to be notified by your action node.

Click "Add recipients", then search for and select the users to add.

You can also notify users based on the Zone (Brand, Location, Location Group) concerned by the customer interaction.

To define specific users for your brands, click "**Brands +**".

You can "**Choose brands**" to add brands to your action node and define the recipients to notify for this brand.\
You can also use the option "**Pre-fill from settings**". In that case, we will create the notification logic for you based on your brands and the users who have rights on your brands.

You can perform this operation for the **Locations** and **Location Groups.**
{% endstep %}

{% step %}

#### Notifications panel

In the Notifications panel, you can select the channels to use for sending notifications: Email, Fullwhere App, and WhatsApp.

**Email**

* the email subject
* a potential custom message (optional) for the recipients, which will be displayed in the header of the received email.

**Fullwhere App**\
Notifications sent on the Fullwhere App channel will be sent to users directly on the platform, in the [notification center](https://docs.fullwhere.com/documentation/documentation-en/notifications/the-notification-center.md).

**WhatsApp**\
WhatsApp notifications can be sent to selected users who have WhatsApp and who have saved their phone number on their [Fullwhere account](https://docs.fullwhere.com/documentation/documentation-en/get-started/set-up-your-account.md#h_383effe7cc).

{% hint style="info" %}
WhatsApp sending is subject to additional billing. Contact your account manager for more information.
{% endhint %}
{% endstep %}
{% endstepper %}

### Assign users

The "Assign users" action lets you assign a customer interaction to users of your choice.

{% hint style="info" %}
The assignment determines the users for whom a customer interaction will appear in the main view "[My Inbox](https://docs.fullwhere.com/documentation/documentation-en/inbox/navigate-in-the-inbox.md#mon-inbox)".
{% endhint %}

Click "Add users", then search for and select the users to add.

You can also assign users based on the Zone (Brand, Location, Location Group) concerned by the customer interaction.

To define specific users for your brands, click "**Brands +**".

You can "**Choose brands**" to add brands to your action node and define the users to assign for this brand.\
You can also use the option "**Pre-fill from settings**". In that case, we will create the assignment logic for you based on your brands and the users who have rights on your brands.

You can perform this operation for the **Locations** and **Location Groups.**

### Generate an AI response

This action lets you generate a response using a [AI agent](https://docs.fullwhere.com/documentation/documentation-en/automations/ai-agents.md) previously configured on your account.

#### General settings

{% stepper %}
{% step %}

#### Associate an AI agent

Select the '[AI agent](https://docs.fullwhere.com/documentation/documentation-en/automations/ai-agents.md) that your action will use to generate a response. Your agent must have been previously configured.
{% endstep %}

{% step %}

### Associate knowledge bases (optional)

Select the [knowledge bases](https://docs.fullwhere.com/documentation/documentation-en/automations/knowledge-bases.md) to use for response generation. You can add up to 5 knowledge bases to a response generation action.
{% endstep %}

{% step %}

#### Response channel

This setting lets you select the [channel](https://docs.fullwhere.com/documentation/documentation-en/inbox/handle-a-customer-interaction.md#h_817c292fa7) on which you want to reply to your customer.

* **Customer channel:** the response channel will match the [default response channel](https://docs.fullwhere.com/documentation/documentation-en/inbox/handle-a-customer-interaction.md#le-canal-de-reponse) of the interaction
* **Email:** your response draft will be generated to be sent by email. You can then specify advanced settings specific to the Email channel.
* **SMS:** your response draft will be generated to be sent by SMS. You can then specify advanced settings specific to the SMS channel.
  {% endstep %}

{% step %}

#### Automatic sending of the response

**Yes** : your response draft will be sent automatically.\
You can then define sending settings:\
\- the sending delay\
\- the days of the week on which responses should be sent\
\- the time window during which responses can be sent.

**No** : your response draft will simply be generated but will not be sent automatically.
{% endstep %}

{% step %}

#### Advanced settings

**Additional instructions for your AI agent**\
This field lets you specify additional instructions for your AI agent, which will only be taken into account by this response generation action. This setting can allow you to specialize your AI agent according to your different scenarios. You can use [variables](https://docs.fullwhere.com/documentation/documentation-en/automations/ai-agents.md#h_3198d4840a) to dynamically specify context to your AI agent.

**Provide your AI agent with the interaction history**\
By enabling this setting, your AI agent will be able to use the entire conversation to generate the response, not just the last received message. This setting is enabled by default.\
It is recommended to enable this setting for conversation-type interactions (email, direct messages...).

**Provide your AI agent with the conversation attachments**\
By enabling this setting, your AI agent will be able to analyze attachments provided by your customers.

**If you have set the response channel to Email, you can configure specific advanced settings:**

* Sending email address: lets you define the email address of your account that will be used to send the response
* Email sender: lets you configure the sender name of your email, which will appear in the recipient's inbox. You can use variables to use a dynamic sender based on your brands or locations.
* Additional recipients: you can specify recipients (To or CC) who will be added to the email loop

**If you have set the response channel to SMS, you can configure specific advanced settings:**

* SMS sender: the name displayed when the SMS is received by the recipient
* Additional recipients: you can specify recipients who will also receive the SMS.
  {% endstep %}
  {% endstepper %}

#### Language settings

The tab **Language** of the Generate AI response action lets you control the language in which the response will be generated. You can define a priority order among several language sources so that Fullwhere automatically determines the most appropriate language.

Four sources can be used:

* **Customer language** : the language associated with the customer profile.
* **Interaction language** : the language detected in the received message.
* **Location language** : the default language of the location linked to the interaction
* **Brand language** : the default language of the brand linked to the interaction

These options can be prioritized. For example, you can choose to first respond in the language of the received message, and if it is not detected, use the customer's language.

You can also define a default language. This language will serve as a fallback if none of the configured languages (customer language, interaction language, location language or brand language) is available or detected.

If only a default language is defined in the action, then all generated responses will automatically be produced in this language.

### Create a manual response

The response creation action lets you create a response draft using a fixed response template.

This action can be used if you always want to reply with the same response for a specific scenario.

{% stepper %}
{% step %}

#### Text of your response

Enter the text that will be used to create your response draft.\
You can use **variables** to make your response template dynamic.
{% endstep %}

{% step %}

### Response language

Indicate the language in which your response is written.
{% endstep %}

{% step %}

#### Response channel

This setting lets you select the channel on which you want to reply to your customer.

**Customer channel:** the response channel will match the [default response channel](https://docs.fullwhere.com/documentation/documentation-en/inbox/handle-a-customer-interaction.md#le-canal-de-reponse) of the interaction\
**Email:** your response draft will be generated to be sent by email. You can then specify advanced settings specific to the Email channel.\
**SMS:** your response draft will be generated to be sent by SMS. You can then specify advanced settings specific to the SMS channel.
{% endstep %}

{% step %}

#### Automatic sending of the response

**Yes** : your response draft will be sent automatically.\
You can then define sending settings:\
\- the sending delay\
\- the days of the week on which responses should be sent\
\- the time window during which responses can be sent.

**No** : your response draft will simply be generated but will not be sent automatically.
{% endstep %}
{% endstepper %}

### Switch to manual mode

This action lets you switch the mode of an interaction to *<mark style="color:orange;">`Human`</mark>*, which means automatic response sending will not be allowed for this customer interaction.

From the moment this action is executed for a customer interaction, no further responses can be sent automatically for this customer interaction.

To reactivate automatic response sending for a customer interaction, see Inbox.

Setting up this action can be useful to delegate the handling of certain customer interactions to your teams.

For more information on how Interaction Mode works, see this [dedicated section](https://docs.fullwhere.com/documentation/documentation-en/inbox/handle-a-customer-interaction.md#modifier-le-mode-dune-interaction).

### Define attributes

The [attributes](https://docs.fullwhere.com/documentation/documentation-en/automations/attributes.md) are custom fields that you can add to your Fullwhere workspace.

The Define attributes action lets you automatically set the value of some of your attributes directly from a workflow.

{% hint style="warning" %}
If you configure the value of an attribute through a workflow for which AI detection is enabled, the values assigned by your workflow will overwrite any values found by AI
{% endhint %}

{% stepper %}
{% step %}

#### Select the attributes

In the Attributes to define drop-down menu, select the attributes for which your action must assign values.
{% endstep %}

{% step %}

#### Configure values

For each selected attribute, you must select or specify the value or values to assign to your interaction.

For Multiple Select type attributes, indicate whether or not you want to Overwrite the values already present.\
If, at the time of analysis, a customer interaction already has values for a given attribute, two behaviors are possible:

* Overwrite the values already present: the values already assigned by a workflow or a user will be replaced by those defined in your action
* Do not Overwrite the values already present: the values defined in your action will be added to those already assigned by a workflow or a user.
  {% endstep %}
  {% endstepper %}

### Archive the interaction

This action lets you automatically archive a customer interaction.\
Once archived, a customer interaction will no longer be visible in your Fullwhere Inbox.\
Archived interactions can be viewed in the "Archived" view.

### Set interaction status

This action lets you set the status of your interaction once it has been processed by your workflow.

The status of your interaction can be set to <mark style="color:orange;">Pending</mark>, <mark style="color:$success;">Processed</mark>, or <mark style="color:$info;">Ignored</mark>.

**Use cases:**

* <mark style="color:$success;">Processed</mark> : for example, this can be useful when, despite a customer reply, you consider the interaction to be finished
* <mark style="color:orange;">Pending</mark> : can help you keep your customer interaction in Pending status even if a response is sent automatically.
* <mark style="color:$info;">Ignored</mark> : allows you not to reply to a customer interaction. Unlike the Processed status, this status does not affect your handling statistics.

{% hint style="info" %}
If your workflow includes a response generation or creation action with automatic sending, the interaction status automatically changes to Processed when the response is sent. For it to remain Pending, you must add an action explicitly setting this status.
{% endhint %}

### Send a webhook

The **Webhooks** are automated messages sent by Fullwhere when the "Send a webhook" action is triggered in one of your workflows. They contain a payload with the information of the interaction that triggered the action and are sent to a unique URL that you define. You can add custom Headers and Metadatas as needed.

Webhooks are an excellent way to integrate your ecosystem with Fullwhere, as they allow you to set up more advanced integrations based on your needs, without requiring much development work from you.

If needed, for security reasons, webhooks received in your system can be identified and verified using a unique signature.

Once your webhook sending action has been added to your Workflow, you can configure the following fields:

* **Destination URL** : this is the URL to which Fullwhere will send the event
* **Custom Headers** : you can add custom headers as needed that will be sent to the destination URL.\
  Headers must be added as a list of key-value pairs.
* **Custom Metadatas** : you can add custom metadatas as needed that will be sent to the destination URL.\
  Metadatas must be added as a list of key-value pairs.

To learn more about webhook signing or the received payload, refer to our [dedicated documentation](https://docs.fullwhere.com/developer/webhooks/utiliser-les-webhooks.md).

### Add a delay to an action

Adding a delay to your action lets you postpone its execution into the future.

To configure a delay, click the action to modify, then at the top right click the 3 small dots and in the drop-down menu click on **Add a delay**.

* **Action delay:** determines the delay after which an action must be executed
* **Days:** the action will only execute on the selected days. If the workflow is triggered on an unselected day, execution of the action will be postponed until the next valid day.
* **Trigger time window:** the action will only execute within the defined time window. If the workflow is triggered outside this time, execution of the action will be postponed until the next valid time window.

When an action has a delay, it carries the indicator <i class="fa-bolt-lightning" style="color:$info;">:bolt-lightning:</i>.

To modify an action's delay, click the indicator <i class="fa-bolt-lightning" style="color:$info;">:bolt-lightning:</i> at the top right of the action configuration panel.

To remove a delay, click Remove delay in the delay configuration panel.

{% hint style="info" icon="lightbulb" %}
Use case

An action delay may be necessary, for example, if you want to keep your customer interaction in Pending status after sending an automatic response.

To do this, add a response generation and status-setting action to your Workflow.

Then set a delay of a few minutes on your status-setting action.
{% endhint %}

## List of logical conditions

### Conditions related to the interaction

<table><thead><tr><th width="232.09375">Name</th><th>Description</th></tr></thead><tbody><tr><td><code>Source</code></td><td>Initial source of the customer interaction</td></tr><tr><td><code>Message channel</code></td><td>Source of the new incoming message within a conversation</td></tr><tr><td><code>Rating</code></td><td>Rating out of 5 (for reviews and satisfaction surveys)</td></tr><tr><td><code>Text content</code></td><td>Text content</td></tr><tr><td><code>Sentiment</code></td><td>Sentiment detected in the text</td></tr><tr><td><code>Topics</code></td><td>Themes detected in the text</td></tr><tr><td><code>Emotions</code></td><td>Emotions detected in the text</td></tr><tr><td><code>Text size</code></td><td>Length of the text in number of characters</td></tr><tr><td><code>Categories</code></td><td>Categories detected according to your <a href="https://docs.fullwhere.com/documentation/documentation-en/automations/keywords.md">keywords</a></td></tr><tr><td><code>Brand</code></td><td>Brand of the customer interaction or the interaction location</td></tr><tr><td><code>Location</code></td><td>Location of the customer interaction (if any)</td></tr><tr><td><code>Location group</code></td><td>Location groups of the interaction location (if any)</td></tr><tr><td><code>Contact address</code></td><td>Email address that received the incoming email</td></tr><tr><td><code>Language</code></td><td>Language detected in the text. The language of the text can be compared to a fixed value (for example English) or to the language of the brand or location.</td></tr><tr><td>Status</td><td>The interaction status (To process, Processed, Ignored)</td></tr><tr><td><code>Form</code></td><td><a href="#formulaire-de-contact-conditions-avancees">Advanced conditions</a> on contact forms.</td></tr><tr><td><code>Survey</code></td><td><a href="#enquete-conditions-avancees">Advanced conditions</a> on satisfaction surveys</td></tr><tr><td><code>SevenRooms</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Zenchef</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Sunday</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Booking</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Message attributes</code></td><td>Allows conditions to be triggered on <a href="https://docs.fullwhere.com/documentation/documentation-en/automations/attributes.md">custom attributes</a>.</td></tr></tbody></table>

#### Contact form - Advanced conditions

<table><thead><tr><th width="228.8671875">Name</th><th>Description</th></tr></thead><tbody><tr><td><code>Form name</code></td><td><a href="https://docs.fullwhere.com/documentation/documentation-en/capture/contact-forms.md">Form</a> of the contact form that received the interaction</td></tr><tr><td><code>Reply</code></td><td>Allows filtering on the answers given to the different form questions*.</td></tr><tr><td><code>Enabled</code></td><td>Online / Offline status of the form</td></tr></tbody></table>

{% hint style="info" icon="circle-info" %}
\*When you use the advanced "Answer" condition of Contact forms, you are asked to select the form field and the possible values for which you want your condition to be evaluated.

If within your Fullwhere workspace you have several forms with fields that have the same name, your condition can be validated regardless of the form submitted by the customer, as long as it contains a field with that name. If you want to target a specific form, add a "Form name" condition.

Also, the values proposed for the condition are taken from all fields with the same name across all your Fullwhere forms. Thus, for example, if several forms contain a "Order type" field, the list displays the possible values coming from all forms combined.
{% endhint %}

#### Survey - Advanced conditions

<table><thead><tr><th width="228.8671875">Name</th><th>Description</th></tr></thead><tbody><tr><td><code>Survey name</code></td><td><a href="https://docs.fullwhere.com/documentation/documentation-en/capture/satisfaction-surveys.md">Survey</a> of the contact form that received the interaction</td></tr><tr><td><code>Reply</code></td><td>Allows filtering on the answers given to the different survey questions*.</td></tr><tr><td><code>Enabled</code></td><td>Online / Offline status of the survey</td></tr><tr><td><code>Public access</code></td><td>Public or private survey</td></tr><tr><td><code>Solicitation channel</code></td><td>Survey collected by Email, SMS or WhatsApp</td></tr></tbody></table>

{% hint style="info" %}
\*When you use the advanced "Answer" condition of Surveys, you are asked to select the survey field and the possible values for which you want your condition to be evaluated.

If within your Fullwhere workspace you have several surveys with fields that have the same name, your condition can be validated regardless of the survey completed by the customer, as long as it contains a field with that name. If you want to target a specific survey, add a "Survey name" condition.

Also, the values proposed for the condition are taken from all fields with the same name across all your Fullwhere surveys. Thus, for example, if several surveys contain an "Order type" field, the list displays the possible values coming from all surveys combined.
{% endhint %}

### Conditions related to the customer attached to the interaction

<table><thead><tr><th width="232.09375">Name</th><th>Description</th></tr></thead><tbody><tr><td><code>Phone</code></td><td>Customer phone number</td></tr><tr><td><code>Email</code></td><td>Customer email</td></tr><tr><td><code>Customer tag</code></td><td>Tags assigned to the customer</td></tr><tr><td><code>Description</code></td><td>Customer description</td></tr><tr><td><code>Zenchef</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Zelty</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Customer attributes</code></td><td>Allows conditions to be triggered on <a href="https://docs.fullwhere.com/documentation/documentation-en/automations/attributes.md">custom attributes</a>.</td></tr></tbody></table>

### Conditions relating to the transaction attached to the interaction

<table><thead><tr><th width="266.0703125">Name</th><th>Description</th></tr></thead><tbody><tr><td><code>Origin</code></td><td>Transaction source</td></tr><tr><td><code>Amount</code></td><td>Transaction amount</td></tr><tr><td><code>Sevenrooms - Order</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Zenchef - Order</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Zelty - Order</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Juxta - Order</code></td><td>Allows use of specific sub-fields of this provider</td></tr><tr><td><code>Transaction attributes</code></td><td>Allows conditions to be triggered on <a href="https://docs.fullwhere.com/documentation/documentation-en/automations/attributes.md">custom attributes</a>.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fullwhere.com/documentation/documentation-en/automations/workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
