You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-video-indexer/logic-apps-connector-arm-accounts.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,17 +12,19 @@ Azure Video Indexer (AVI) [REST API](https://api-portal.videoindexer.ai/api-deta
12
12
13
13
You can use the connectors to set up custom workflows to effectively index and extract insights from a large amount of video and audio files, without writing a single line of code. Furthermore, using the connectors for the integration gives you better visibility on the health of your workflow and an easy way to debug it.
14
14
15
+
> [!TIP]
16
+
> If you are using a classic AVI account, see [Logic Apps connector with classic-based AVI accounts](logic-apps-connector-tutorial.md).
17
+
18
+
## Get started with the Azure Video Indexer connectors
19
+
15
20
To help you get started quickly with the Azure Video Indexer connectors, the example in this article creates Logic App flows. The Logic App and Power Automate capabilities and their editors are almost identical, thus the diagrams and explanations are applicable to both. The example in this article is based on the ARM AVI account. If you're working with a classic account, see [Logic App connectors with classic-based AVI accounts](logic-apps-connector-tutorial.md).
16
21
17
22
The "upload and index your video automatically" scenario covered in this article is composed of two different flows that work together. The "two flow" approach is used to support async upload and indexing of larger files effectively.
18
23
19
24
* The first flow is triggered when a blob is added or modified in an Azure Storage account. It uploads the new file to Azure Video Indexer with a callback URL to send a notification once the indexing operation completes.
20
25
* The second flow is triggered based on the callback URL and saves the extracted insights back to a JSON file in Azure Storage.
21
26
22
-
> [!NOTE]
23
-
> For details about the Azure Video Indexer REST ARM API and the request/response examples, see [API](https://aka.ms/avam-arm-api). For example, [Generate an Azure Video Indexer access token](/rest/api/videoindexer/generate/access-token?tabs=HTTP). Press **Try it** to get the correct values for your account.
24
-
>
25
-
> If you are using a classic AVI account, see [Logic Apps connector with classic-based AVI accounts](logic-apps-connector-tutorial.md).
27
+
The logic apps that you create in this article, contain one flow per app. The second section ("**Create a second flow - JSON extraction**") explains how to connect the two.
26
28
27
29
## Prerequisites
28
30
@@ -160,13 +162,15 @@ The following image shows the first flow:
160
162
|----|----|
161
163
|Location| Location of the associated the Azure Video Indexer account.|
162
164
| Account ID| Account ID of the associated Azure Video Indexer account. You can find the **Account ID** in the **Overview** page of your account, in the Azure portal. Or, the **Account settings** tab, left of the [Azure Video Indexer website](https://www.videoindexer.ai/).|
163
-
|Access Token|Select **accessToken** from the **dynamic content** of the **Parse JSON** action.|
165
+
|Access Token|Use the `body('HTTP')['accessToken']` expression to extract the access token in the right format from the previous HTTP call.|
164
166
| Video Name| Select **List of Files Name** from the dynamic content of **When a blob is added or modified** action. |
165
167
|Video URL|Select **Web Url** from the dynamic content of **Create SAS URI by path** action.|
166
168
| Body| Can be left as default.|
167
169
168
170

169
171
172
+
Select **Save**.
173
+
170
174
The completion of the uploading and indexing from the first flow will send an HTTP request with the correct callback URL to trigger the second flow. Then, it will retrieve the insights generated by Azure Video Indexer. In this example, it will store the output of your indexing job in your Azure Storage. However, it's up to you what you do with the output.
0 commit comments