Menu

1 / 2

A non-engineer CEO connected Copilot Studio to LDX hub. It took 8 errors and 3 hours. Here's the full log.

DEV Community·Kozo-KI·6 months ago
#aAOXE9AS
#ai#powerautomate#ldxhub#cause#connector
Reading 0:00
15s threshold

I'm the CEO of a translation company. Not an engineer.

In Part 1 , I tried to connect Copilot Studio to LDX hub's StructFlow API and hit a wall before getting anything to work. This is Part 2 — the completion.

It works now.

I pasted meeting minutes into a Copilot Studio chat. It returned structured action items with assignees, tasks, and deadlines. It even interpreted "next week" as a specific date (May 8, Friday) based on the meeting date — and flagged it as an assumption for me to verify.

Here's everything that happened between Part 1 and that result.

The root cause of BadGateway

The HTTP action I'd been using — "Send an HTTP request" — was actually routed through the Office 365 Users connector , not a raw HTTP connector. That's why every request to LDX hub returned BadGateway.

The fix: use the green HTTP connector under "Built-in tools" in Power Automate. It looks similar to the white Office connector but behaves completely differently.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.