# Examples snippets Unpublished/missing examples for the reference pages. ## Examples - Triggers You can learn more about using Triggers from the following examples.
How to create a Process Integration flows in Frends are referred to as Processes. Processes consist of elements such as Triggers, Tasks, Subprocesses, decisions and loops. Processes are created by connecting elements together and configuring their parameters. ## Step by Step Tutorial Available If you prefer more visual or interactive guidance on how to create Processes with Frends, you can find a step-by-step walkthrough from your own environment's home page, under Onboarding by selecting "Tutorial 1, Step 3: Creating my first Process" tutorial. ## Creating New Process The Process list displays the already created Processes in the Environment.
The view shows a list of Processes within Frends.

Example view of Process list.

In order to create a new Process, click on **Create New** button while in Process list view and having the Development Environment selected. All new Processes have to be created and edited in the Development Environment, from where they are then deployed to other Environments and Agent Groups for execution.
Showing where and how to create a new Process.

Integrations can be created from Process list view while having Development Environment selected.

Default view in Process Editor, when starting to create a new Process.

Process Editor for a new Process.

When creating a new Process, you can start by providing the Process a name and optionally a description. To use the latest versions in Frends, targeting .NET 8 is recommended, while .NET Framework 4.7.1 or .NET Standard 2.0 are only used to support legacy environments. As an example, let's create a Process which is started manually without parameters, calls an API endpoint and then returns a result. Because the start element, called **Trigger**, is already provided, we can continue forward by adding a **Task** to the process. You can drag or click and place the Task shape from the leftside toolbar to right of the Trigger shape.
Image shows where to select a Task shape and insert it to the canvas.

Adding a Task shape to the Process.

To make the Task perform an API call, click on the **Select a Task** field and search and select **HTTP Request** Task. When the Task type is selected, the right sidebar contents change to show the Task parameters. In here, enter the url as **** and make sure Method is GET. Rest of the options can be left as-is for this example.
This image shows the parameters for the chosen Task, to perform an API call.

Parameters for the Task can be set after selecting its type.

Once the Task is configured for our use, we need to connect it to the earlier shape. To do this, click on the **Connect tool** from the left toolbar or from the quick toolbar next to the Trigger shape, and draw an arrow from the Trigger to the Task shape.
Here we show how to find and use Connect tool to connect shapes together.

Draw a connection from the Trigger to Task using the Connect tool.

Finally, we need to end the Process and save it. All Processes start with a Trigger, and end to a **Return shape**, or optionally to a **Throw** shape. Let's drag a Return shape to the right side of the Task, and connect it to the Task shape to create a complete Process flow.
Image showing a completed Process flow, with Return shape parameters.

Complete integration flow with return value.

For the example, we want to return the API response's body. We can do this by selecting the Return shape, and writing **#result\[HTTP Request].Body** to the Expression field. Make sure the field's type is set to **Expression,** and not **Text**, in order to Frends consider the content as C# code and not text.
Utilizing the Auto-complete feature makes Process development faster.

Utilize the provided Auto-complete feature to fill in variable names and result objects' names quicker.

{% hint style="info" %} We will cover the C# expressions and other programming features of Frends later on in the guides, but you can also [check out our guide about Expressions in Frends](/guides/development/using-expressions-in-frends-processes.md) already to learn more right from the start. {% endhint %} Once ready, we can **validate** and **save** the process. You can optionally provide a **Description** or a comment to version history, what was changed in this version. It's recommended to always include a short comment on what was done.
Saving and validating the Process is done at the bottom of the editor.

Saving and validating the Process is done at the bottom of the editor.

Validation at this point means that the Process is taken through C# compiler and checked for errors, but it does not save the Process in any way. To save the Process for testing and deployment, select **Create new Process**. Saving the Process also validates it for errors, but save is not done if any errors persist. When editing a Process, the save button changes to **Save changes**. If you want to save your Process but not create a new version for use yet, you can instead select **Create new draft** from the small arrow menu. This way you can save your work even if the Process is not yet valid. Once the saving and validation succeeds, you are taken back to Process list view with your new Process highlighted at the top of the list. From there, you can run it, deploy it or continue editing, among other options.
New Process hightlighted at the top of the Process list, with options for the Process shown.

New Process hightlighted at the top of the Process list, with options for the Process shown.

How to enable manual execution for an API Process Adding manual trigger to API process, checking for trigger type, configuring parameters.
How to create and use conditional trigger Creating subprocess for conditional trigger, configuring parameters for the trigger, how to use the result value from trigger.
How to create a Subprocess Manual trigger parameters, trigger reference value usage.
How to run Process every 5 minutes Schedule trigger configuration options, trigger ref value usage.
## Examples - Return You can learn more about using Return shape from the following examples.
How to create a Process Integration flows in Frends are referred to as Processes. Processes consist of elements such as Triggers, Tasks, Subprocesses, decisions and loops. Processes are created by connecting elements together and configuring their parameters. ## Step by Step Tutorial Available If you prefer more visual or interactive guidance on how to create Processes with Frends, you can find a step-by-step walkthrough from your own environment's home page, under Onboarding by selecting "Tutorial 1, Step 3: Creating my first Process" tutorial. ## Creating New Process The Process list displays the already created Processes in the Environment.
The view shows a list of Processes within Frends.

Example view of Process list.

In order to create a new Process, click on **Create New** button while in Process list view and having the Development Environment selected. All new Processes have to be created and edited in the Development Environment, from where they are then deployed to other Environments and Agent Groups for execution.
Showing where and how to create a new Process.

Integrations can be created from Process list view while having Development Environment selected.

Default view in Process Editor, when starting to create a new Process.

Process Editor for a new Process.

When creating a new Process, you can start by providing the Process a name and optionally a description. To use the latest versions in Frends, targeting .NET 8 is recommended, while .NET Framework 4.7.1 or .NET Standard 2.0 are only used to support legacy environments. As an example, let's create a Process which is started manually without parameters, calls an API endpoint and then returns a result. Because the start element, called **Trigger**, is already provided, we can continue forward by adding a **Task** to the process. You can drag or click and place the Task shape from the leftside toolbar to right of the Trigger shape.
Image shows where to select a Task shape and insert it to the canvas.

Adding a Task shape to the Process.

To make the Task perform an API call, click on the **Select a Task** field and search and select **HTTP Request** Task. When the Task type is selected, the right sidebar contents change to show the Task parameters. In here, enter the url as **** and make sure Method is GET. Rest of the options can be left as-is for this example.
This image shows the parameters for the chosen Task, to perform an API call.

Parameters for the Task can be set after selecting its type.

Once the Task is configured for our use, we need to connect it to the earlier shape. To do this, click on the **Connect tool** from the left toolbar or from the quick toolbar next to the Trigger shape, and draw an arrow from the Trigger to the Task shape.
Here we show how to find and use Connect tool to connect shapes together.

Draw a connection from the Trigger to Task using the Connect tool.

Finally, we need to end the Process and save it. All Processes start with a Trigger, and end to a **Return shape**, or optionally to a **Throw** shape. Let's drag a Return shape to the right side of the Task, and connect it to the Task shape to create a complete Process flow.
Image showing a completed Process flow, with Return shape parameters.

Complete integration flow with return value.

For the example, we want to return the API response's body. We can do this by selecting the Return shape, and writing **#result\[HTTP Request].Body** to the Expression field. Make sure the field's type is set to **Expression,** and not **Text**, in order to Frends consider the content as C# code and not text.
Utilizing the Auto-complete feature makes Process development faster.

Utilize the provided Auto-complete feature to fill in variable names and result objects' names quicker.

{% hint style="info" %} We will cover the C# expressions and other programming features of Frends later on in the guides, but you can also [check out our guide about Expressions in Frends](/guides/development/using-expressions-in-frends-processes.md) already to learn more right from the start. {% endhint %} Once ready, we can **validate** and **save** the process. You can optionally provide a **Description** or a comment to version history, what was changed in this version. It's recommended to always include a short comment on what was done.
Saving and validating the Process is done at the bottom of the editor.

Saving and validating the Process is done at the bottom of the editor.

Validation at this point means that the Process is taken through C# compiler and checked for errors, but it does not save the Process in any way. To save the Process for testing and deployment, select **Create new Process**. Saving the Process also validates it for errors, but save is not done if any errors persist. When editing a Process, the save button changes to **Save changes**. If you want to save your Process but not create a new version for use yet, you can instead select **Create new draft** from the small arrow menu. This way you can save your work even if the Process is not yet valid. Once the saving and validation succeeds, you are taken back to Process list view with your new Process highlighted at the top of the list. From there, you can run it, deploy it or continue editing, among other options.
New Process hightlighted at the top of the Process list, with options for the Process shown.

New Process hightlighted at the top of the Process list, with options for the Process shown.

How to create an API Process HTTP response creation.
How to use Scope shape Returning a value from a scope.
How to create a Subprocess Returning a value from a subprocess
How to create and use Conditional Trigger Returning a value from the conditional trigger subprocess.
## Examples - Intermediate Return Here are some examples to learn more about using Intermediate Return shape.
How to use Intermediate Return shape Basics of intermediate return usage and configuration
How to create asynchronous API Process API process creation, intermediate return shape usage, sending a response as new http request.
## Examples - Throw Here are some examples to learn more about using Throw shape.
How to interrupt iteration Using throw
How to log error to Frends Process Instances Throwing error from process
How to use Subprocess for catching unhandled errors If error is raised or thrown, how to handle it.
How to handle errors effectively within Processes
## Examples - Catch Here are some examples to learn more about using Catch shape.
How to handle errors within iteration Scope and catch within iteration
How to handle errors effectively within Processes Default error handling scheme
How to handle errors for single Tasks Minimized version of error handling.
## Examples - Exclusive Decision You can learn more about using Exclusive Decision shape from the following examples.
How to use conditions within Processes
## Examples - Inclusive Decision You can learn more about using Inclusive Decision shape from the following examples.
How to use conditions within Processes
## Examples - Task You can learn more about Task shapes from the following guides and examples.
How to create a Process with Frends Integration flows in Frends are referred to as Processes. Processes consist of elements such as Triggers, Tasks, Subprocesses, decisions and loops. Processes are created by connecting elements together and configuring their parameters. ## Step by Step Tutorial Available If you prefer more visual or interactive guidance on how to create Processes with Frends, you can find a step-by-step walkthrough from your own environment's home page, under Onboarding by selecting "Tutorial 1, Step 3: Creating my first Process" tutorial. ## Creating New Process The Process list displays the already created Processes in the Environment.
The view shows a list of Processes within Frends.

Example view of Process list.

In order to create a new Process, click on **Create New** button while in Process list view and having the Development Environment selected. All new Processes have to be created and edited in the Development Environment, from where they are then deployed to other Environments and Agent Groups for execution.
Showing where and how to create a new Process.

Integrations can be created from Process list view while having Development Environment selected.

Default view in Process Editor, when starting to create a new Process.

Process Editor for a new Process.

When creating a new Process, you can start by providing the Process a name and optionally a description. To use the latest versions in Frends, targeting .NET 8 is recommended, while .NET Framework 4.7.1 or .NET Standard 2.0 are only used to support legacy environments. As an example, let's create a Process which is started manually without parameters, calls an API endpoint and then returns a result. Because the start element, called **Trigger**, is already provided, we can continue forward by adding a **Task** to the process. You can drag or click and place the Task shape from the leftside toolbar to right of the Trigger shape.
Image shows where to select a Task shape and insert it to the canvas.

Adding a Task shape to the Process.

To make the Task perform an API call, click on the **Select a Task** field and search and select **HTTP Request** Task. When the Task type is selected, the right sidebar contents change to show the Task parameters. In here, enter the url as **** and make sure Method is GET. Rest of the options can be left as-is for this example.
This image shows the parameters for the chosen Task, to perform an API call.

Parameters for the Task can be set after selecting its type.

Once the Task is configured for our use, we need to connect it to the earlier shape. To do this, click on the **Connect tool** from the left toolbar or from the quick toolbar next to the Trigger shape, and draw an arrow from the Trigger to the Task shape.
Here we show how to find and use Connect tool to connect shapes together.

Draw a connection from the Trigger to Task using the Connect tool.

Finally, we need to end the Process and save it. All Processes start with a Trigger, and end to a **Return shape**, or optionally to a **Throw** shape. Let's drag a Return shape to the right side of the Task, and connect it to the Task shape to create a complete Process flow.
Image showing a completed Process flow, with Return shape parameters.

Complete integration flow with return value.

For the example, we want to return the API response's body. We can do this by selecting the Return shape, and writing **#result\[HTTP Request].Body** to the Expression field. Make sure the field's type is set to **Expression,** and not **Text**, in order to Frends consider the content as C# code and not text.
Utilizing the Auto-complete feature makes Process development faster.

Utilize the provided Auto-complete feature to fill in variable names and result objects' names quicker.

{% hint style="info" %} We will cover the C# expressions and other programming features of Frends later on in the guides, but you can also [check out our guide about Expressions in Frends](/guides/development/using-expressions-in-frends-processes.md) already to learn more right from the start. {% endhint %} Once ready, we can **validate** and **save** the process. You can optionally provide a **Description** or a comment to version history, what was changed in this version. It's recommended to always include a short comment on what was done.
Saving and validating the Process is done at the bottom of the editor.

Saving and validating the Process is done at the bottom of the editor.

Validation at this point means that the Process is taken through C# compiler and checked for errors, but it does not save the Process in any way. To save the Process for testing and deployment, select **Create new Process**. Saving the Process also validates it for errors, but save is not done if any errors persist. When editing a Process, the save button changes to **Save changes**. If you want to save your Process but not create a new version for use yet, you can instead select **Create new draft** from the small arrow menu. This way you can save your work even if the Process is not yet valid. Once the saving and validation succeeds, you are taken back to Process list view with your new Process highlighted at the top of the list. From there, you can run it, deploy it or continue editing, among other options.
New Process hightlighted at the top of the Process list, with options for the Process shown.

New Process hightlighted at the top of the Process list, with options for the Process shown.

How to create a Subprocess
Using a database in Processes
How to create your own Task
## Examples - Call Subprocess You can learn more about Call Subprocess shape from the following guides and examples.
How to create a Subprocess
How to use a Subprocess in Processes
How to access internal resources from public API
## Examples - Assign Variable You can learn more about Assign Variable shape from the following guides and examples.
How to create and use variables in Processes
Data types in Frends Processes
## Examples - Code Task You can learn more about Code Task shape from the following guides and examples.
How to create and use variables in Processes
Data types in Frends Processes
## Examples - Shared State Task You can learn more about Shared State Task from the following guides and examples.
How to store an authentication token to cache
Performing execution lock in Frends Processes
## Examples - DMN Task You can learn more about DMN Task shape from the following guides and examples.
How to use DMN in a Process
## Examples - AI Connector You can learn more about AI Connector from the following guides and examples.
How to use AI as part of your Process
## Examples - Scope You can learn more about Scope shape from the following guides and examples.
How to handle errors in Processes
## Examples - Foreach You can learn more about Foreach shape from the following guides and examples.
How to iterate through all rows of a dataset
## Examples - While You can learn more about While shape from the following guides and examples.
How to iterate until operation is a success
## Examples - File Trigger You can learn more about File Trigger from the following guides and examples.
## Examples - Schedule Trigger You can learn more about Schedule Trigger from the following guides and examples.
How to run a process automatically
## Examples - Conditional Trigger You can learn more about Conditional Trigger from the following guides and examples.
How to use complex criteria for starting a Process
## Examples - HTTP Trigger You can learn more about HTTP Trigger from the following guides and examples.
How to handle HTTP requests with Frends
## Examples - API Trigger You can learn more about API Trigger from the following guides and examples.
How to handle HTTP requests with Frends
Creating API with Frends
## Examples - AMQP Trigger You can learn more about AMQP Trigger from the following guides and examples.
How to listen for message queues
## Examples - Service Bus Trigger You can learn more about Service Bus Trigger from the following guides and examples.
How to listen for message queues
## Examples - RabbitMQ Trigger You can learn more about RabbitMQ Trigger from the following guides and examples.
How to listen for message queues
## Examples - Azure Event Hub Trigger You can learn more about Azure Event Hub Trigger from the following guides and examples.
How to listen for message queues
--- # 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.frends.com/reference/frends-6.1.0/examples-snippets.md?ask= ``` 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.