Manage artifact metadata in integration accounts with Azure Logic Apps and Enterprise Integration Pack
You can define custom metadata for artifacts in integration accounts and get that metadata during runtime for your logic app to use. For example, you can provide metadata for artifacts, such as partners, agreements, schemas, and maps - all store metadata using key-value pairs.
An Azure subscription. If you don't have a subscription, sign up for a free Azure account.
A basic integration account that has the artifacts where you want to add metadata, for example:
A logic app that's linked to the integration account and artifact metadata you want to use. If your logic app isn't already linked, learn how to link logic apps to integration accounts.
If you don't have a logic app yet, learn how to create logic apps. Add the trigger and actions you want to use for managing artifact metadata. Or, to just try things out, add a trigger such as Request or HTTP to your logic app.
Add metadata to artifacts
Sign in to the Azure portal with your Azure account credentials. Find and open your integration account.
Select the artifact where you want to add metadata, and choose Edit. Enter the metadata details for that artifact, for example:
When you're done, choose OK.
Get artifact metadata
In the Azure portal, open the logic app that's linked to the integration account you want.
In the Logic App Designer, if you're adding the step for getting metadata under the trigger or last action in the workflow, choose New step > Add an action.
In the search box, enter "integration account". Under the search box, choose All. From the actions list, select this action: Integration Account Artifact Lookup - Integration Account
Provide this information for the artifact you want to find:
Property Required Value Description Artifact Type Yes Schema, Map, Partner, Agreement, or a custom type The type for the artifact you want Artifact Name Yes <artifact-name> The name for the artifact you want
For example, suppose you want to get the metadata for a trading partner artifact:
Add the action that you want for handling that metadata, for example:
Under the Integration Account Artifact Lookup action, choose Next step, and select Add an action.
In the search box, enter "http". Under the search box, choose Built-ins, and select this action: HTTP - HTTP
Provide information for the artifact metadata you want to manage.
For example, suppose you want to get the
routingUrlmetadata that's added earlier in this topic. Here are the property values you might specify:
Property Required Value Description Method Yes <operation-to-run> The HTTP operation to run on the artifact. For example, this HTTP action uses the GET method. URI Yes <metadata-location> To access the
routingUrlmetadata value from the artifact you retrieved, you can use an expression, for example:
Headers No <header-values> Any header outputs from the trigger you want to pass into the HTTP action. For example, to pass in the trigger's
headersproperty value: you can use an expression, for example:
Body No <body-content> Any other content you want to pass through the HTTP action's
bodyproperty. This example passes the artifact's
propertiesvalues into the HTTP action:
1. Click inside the Body property so the dynamic content list appears. If no properties appear, choose See more.
2. From the dynamic content list, under Integration Account Artifact Lookup, select Properties.
To check the information you provided for the HTTP action, view your logic app's JSON definition. On the Logic App Designer toolbar, choose Code view so the app's JSON definition appears, for example:
After you switch back to the Logic App Designer, any expressions you used now appear resolved, for example:
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.