"Run with Payload" option missing in new Logic App Experience

Send the XML directly to the Request trigger’s HTTP endpoint, because the new designer’s Run with payload control expects JSON and changing the trigger content type does not change that input pane to an XML editor.^1^

Test the workflow with XML

For a workflow using When an HTTP request is received:

1. Open the Request trigger in the designer.
2. Copy its HTTP URL.
   • If no URL appears yet, publish/save the workflow first.
3. Send an HTTP request using the method configured on the trigger—typically POST—and set Content-Type to application/xml.^2^
4. For example, using curl:

curl --request POST "<callback-url>" \
  --header "Content-Type: application/xml" \
  --data-binary @payload.xml

Example payload.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Customer>
  <Name>Frank</Name>
  <AccountId>12345</AccountId>
</Customer>

Microsoft’s XML-validation guidance documents this same testing approach: copy the Request trigger endpoint and use an HTTP client to send XML to it.^3^

Treat the callback URL as a secret because it can contain a Shared Access Signature. After sending the request, open Run history and inspect the trigger’s inputs and subsequent action outputs.

Process the XML body

Logic Apps supports application/xml at runtime. Where an action needs an XML value, use:

xml(triggerBody())

To select an XML value directly, for example:

xpath(xml(triggerBody()), '/Customer/Name/text()')

The xml() conversion produces XML content, while xpath() extracts matching nodes or values.^4^

Where “Run with payload” moved

For Standard workflows in the preview designer, Microsoft documents Run and Run with payload at the bottom of the designer. The preview runs the current draft rather than the published production workflow.^5^

The same documentation currently provides this temporary fallback:

1. Open the vertical ellipsis ⋮ beside Publish.
2. Select Revert to previous experience.
3. In the classic designer, use Run with payload from the toolbar.

However, this does not provide a durable answer for XML testing. Current Microsoft examples describe the Run with payload body as JSON, and community reporting identifies non-JSON input as a gap in the new designer.^6^ There is no official source here that supplies an XML-capable replacement in that pane or commits to a delivery date.

Therefore, use direct HTTP invocation for repeatable XML tests rather than depending on the legacy designer. If the bottom control itself is entirely absent—not merely rejecting XML—use ⋮ → Revert to previous experience, then select Info → File a bug in the classic designer to report the preview-designer UI discrepancy.^5^

References

1. Run workflows in Azure Logic Apps from agents in Foundry Agent Service (preview) (portal)
2. Create workflows that you can call, trigger, or nest using HTTPS endpoints in Azure Logic Apps
3. Validate XML using schemas in B2B workflows with Azure Logic Apps
4. Handle content types in Azure Logic Apps
5. Navigate the Standard Workflow Designer - Azure Logic Apps
6. Logic Apps: Run With Payload Only Accepts JSON