Map your own fields: the wizard that turns intake into a real integration spec
by Green Dolphin Software, Integration practice
Most integration projects spend the first week arguing about field mappings in spreadsheets. We moved that into the product. After you describe what to connect, you get an optional, two-minute field-mapping wizard — and it is the part customers fall in love with. Here is the whole thing in three minutes.
1. Pick the source and target
Choose the system and object you are reading from — say Salesforce / Opportunity — and where it should land, like Snowflake / SALES_OPPORTUNITIES. The wizard shows you the real fields on each side, so there is no guessing about what exists.
2. Let AI suggest the mapping
One click on Suggest with AI and the wizard matches the fields for you: Id → ID, Amount → AMOUNT_USD, StageName → STAGE, CloseDate → CLOSE_DATE, OwnerId → OWNER. It even proposes the right transforms — Amount becomes a float, StageName gets uppercased. You stay in control: change any target, add a row, or drop one.
3. Add transforms — with a live preview
Need to trim whitespace, change a type, or normalize a value? Pick a transform and watch the result update live in the preview box (" Acme, Inc " → trim → "Acme, Inc"). No code, no waiting for a build to see whether your rule is right.
4. Save a versioned spec
Hit Save and you have a versioned mapping you can roll back to. Nothing runs from here — your architect confirms it in the SOW — but you have just handed us a precise, unambiguous spec instead of a vague paragraph. That is days off the front of the engagement.
Why it matters
The hardest, most error-prone part of any integration is the field-level detail. Putting it in a wizard — with AI suggestions, live transforms, and versioning — turns a back-and-forth into a two-minute, self-serve step. It is the difference between "we'll figure out the mapping later" and "here is exactly what we want."
Try the mapping wizard — or tell us what to connect and we'll take it from there.