Implementation Agent

The Implementation Agent generates your connectors, flows and resolves schema mappings automatically - no manual configuration required.

The Implementation Agent is active on your account. Access it from connector builder, process flow or mapping via the AI icon.

How it works

The Implementation Agent is accessed through a chat panel, primarily from within the Patchworks canvas on the left-hand side. It can also be opened from the Connector Builder and mapping screens (both shown further down this page). You describe what you want to build — for example, "Build a Shopify to NetSuite order flow" or "Map Shopify to NetSuite order fields" — and the agent builds it step by step.

Because the agent has access to your connector configurations and available endpoints, it can make sensible decisions about which connectors to use, how shapes should connect, and what mappings are needed - surfacing any ambiguities for you to confirm rather than guessing.

You can also give the agent files to work from - a specification, a sample payload, or a screenshot - see attachments.

Flow Builder

Flow Builder lets you generate a complete integration flow from a single prompt. Describe the systems involved and what you want to move between them, and the agent constructs the full flow on the canvas - trigger, connector steps, mappings and all.

1

Open a new or existing process flow

Navigate to Process Flows and open the canvas. The AI assistant panel appears on the left-hand side.

2

Describe your integration

Type what you want to build - e.g. "Build a flow to sync Shopify orders to NetSuite every hour". Be as specific or as high-level as you like.

3

Review and confirm

The agent builds the flow step by step, surfacing any decisions that need your input (e.g. which connector instance to use). Confirm or adjust as needed.

4

Iterate with follow-up prompts

Once the initial flow is built, continue the conversation to refine it - add filters, change triggers, or ask the agent to build the mapping data.

Flow Builder works best when your connectors are already set up and authenticated but can also grab from the Marketplace.

Smart Mapping

Smart Mapping handles schema translation between systems. Once a flow is built, you can ask the agent to resolve the field-by-field mapping between your source and destination connectors - it reads the schemas, works out the appropriate field matches and transformations, and builds the mapping for you.

You can also use Smart Mapping independently, opening the Map Builder panel within any mapping step and describing the changes you want to make.

1

Automatically resolves field names across different system schemas

2

Applies appropriate transformations (format conversions, string casting, fallbacks)

3

Handles multi-source fields - e.g. combining first and last name into a full name field

4

Works iteratively - describe changes to update an existing mapping

Attachments

Both Flow Builder and Smart Mapping accept file attachments alongside your prompt, so you can give the agent something to work from rather than describing it.

Typical uses:

• An integration specification, so the agent builds to a documented requirement

• A sample payload from the source or destination system, so field names and structure come from real data

• A screenshot of an existing configuration you want to reproduce

Supported file types and limits are summarised below:

Property	Detail
Supported file types	PDF, JPEG, PNG, GIF, WebP, JSON, TXT
Maximum file size	2 MB per file

Where an attachment and prompt together are interpreted as a request to build a flow, the agent responds with its understanding and a proposal of what it intends to build - so you can confirm it has read the file correctly before anything is created.

If the agent intends to build a new or different flow in the context of an existing one, it will ask for your approval before removing any existing steps.

Connector Builder

Generate a complete, ready-to-use connector from a description.

Describe the API you want to connect to and the agent researches it, maps the endpoints, detects the authentication method and required variables, and builds the connector configuration for you - no Postman Collection / OpenAPI spec or manual setup required.

1

Create a new connector

From Manage Connectors, select Create new connector.

2

Describe the API

On the Discover step, type what you want to build - e.g. “Build a NetSuite Connector” - and select Build. The AI searches for a specification and uses it to generate your connector. Prefer to set it up yourself? Use Import OpenAPI, Import Postman, or Build manually.

3

Let the AI research and build

The agent constructs the connector for you - usually in under 30 seconds. It checks the Patchworks marketplace, searches for endpoint collections, fetches brand assets, extracts authentication methods, maps endpoints and parameters, identifies required variables, and generates the configuration.

4

Review & edit

Check the detected authentication method, variables, and endpoints. Up to 20 initial endpoints are generated here; if the API has more, they’re discovered and added automatically in the background. Select Looks good, continue, or use Edit details to adjust.

5

Authenticate

Enter the credentials for your new connector instance. Fill in the Connection Settings (e.g. Account ID and Base URL) and the authentication details detected for the API - for example, OAuth 2.0 Client Credentials.

6

Deploy

Once authenticated, your connector is ready to use with all of its configured endpoints. Select Build a flow with it to jump straight into Flow Builder, or New connector to build another.

7

Manage instances

Your new connector now appears in your connector library. Use Add new instance to create additional authenticated instances (e.g. staging vs production), or Export / Upload to share it across accounts.

Connector Builder AI via Flow Builder

You don’t have to build connectors up front. When you ask the Implementation Agent to build a flow, it can build the connectors that flow needs at the same time -calling Connector Builder AI in the background as part of the same conversation.

For example, prompt the agent with “Build a Shopify to NetSuite order flow” and “Map Shopify to NetSuite order fields”, and ask it to create any connectors it’s missing. The agent builds the new connectors, creates placeholder instances and mapping steps, and assembles the full flow on the canvas - all in one pass.

Tips & best practices

Be specific about connector instances. If you have multiple instances of the same connector (e.g. Shopify staging vs production), mention which one you want the agent to use. If you don't specify, it will ask.

Build flows and mappings in sequence. Ask the agent to build the flow structure first, then follow up with "Build the mapping data" as a second prompt. This gives cleaner results than trying to do both in one step.

Connector Builder AI works best for APIs with a published OpenAPI / Swagger specification. For APIs without one, use Import Postman or Build manually to configure endpoints yourself.

Always review before activating. The Implementation Agent builds flows based on your description and available connectors, but you should review the generated steps and mappings before setting a flow live in production.