Otto.bot
Otto is an easy-to-train chatbot which answers questions and automates the tasks you need done, while never forgetting, never leaving the organization, and working 24/7/365 to help you get more accomplished every single day. AI and automation solutions allow you to get more tasks done every day with more productivity, lower costs, without the constraint of time.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | Otto.bot |
| URL | https://otto.bot |
| support@otto.bot |
| Connector Metadata | |
|---|---|
| Publisher | Otto.bot, LLC |
| Website | https://otto.bot |
| Privacy policy | https://otto.bot/privacy |
| Categories | AI;Productivity |
Otto.bot connector allows users to rapidly build chatbot skills which can run automation workflows, and return one or more conversational updates and results back into the chat conversation dialog as either plain text, markdown text, or within a visually formatted response. Otto.bot provides low-code/no-code capabilities for users to quickly deploy a chatbot with capabilities beyond QnA, by leveraging the ability to retrieve requested information, update databases, send file attachments, automate processes, and even perform Robotic Process Automation (RPA) in response to a conversational request made by an end user. With our enterprise authentication options, businesses can build permission-based bot solutions in addition to anonymous chatbot experiences.
Prerequisites
- An Otto.bot account with at least Client Admin role permission.
- An API Key from Otto Admin Portal.
How to get credentials
- Visit Otto Admin Portal and select the required company from the list.
- Expand the API Keys panel and generate/copy an existing API Key. We recommend naming your keys according to its usage.
- Navigate to the Otto Admin Portal API Skills and select the required skill.
- If the skill returns the result to the user after the execution, ensure Expect Execution Result is enabled.
- Select the View JSON Schema and copy the schema to clipboard.
- Create a new automation workflow with HTTP Request trigger and paste the schema copied above.
- Add required actions to your connector to complete the automation workflow logic.
- Select Otto connector and select Return results to bot action.
- Use the API Key from step 2 and create a new API connection in your automation workflow.
Known issues and limitations
- Every automation workflow initiated from Otto.bot has a unique Request ID/Return Result URL associated with it which is generated from Otto. The workflow cannot be triggered manually.
- If your automation workflow has a successful run, replaying the run would result in an error. As the Request ID is unique per run, replaying the run would result in reusing the ID which leads to the error.
Creating a connection
The connector supports the following authentication types:
| Default | Parameters for creating connection. | All regions | Not shareable |
Default
Applicable: All regions
Parameters for creating connection.
This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.
| Name | Type | Description | Required |
|---|---|---|---|
| API Key | securestring | The API Key for this api | True |
Throttling Limits
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
Actions
| Return results to bot |
Send one or more responses to Otto during the execution of a skill |
| Send file attachments to any URL |
Send file attachments and data to a URL using multipart/form-data encoding. This API is created to support execution flows where the built-in HTTP request connector cannot easily handle multipart/formdata |
Return results to bot
Send one or more responses to Otto during the execution of a skill
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Return Result URL
|
returnResultURL | True | string |
The absolute URL sent from Otto when the skill is triggered. This value is unique per request and is available in the request body. |
|
Adaptive Card Schema
|
$schema | True | string |
The Adaptive Card Schema from https://adaptivecards.io. Must be set to 'https://adaptivecards.io/schemas/adaptive-card.json' |
|
Adaptive Card Actions
|
Adaptive Card Actions | object | ||
|
Adaptive Card Body
|
Adaptive Card Body | object | ||
|
Adaptive Card Type
|
type | True | string |
The Adaptive Card Type. Must be set to 'AdaptiveCard.' |
|
Adaptive Card Version
|
version | True | string |
One of the available versions from https://adaptivecards.io. The elements used in the adaptive card are subject to the adaptive card version set within this result. |
|
Render Preformatted Text
|
renderPreformattedText | boolean |
A boolean field to let Otto render the result as provided to the user. When this flag is enabled, Otto skips markdown, adaptive card processing of the sent result. Example scenarios include rendering tabular, csv formatted text file results. |
|
|
Text
|
text | True | string |
A markdown supported text field. Otto parses the markdown before rendering the content to the user. |
|
End Request
|
endRequest | True | boolean |
A boolean field which instructs Otto to expect multiple responses throughout this request. Set this to false to send multiple responses to Otto throughout the execution of this request. |
Returns
- Body
- Response
Send file attachments to any URL
Send file attachments and data to a URL using multipart/form-data encoding. This API is created to support execution flows where the built-in HTTP request connector cannot easily handle multipart/formdata
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
additionalParameters
|
additionalParameters | True | object |
A JSON object describing the additional fields to send with POST request |
|
apiRequestHeaders
|
apiRequestHeaders | True | object |
A JSON object describing the headers to send with POST request such as Authorization |
|
API URL
|
apiUrl | True | string |
The API URL to send the attachments and data to. |
|
Attachment URL
|
attachmentUrl | True | string |
The URL which contains the attachment content to send to the API URL |
|
Attachment File Name
|
filename | True | string |
The file name of the attachment |
Definitions
Response
| Name | Path | Type | Description |
|---|---|---|---|
|
Result Message
|
message | string |
The result message from Otto when an action is executed. |