{"id":110797,"date":"2017-02-17T03:55:56","date_gmt":"2017-02-17T11:55:56","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/five-services-json-http\/"},"modified":"2017-02-17T03:55:56","modified_gmt":"2017-02-17T11:55:56","slug":"five-services-json-http","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/five-services-json-http\/","title":{"rendered":"Five new services and improved advanced capabilities for JSON and HTTP"},"content":{"rendered":"
This past week we added five new services: Azure Data Lake, Bitbucket, Eventbrite, Infusionsoft and Pipedrive. Azure Data Lake<\/a> allows you to read and add data to an Azure Data Lake account.<\/p>\n Bitbucket<\/a> is a web based hosting service for projects that use GIT revision control.<\/p>\n <\/p>\n With Bitbucket in Microsoft Flow you can now automate many different aspects of your project’s life cycle. From simple tasks like syncing issues into another system, to even automatically approving, declining or merging pull requests.\u00a0<\/p>\n Eventbrite<\/a> is a self-service ticketing platform used to create and discover local events. Eventbrite has triggers on when events or created or when someone orders a ticket for an event. This means you can copy events to other systems or keep a separate log of all the event attendees. Infusionsoft <\/a>is sales and marketing automation software built exclusively for small business success.<\/p>\n Finally,\u00a0Pipedrive<\/a> is a CRM & pipeline management tool that helps you focus on actions that matter. There are actions for adding deals or updating the stage of a deal.<\/p>\n <\/p>\n Although we now connect natively to 95+ different services, you may also have HTTP endpoints that you want to work with that aren’t natively supported with Microsoft Flow. Microsoft Flow has long supported interacting with custom, unauthenticated HTTP endpoints, and today it’s now possible to set up calls to authenticated HTTP endpoints as well.\u00a0To connect to a custom HTTP endpoint, first select the\u00a0HTTP<\/strong>\u00a0service when you add an action:<\/p>\n <\/p>\n There are three possible actions:<\/p>\n <\/p>\n After you have selected the action, select Show advanced options<\/strong>\u00a0and then select Authentication.<\/strong>\u00a0The default is None<\/strong>, but you can choose one of four other types of authentication. After you select the endpoint’s authentication type you will be able to configure any specific data you need to send.\u00a0<\/p>\n When working with the Request trigger or the HTTP actions, you may need to parse out JSON data. This week we added a new data operation called\u00a0Parse JSON<\/strong>. This action takes:<\/p>\n <\/p>\n When the flow runs, it will evaluate the content against the schema. This means you can use the different fields you defined in the schema throughout the rest of your workflow as dynamic content.<\/p>\n To make it easier to generate a JSON schema, we have also added a\u00a0Use sample payload<\/strong>\u00a0button. When you select this button, you can paste in your JSON content and it will attempt to generate a JSON schema that matches that payload. We have also added this new button directly on the HTTP Request card.<\/p>\n Finally, we have added additional options for filtering the runs of your flow. Previously, you could only see succeeded or failed runs when you selected a flow and looked at its history.<\/p>\n <\/p>\n Now, you can also filter to see just the instances that are currently running, or those runs that are cancelled. It is now possible to filter specifically to see failed checks (meaning the trigger did not fire because of an error), or, to see failed runs (meaning one or more of the actions did not execute successfully).<\/p>\n","protected":false},"excerpt":{"rendered":" We five new services in the last week: Azure Data Lake<\/a>, Bitbucket<\/a>, Eventbrite<\/a>, Infusionsoft<\/a> and Pipedrive<\/a>. In the flow designer it’s now possible to use authentication with custom HTTP endpoints, and to parse JSON objects returned from APIs. Finally, we added more options for filtering flow runs.<\/p>\n","protected":false},"author":347,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","power-automate-category":[2752],"power-automate-tag":[],"coauthors":[2913],"class_list":["post-110797","power-automate","type-power-automate","status-publish","hentry","power-automate-category-product-updates"],"yoast_head":"\nDefine HTTP Authentication<\/h2>\n
\n
Parse JSON messages<\/h2>\n
\n
Better filtering for flow runs<\/h2>\n