Broken integrations surface where the team already works, and are fixed without opening the platform.
PatchBuddy Integration Build Agent
A written integration specification becomes working flows and mappings in days.
An agent reads an integration specification and builds the flows, scripts, and mappings from it.
What the agent does
Reads an integration specification and builds the flows, custom scripts, and field mappings from it, rather than a developer writing each one.
- Brand
- Peak Distribution
- Built by
- eCirql by CirqlWorks, a Patchworks systems integrator partner
- Contributed by
- Patchworks (Integration platform and APIs), eCirql (Agent build partner)
- Industry
- Retail, Manufacturing & Industrial
- Audience
- B2B
01
The problem
Why this exists
Integration work starts with a specification and ends with flows, scripts, and field mappings. The translation between the two is mechanical, repetitive, and slow, and it is where an implementation timeline actually goes.
Read more
It is also the work that scales worst. Every new customer needs it again, and the specification is different enough each time that a template does not close the gap.
02
Outcomes
What changes when this is in place
- Peak Distribution in Australia was built out in days.
- The agent produces the flows, custom scripts, and mappings rather than a starting point for them, which is what compresses the timeline.
- The pattern is reusable by the partner across its own customer base, because it works from the specification rather than from a fixed template.
03
How it works
Architecture
PatchBuddy works against the Patchworks APIs as published on the Patchworks website, driving them with the partner's own models. Nothing about the integration is private: it uses the same public interface any integrator would.
Read more
That is the notable property. The agent is built by a Patchworks systems integrator partner, eCirql by CirqlWorks, rather than by Patchworks, and the partner's customers use it directly. An open, documented API surface is what made a third party able to build an agent on top of the platform without the platform vendor's involvement.
Open standards used
REST APIs
Tech stack
Patchworks APIsPatchBuddyPartner-hosted models
Resources
Next step
Request an intro
Patchworks is behind this solution. Ask about building integrations from a spec, and the MACH Alliance will put you in touch with the person who can answer.
Not ready to talk to anyone? MACH Insider is the Alliance mailing list. New solutions, program openings, and the research behind them, once a month.
Everyone credited on this solution
- PatchworksIntegration platform and APIs
- eCirqlAgent build partner
Every organization named here has a page listing the rest of its work on the Agent Solutions Hub.
Related solutions
Stock moves to where demand actually is, cutting stockouts and lost sales across four stores.
Psycho Bunny Store Replenishment Agent
Four recurring workflows run against the live store, lifting conversion from 0.8% to 1.1% in 30 days.
Carsncards Revenue Operations Agent
Verification
Contributor submission
The detail on this page comes from the contributor's own account of their own work. The MACH Alliance reviews a submission before publishing it and does not independently verify the figures in it.
Where this came from
Solution detail is published from the contributor's 2026 Agent Ready submission to the MACH Alliance. Submitter names and contact details are not published.
Status: Live in productionAdded Jul 8, 2026A listing is an editorial decision, not a MACH Alliance certification.
Built something worth showing?
Put your agentic solution in front of the enterprise leaders who use the Agent Solutions Hub to decide what to build next. Submissions are open to MACH Alliance Members, Collaborators, or Ambassadors.