Zuper Mapping Collections
Map data between Zuper and iPaaS.com
8 articles
- iPaaS.com to Zuper Customer Mapping DocumentationHow the Zuper integration writes customer records and their addresses from iPaaS.com to Zuper, including field mappings, ID formats, and setup requirements.
- Zuper to iPaaS.com Customer Mapping DocumentationHow the Zuper to iPaaS.com Customer mapping collection captures customer and address records from Zuper into iPaaS.com, including field mappings, triggers, and validation.
- iPaaS.com to Zuper Product Mapping DocumentationHow the Zuper integration maps iPaaS.com products and their inventory to Zuper, including the product create/update collection, the inventory child collection, the standalone stock-update collection, field mappings, prerequisites, and validation…
- Zuper to iPaaS.com Invoice Mapping DocumentationHow the Zuper to iPaaS.com Invoice mapping collection captures invoice records — with their line items, addresses, notes, payments, and tax — from Zuper into iPaaS.com, including field mappings, filters,…
- Zuper to iPaaS.com Deposit Ticket Mapping DocumentationHow the Zuper to iPaaS.com Deposit Ticket mapping collections capture a Zuper deposit ticket and its lines, addresses, notes, payments, and tax into iPaaS.com, including field mappings, filters, triggers, and…
- Zuper to iPaaS.com Job Mapping DocumentationHow the Zuper integration captures a Zuper job — its product lines, addresses, notes, description, and outstanding-balance entry — into iPaaS.com as a transaction, including field-by-field mappings and filters.
- iPaaS.com to Zuper Employee Mapping DocumentationHow the Zuper integration maps iPaaS.com employee records to Zuper users when data flows from iPaaS.com to Zuper, including the email filter, field mappings, placeholder values to replace before go-live,…
- iPaaS.com to Zuper Location Mapping DocumentationHow the iPaaS.com to Zuper integration creates and updates Zuper product locations from iPaaS.com location records, including ID formats, trigger events, setup requirements, field mappings, and validation steps.