Hero - Build your bot

Integrations are a reusable set of scripts that can be written once and used many times within flows throughout the solution. Most commonly, they are used to connect to external services. For example, your bot may want to provide weather information and use an integration to connect to a weather service.

Integrations are added at the solution level by clicking on the 'Solution' button in the top left, selecting 'Resources', and choosing 'Integrations'.

![1-integration script](//images.ctfassets.net/2vbtnveccz5s/3cnjJXED8VO96FwDfjqTnz/6dd89b3c61a27b2fe4c93e71d42158ab/1-integration_script.PNG)

## Methods

Every integration can contain one or more methods. For example, a weather integration might have two methods; 'Get current weather' and 'Get weather forecast'.  

Each method has a name and an optional description. Additionally, each method can contain input and output parameters and a script.

### Input parameters

Input parameters allow your method to receive information from a flow. The ‘Get current weather’ method for a weather integration could, for example, have an input parameter ‘city’. A ‘Get weather’ flow extracts the city from the user’s input and passes it on to the integration via an input parameter. The input parameters can be strings, lists, objects, etc. The type depends on the type of the variable that was transferred by the flow. Input parameters are optional. Their names cannot contain spaces.

### Output parameters

Output parameters allow your method to send information back to a flow. The ‘Get current weather’ method could, for example, have two output parameters ‘weatherTemperature’ and ‘weatherDescription’ which can be used by the ‘Get weather’ flow in the final answer. Just as input parameters, output parameters can be strings, lists, objects, etc. Output parameters are optional and their names cannot contain spaces.

### Script

This is the script that will be executed when the integration is called by a flow. Both the integration's input parameters and the solution's global variables are available inside the script. For example, the script node of a 'Get current weather' method might receive a location as an input parameter and use a global variable to determine the user's preference for Fahrenheit or Celsius. A method's script can populate its output parameters as well as global variables.

!!! Integrations are widely used while creating Backend Connectors. Please see [Resources](/resources) for more examples.

## Adding an integration to a flow

Once the integration is saved, it is available in the ribbon when a flow is opened in Edit mode. From there, it can be used in a flow where the required method can be selected and the relevant flow variables can be assigned to input and output parameters.

For an example of how to add an integration to your solution and use it in a flow, see [How to add an integration](/studio/scripting/how-to/add-an-integration).


Integration manager

Integrations are a reusable set of scripts that can be written once and used many times within flows throughout the solution. Most commonly, they are used to connect to external services. For example, your bot may want to provide weather information and use an integration to connect to a weather service.

Integrations are added at the solution level by clicking on the 'Solution' button in the top left, selecting 'Resources', and choosing 'Integrations'.

![integration-manager-sw](//images.ctfassets.net/2vbtnveccz5s/dUTTWnPPNFJXUFW4gFf6I/4c8141c42806b449834f79ab77bd725b/integration-manager-sw.png)

## Methods

Every integration can contain one or more methods. For example, a weather integration might have two methods; 'Get current weather' and 'Get weather forecast'.  

Each method has a name and an optional description. Additionally, each method can contain input and output parameters and a script.

### Input parameters

Input parameters allow your method to receive information from a flow. The ‘Get current weather’ method for a weather integration could, for example, have an input parameter ‘city’. A ‘Get weather’ flow extracts the city from the user’s input and passes it on to the integration via an input parameter. The input parameters can be strings, lists, objects, etc. The type depends on the type of the variable that was transferred by the flow. Input parameters are optional. Their names cannot contain spaces.

### Output parameters

Output parameters allow your method to send information back to a flow. The ‘Get current weather’ method could, for example, have two output parameters ‘weatherTemperature’ and ‘weatherDescription’ which can be used by the ‘Get weather’ flow in the final answer. Just as input parameters, output parameters can be strings, lists, objects, etc. Output parameters are optional and their names cannot contain spaces.

### Script

This is the script that will be executed when the integration is called by a flow. Both the integration's input parameters and the solution's global variables are available inside the script. For example, the script node of a 'Get current weather' method might receive a location as an input parameter and use a global variable to determine the user's preference for Fahrenheit or Celsius. A method's script can populate its output parameters as well as global variables.

!!! Integrations are widely used while creating Backend Connectors. Please see [Resources](/resources) for more examples.

## Adding an integration to a flow

Once the integration is saved, it is available in the ribbon when a flow is opened in Edit mode. From there, it can be used in a flow where the required method can be selected and the relevant flow variables can be assigned to input and output parameters.

For an example of how to add an integration to your solution and use it in a flow, see [How to add an integration](/studio/scripting/how-to/add-an-integration).


Studio Web - Integration manager

Integration manager - Article

Build - Integration manager

Analyze your bot

Analyze Log Data

Analyzing sessions

Augmenters

Concepts

Extract values with Augmenters

How To

Metadata

Running custom queries

Counting coffees with Metadata

Reference

Teneo Query Language Cookbook

Teneo Query Language Reference Guide

Teneo Query Language Syntax Overview

Teneo Query Language

Data hierarchy

Event

Property

Session

Transaction

How to

Explore session statistics

Find stuck flows

Generate session logs

Locate and view a session

Make use of skip constraints

Make use of sub queries

Query variables

Troubleshoot the Safetynet

Use relative dates in queries

Query Syntax

Command

Constraint

Meta-parameter

Selection

Transformer

Build your bot

Bot design

Best practices

Data footprint

Encrypting user data in sessions

Flow checklist

Plan your bot

Starting a new Teneo project

Writing good answers

Writing good examples

Conversations

Context restrictions

Flow stack

Greeting message

Listeners

Safetynet

Trigger Ordering

Create a custom order group

Handle ambiguous inputs

Make your bot pro-active

Share information between flows

Use listeners

Flows

Bulk Import

Entities

Junctions

Outputs

Sub-Flows

Transitions

Intent triggers

Variables

Add a script to your flow

Branch at the beginning of a flow

Use TLML Syntax Match

Use a Sub-Flow

Use Bulk Import

Language Understanding

Annotations

Attached scripts

Language conditions

Language objects

Languages

Lexical resources

Libraries

Linguistic Modeling Language

Localization

Match requirements

Used words

Combine Match requirements

Create a solution in your language

Create your own language objects

Find language objects and entities

Localize a bot

Normalize the user's spelling

Optimize language conditions

Recognize plural and singular

Store what the user said

Advanced Condition Coding

Annotations Reference

Condition Syntax Reference

DateTime Handler

Engine Scripting API Reference

Input Processing Path

Language Object Reference

Scripting

Engine scripting API

Groovy basics

Resource file manager

Scripts

Add a Groovy class

Add an integration

Add files to your solution

Annotate user inputs

Anonymize user data

Define a scripted context

Populate output parameters

Store input parameters

Test your bot

Run automated tests

Test your bot with Botium

Dialog Tester

Deploy your bot

Engine API

Versioning and Publishing

Publish your bot

Version Flags

Work with Version Flags

SDK's

Android

JavaScript

Node.js

Getting started

After Match

Extract Entities

Class Manager

Introduction to transitions

Introduction to entities

Deal with Follow-ups

Dialogue and Context Model

Getting started with Teneo

Handle interruptions

Skip conditions

Teneo in 10 minutes

Flows and match requirements

Entities and After Match

Your First Flow

Your First Solution

Optimize your bot

Optimize classes

Improve the balance

Review Inputs

Refine your bot

Debug your bot in Tryout

Use data to improve your bot

Use Teneo's improvement tips

Troubleshooting

My flow doesn't trigger

My flow behaves unexpectedly

I see warnings in Tryout

Suggestions

root

Table of Contents