Build an order-processing integration for a low-code platform from API specs

A Frends integration architect had Claude generate a scheduled order process and eight MCP tool processes for a hackathon challenge; it got 18 of 20 messy orders right for about five dollars.

Done withClaude· Nov 16, 2026

What they did

Ossi Galkin, an integration architect at Frends, tried the Frends MCP hackathon challenge after it closed. Instead of connecting Claude to a Frends tenant through the platform MCP, he used Claude in the plain web chat with one skill he maintains, which teaches a model how Frends works and writes processes as import files. He pasted in the API portal descriptions and the OpenAPI specs for the PIM, CRM, ERP and customer service APIs the challenge used. Claude produced one scheduled process that reads open orders, has Frends' built-in LLM step work out each fuzzy order message and posts the batch to the ERP, plus eight small processes exposed as MCP tools for product lookups, bill of material checks, account notes and asking the customer a question.

How it went

Claude got it nearly right on the first try. Galkin imported the files by hand, pasted each import error back, and re-imported fixes; it took about an hour and a half to get everything running. The solution ran for roughly half an hour, used a few hundred Frends credits, and got 18 of 20 orders valid, plus 4 of 5 in the bonus round where it had to chat with the customer. He did not iterate further. The diagrams looked tidy, but he called the C# inside the code elements unfit to show anyone.

Worth knowing

The author works at Frends and wrote the skill, so read the enthusiasm with that in mind. He put the API key in the prompt by mistake; Claude moved it to environment variables. The token cost showed 0.31 USD that day and 7.16 USD a few days later. Asked for a post-mortem, Claude listed six import failures the skill had let through and noticed the skill's own test file ran no tests.

Try it

With Claude· 4 parts to fill in

I need an integration on [integration platform] that solves this: [describe the task, e.g. process open orders from free-text messages]. Here are the API descriptions and OpenAPI specs: [paste specs]. Generate the processes as import files: one main [scheduled or triggered] process and one small process per API call the model will need. Keep secrets in environment variables, never in the files. I will import each file and paste back any errors; fix only what the error points to. When all files import cleanly, list the parts of the generated code you are least sure about.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related