I’m very pleased to release D365 Posts Bot today! This is the finished article from my earlier series of blog posts on creating a bot to link posts from D365 through to Teams and back again.
Now we’ve got our bot sending out notifications, we want to be able to handle a reply from the user and add it back into D365 as a new post. The adaptive card notification lets the user reply via an embedded form. This makes it nice and neat. When the user fills in this form […]
Now I’ve got my bot sending notifications to Teams, but the display of the messages left something to be desired. This is where Adaptive Cards comes in.
Now we’ve got a notification when a new post is added, we need to figure out who to notify about it. This is the process I’ve come up with:
Now we’ve got the infrastructure sorted for the bot talking to Teams and getting it installed for users, we need to start letting it know when something interesting happens in D365 so the bot can send messages out to users. Enter the WebHook.
Last time I proved I could send a proactive message to myself, but I needed my user ID that I could only get after I’d started a conversation with the bot. For my real-life scenario I need to be able to push notifications to users that haven’t interacted with my bot before.
Last time we managed to get everything we need to push messages to a user by having them install our app in Teams, but to make this really seamless it would be better to push the app out to users automatically.
The key thing I want to do with my bot is to push messages out to users when something happens in D365, not just in response to the user sending a message to the bot. This was the part I was unsure of, but a bit of searching gives me the key phrase Proactive Messages. […]
Before I make any progress with the real logic of my new bot, I need to get the basics set up. I first need to create a simple bot and be able to interact with it from Teams. This is where the whole Azure Bot Framework really shines – I need to know just about […]
At Data8 we’ve successfully used posts on CRM records for some time to share updates. The problem was that people didn’t know when someone had written a post, so they would resort to email instead.