Before you start to use our MCP, please review the following items:

Ensure you have completed the iPaaS.com platform training before using this to best understand what is going on. If you need to gain access to it reach out to partnerships@ipaas.com.
With great power comes great responsibility - the MCP can do things like trigger a sync for your entire catalog and modify (or remove) data from your account. Ensure you understand what you want it to do before you work with it. iPaaS.com is not responsible for restoring any data or configuration changes made using the MCP.
Measure twice, cut once: When working with this, planning ahead of time (or asking the MCP to plan for you) will greatly benefit your work.
Remember that this is in beta so some features may be added, removed or altered as we continue our development. The latest change log notes can be found here.
If you have any issues or need to report a bug please reach out to us at mcp@ipaas.com.

Mappings decide how data is translated every time a record moves between iPaaS.com and a connected system. The MCP can read them, compare them, check them before a first sync and, with your confirmation, change them. This guide shows how to do all of that safely.

The pieces

A mapping collection is one data flow: a data type moving in one direction between iPaaS.com and a connected system. A system usually has several for the same data type, one for each sync type (Add, Update, Add/Update and Delete). See Data Domains & Mapping Collection Types.
A field mapping says how one field is filled in. A collection holds many of them.
A translation collection converts values from one system's vocabulary to another's, such as a status or a country, one source value at a time.
Collections can nest. A child collection, such as order lines under an order, syncs as part of its parent.
A collection can have a mapping filter, which is a short condition that decides which records it handles. A record the filter excludes is skipped without an error.

Before you begin

Connect with the right tools. Use /mcp/integration, or /mcp/mappings if you only want mappings (see Choosing Your Tools).
Check your key's permissions (see Getting Started). To review, give it View on Mapping Collection, Mapping, Translation Collection, Translation, Subscription and Lookup. To change things, add Create, Edit or Delete on the ones you will change.
Know what a mapping change does. It changes configuration, not your records. But it changes how every later record syncs, and iPaaS.com has no undo. Read Safety, Permissions and Limits first.

Rules the assistant follows

The assistant is set up with these working rules. They are good habits for you too.

Start from the templates. A subscription comes with its integration's default mapping templates, so the collections and most mappings already exist. Find and change those rather than building a second set. Create a new collection only for a genuinely new flow, and clone one when you need a divergent copy.
Use the simplest mapping type that works. In this order: Field, then Field with Default, then Static, then Lookup Translation, then Dynamic Formula. A formula is the last resort, when none of the first four can do the job.
Make everything readable. A collection filter is a single return condition with a plain-English comment saying which records it keeps. Every mapping and collection gets a description saying what it does and why.
Change one thing at a time, then test it.

Part 1: Reviewing

Find the collection

Ask for the collections for a data type, a connected system and a direction. For example: "Show me the customer collections that send to NetSuite." The assistant searches every page, so a company with hundreds of collections isn't cut short.

Because a system usually has Add, Update and other collections for the same type, and they don't all nest the same way, check which one you mean before you change anything.

Look inside

Ask the assistant to open a collection. It shows the field mappings, and it can show a collection's children and parents too. Ask for a translation collection to see its value pairs.

Check it before the first sync

Ask for a pre-sync review of a collection (it includes its children). Templates ship with values that you have to replace, such as a default location, a tax code or a sales channel, and the platform has no flag for this. The review reads each mapping's description to find them. It reports:

Mappings that ask for client-specific data, shown word for word with the reason.
Static values to confirm.
Mappings with no description, which are hard to trust.
Filters and how the collection handles duplicates.

Compare two collections

Ask the assistant to compare two collections, for example the Add and the Update flow for the same type, or a staging copy against production. It lists the field mappings that differ.

Find what is broken

Ask for invalid mappings. It lists the field mappings the platform flags as broken.

Check what is possible

What does the integration support? Ask whether a data type and directions are supported before you build a flow for it. A flow for something unsupported can look fine and never work.
Can two systems work together? Ask whether system A and system B can exchange a data type, and whether the collections for it already exist.
How does data arrive? Ask whether a system feeds iPaaS.com by webhook or by polling for a data type.
Which fields can be mapped? Ask for the mappable fields for one system and one data type. Ask for a single combination, since the full list covers the whole platform.

Part 2: Changing

Mapping type	Use it when
1. Field	A source field maps straight to a destination field
2. Field with Default	Same, with a fallback when the source is empty
3. Static	The destination always gets the same fixed value
4. Lookup Translation	Values must be converted using a translation table
5. Dynamic Formula	Only when none of the above can express it

Every change below follows the same steps: ask the assistant to explain what it will change, read the preview, then confirm.

Change or add a field mapping

To change one, tell the assistant which mapping and what the new value should be. It fetches the current mapping and merges your change into it, so you only name what changes. To add one, tell it the collection, the destination field and the type. If you aren't sure what a write needs, ask it what the platform requires before it tries.

Copy missing mappings from one collection to another

Ask the assistant to copy the mappings that are in collection A but missing from collection B. It compares the two, previews what it would add, and adds only those.

It refuses if the two collections run in different directions, because the copy would flip source and destination.
If some mappings couldn't be copied, it says so and doesn't report the copy as done.

Clone a collection

Ask for a copy of a collection with its mappings. A reverse clone flips the direction and swaps source and destination. A reverse clone doesn't copy filters or non-field mappings (such as statics and formulas), so check the result and add them back.

Change a collection's own settings

You can change a collection's name, description, sync type and record filter. The tool keeps the filter and the other settings when you change something unrelated, so an unrelated edit can't wipe them.

Add or change translations

Add, change or remove a source-to-destination value pair in a translation collection.
Create a translation collection for one mapped field.
Clone one. A reverse clone flips direction.

Write and test a formula

Get the namespace. Ask the assistant for the formula context for the mapping. This is everything the formula may legally refer to: the source fields (which side they come from depends on the direction), custom fields, presets, the available functions, and whether the destination's current value is available.
Validate. Ask it to check the formula. It catches misspelled or wrongly capitalised names, an unsupported range operator, a missing return and similar mistakes. It grades its confidence instead of declaring a formula invalid, because the platform's own lists of fields and functions are incomplete. A name it can't verify is reported as unverified, with where to look. The platform's Functions article is the first place.
Try it on one real record. Ask it to preview the formula against a record. It shows what the formula produced and sends nothing. It uses a real record from your account, so it asks which one. If the preview comes back empty, the result is "inconclusive", not a pass.

Remove or restore

Deleting a mapping, a translation or a collection is a soft delete. Each has a matching reactivate.
Collections with children. The platform won't disable a parent while its children are active. The assistant refuses, shows you the full ordered plan, and only goes ahead if you agree to disable the children as well. It works from the deepest child up, stops at the first failure, and gives you the reverse order so you can undo it.

After a change

Resync one record that uses the mapping. See Investigating a Failed Sync for how to do it and how to confirm that the record arrived.
Keep the change log from each change. It records the values before and after, which is your only way back.
Then widen. Resync a few more, up to 25 at a time, before you trust the change.

Prompts to start with

"Show me the order collections that send to NetSuite and what each one does."
"Do a pre-sync review of this collection, including its children."
"Compare the Add and Update collections for customers."
"Which mappings in this system are invalid?"
"Plan how I would change this mapping. Don't change anything yet."
"Validate this formula, then preview it on one record."

If something doesn't work

The assistant can't find the collection I expect. Check the data type, system and direction. A direction is from the point of view of iPaaS.com: to iPaaS.com or from iPaaS.com.
A copy was refused. The two collections run in different directions. Use a reverse clone, or copy between collections that match.
I can't disable a collection. It has children. Ask for the plan, and agree to disable the children too if that is what you want.
A record still doesn't sync after the change. A record filter may exclude it, the integration may not support that data type and direction, or the type may only move with its parent. See the failed-sync guide.
You get a 401. Your key lacks a permission for that area. Ask the assistant to check your permissions.

Anything else: mcp@ipaas.com.

iPaaS.com MCP: Guide - Reviewing and Changing Mappings