Microsoft Azure Bot Service is a Microsoft service that helps you to create, and manage bots to interact naturally with users on apps, and web-based services.
Integrations and Connectors
AgilePoint NX integrates in these ways with Microsoft Azure Bot Service:
- Activities in Process Builder
- Access tokens
Activities in Process Builder
You can use out-of-the-box activities for Microsoft Azure Bot Service to execute actions in process-based apps.
An activity is a functional unit, or task, in a process-based app. Activities that integrate with a third-party system provide access to the API functionality for that system in a simple, point-and-click, form-entry format. This means that you can easily leverage APIs without writing code.
Process Activities for MS Azure Bot Service
The following activities are available for MS Azure Bot Service:
- Animation Card Attachment
- Audio Card Attachment
- Create Conversation
- Get Conversation Members
- Hero Card Attachment
- Receipt Card Attachment
- Reply To Activity
- Send Message To Conversation
- Sign In Card Attachment
- Thumbnail Card Attachment
- Video Card Attachment
For more information, refer to the process activities for Bot Integration in Process Builder.
Access Tokens
You can create access tokens for Microsoft Azure Bot Service.
An access token is a secure object that stores an endpoint (usually a URL) and authentication credentials to connect to a service or technology. Often this is an external or third-party service, like Salesforce or SharePoint, but access tokens can also connect to an AgilePoint NX enviornment, local database, or other types of technologies. Once an access token is created, app designers can simply select and reuse it, rather than entering the credentials each time they are needed.
For more information, refer to Access Token for Microsoft Azure Bot Service.
MS Azure Bot Service Access Token Configuration screen
Related Topics
Examples
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Microsoft Azure Bot Service Documentation
Use these links to find third-party vendor documentation for Microsoft Azure Bot Service:
About This Page
This page is a navigational feature that can help you find the most important information about this topic from one location. It centralizes access to information about the concept that may be found in different parts of the documentation, provides any videos that may be available for this topic, and facilitates search using synonyms or related terms. Use the links on this page to find the information that is the most relevant to your needs.
Keywords
azure bot service, azure, Microsoft Azure Bot Service, MS Azure Bot Service, bot
Comments
0 comments
Please sign in to leave a comment.