getting part 2 links out and a few fixes

content/en/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_intro.md

@@ -42,6 +42,8 @@ I will eventually go over and document all of the things, but I can only write s
 
 And without further adieu - <a href="https://www.lindsaytshelton.com/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_part1/">here's Part 1</a>!
 
+<a href="https://www.lindsaytshelton.com/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_part2/">Part 2 - Conversation Start</a>
+
 <!-- Google tag (gtag.js) -->
 <script async src="https://www.googletagmanager.com/gtag/js?id=G-CN3PDT3T20"></script>
 <script>

content/en/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_part1.md

@@ -79,6 +79,8 @@ This allows you to follow along with the topic and nodes (the blocks) as the con
 *	As the copilot is running a test conversation, click “Variables” and click “Test” to see the values of the variables (both global and topic) as you go.  You can’t see system variables this way, so those you would just have to put into a “Send a message” node to see their values temporarily.
 ![Placeholder](/images/concept_to_chatbot15.png)
 
+I’ll see you in part 2, where we get into the nitty-gritty of the first topic, <a href="https://www.lindsaytshelton.com/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_part2/">Conversation Start</a>!
+
 
 <!-- Google tag (gtag.js) -->
 <script async src="https://www.googletagmanager.com/gtag/js?id=G-CN3PDT3T20"></script>

content/en/blog/202409from_concept_to_chatbot_servicenow_with_copilot_studio_part2.md

@@ -1,6 +1,6 @@
 ---
 title: "From Concept to Chatbot: ServiceNow with Copilot Studio - Part 2"
-date: 2024-09-100T09:29:05-05:00
+date: 2024-09-10T09:29:05-05:00
 draft: false
 author: "Lindsay Shelton"
 tags: ["power automate", "copilot studio", "service-now", "how to"]
@@ -38,7 +38,7 @@ This flow just has two actions in it after the trigger - a premium HTTP call and
 
 This is the entire flow!  The hardest parts are getting the HTTP call right, getting your authorization working, and the formula to return just the sys_id, but I've got you covered for all three.
 
-* HTTP Call: https://<insert your instance name here>.service-now.com/api/now/table/sys_user?sysparm_query=email=@{triggerBody()['text']} AKA https://<insert your instance name here>.service-now.com/api/now/table/sys_user?sysparm_query=email=<dynamic content for Email input>.  This is a GET call.  Set your headers just like mine in the picture.
+* HTTP Call: https://<insert your instance name here>.service-now.com/api/now/table/sys_user?sysparm_query=email=@{triggerBody()['text']} AKA https://{insert your instance name here}service-now.com/api/now/table/sys_user?sysparm_query=email={dynamic content for Email input}.  This is a GET call.  Set your headers just like mine in the picture.
 * Authorization: I used Raw as the method (expand "Show advanced options") and put my username and password into one string like this: username:password.  I then took "username:password" and used a Base 64 encoder website to encode the value.  Then for the Raw value, you just put the word "Basic " and then your encoded username/password.
 * Return value to Power Virtual Agents/Respond to Copilot: This is where you will put the formula to return just the sys_id.  This is what I used: body('HTTP')?['result'][0]['sys_id']