I'm the CEO of a translation company. I'm not an engineer. I can read code, but I can't write it.

That's the context for everything that follows.

LDX hub recently launched plugins for n8n, Dify, and Copilot Studio, making it possible to call StructFlow — their structured data extraction API — from no-code workflow tools. I decided to try it myself instead of delegating.

Spoiler: it's not working yet. But I'm publishing this anyway, because a record of where things broke is more useful than a "it all went smoothly" writeup.

What I was trying to build

Goal: An agent in Copilot Studio that takes meeting minutes as input and returns structured action items.

Stack:

• Microsoft Copilot Studio (agent)
• Power Automate (flow / middleware)
• LDX hub StructFlow (REST API)

Approach: REST API first. If that works, compare with MCP.

The architecture

User (Copilot Studio chat)
    ↓  pastes meeting minutes
Power Automate flow
    ↓  POST to StructFlow API
LDX hub StructFlow
    ↓  returns structured JSON
Power Automate flow
    ↓  passes result back
User (receives action items)

Straightforward on paper. Less so in practice.

Building the Power Automate flow

Finding the right trigger

Opened make.powerautomate.com, selected "Instant cloud flow."

First blocker: "Power Virtual Agents" trigger wasn't visible.

There was no search box on the trigger selection screen. I scrolled through the list and eventually found it. The label was slightly different from what the documentation described. Found it, selected it, moved on.

Input variable

Added a text input variable called minutes_text to the trigger. No issues here.

HTTP action

Added "Send an HTTP request" and configured:

• URI: https://your-ldxhub-host.d2.zuplo.dev/structflow/jobs
• Method: POST
• Header: Authorization: Bearer {API_KEY}

Second blocker: the header field format.

Instead of separate "key" and "value" fields, this action uses a single text field per header, formatted as HeaderName: HeaderValue. So the Authorization header goes in as:

Authorization: Bearer your-api-key-here

Not obvious if you're used to other HTTP tools.

Polling loop

StructFlow is asynchronous. You POST a job, get back a job_id, and need to poll until status: "completed" before you can retrieve results.

In Power Automate, this means a Do until loop. The structure:

1. Initialize variable job_id (string)
2. Set variable — extract job_id from HTTP response
3. Delay 5 seconds
4. Initialize variable job_status (string)
5. Do until loop:
   • GET request to check job status
   • Set job_status from response
   • Stop condition: job_status equals completed
6. Return result to Copilot Studio

Third blocker: the browser back button deletes your flow.

I hit the back button before saving. The flow was gone. Started over.

Lesson: save constantly in Power Automate. There's no autosave equivalent to what you'd expect from a modern web app.

The Do until condition also caused an error when I tried to reference job_status via the GUI. Fixed it by switching to "Edit in advanced mode" and typing the expression directly:

@equals(job_status, 'completed')

The flow eventually completed. Green banner: "Your flow is ready to run."

Connecting to Copilot Studio

Created an agent called "Minutes Assistant" in Copilot Studio.

Observation: the default model was Claude Sonnet 4.6.

Our company uses Claude Team, so Microsoft apparently picked it up automatically. Our enterprise agent running on Claude — mildly amusing given the context of this article.

Now for the main blocker: the Power Automate flow didn't appear in Copilot Studio's tool list.

Same environment, same account. The flow just wasn't visible. I tried searching, browsing the Workflow tab — nothing.

Explored the sidebar and found "Flows" → "Agent flows" — a feature where you describe what you want in natural language and AI generates a flow. The AI generated something instantly, but the action it created pointed to an unrecognizable internal ID — certainly not the StructFlow API in any recognizable form.

Where things stand

What tripped me up:

1. No autosave — browser back = flow gone
2. Single-field header format — Key: Value in one box, not two
3. Flow not visible in Copilot Studio — same environment, still not showing
4. AI-generated flow — unclear what API it's actually calling

What's next

• Inspect the AI-generated agent flow to see what it's actually calling
• Test whether StructFlow is being invoked correctly
• If it works: run it against real meeting minutes
• Part 2 will cover the full resolution (and MCP comparison)

I'll publish the follow-up when it actually works. This one ends here — unresolved, on purpose.

Kawamura International is a translation and localization company. We're documenting our AI process experiments as we go — StructFlow, RefineLoop, RenderOCR, and whatever comes next.