Introduction to Zuper
Zuper is a field service management platform that helps businesses schedule, dispatch, and manage field technicians and service jobs, with tools for work orders, invoicing, and customer communication.
Used by businesses in home services, utilities, HVAC, and other field-service industries that need to coordinate mobile workforces
Popular with operations teams that want end-to-end visibility into job status, technician location, and customer communication from one platform
Connecting Zuper to iPaaS.com enables field service job, customer, and invoicing data to flow into your ERP, POS, CRM, and Ecommerce systems automatically, keeping back-office records accurate without manual data transfer
API Version Support
The integration works with your account's Zuper API. Zuper's base URL is region-specific and is discovered per account through the Zuper Config API (for example, https://us-west-1c.zuperpro.com/api), so the address the integration uses is determined by your account. Zuper does not publish a stable, versioned public API namespace, so the integration is built against Zuper's documented production endpoints. Records captured from Zuper (invoices, deposit tickets, and jobs) can be driven by Zuper webhooks, while records sent to Zuper are driven by iPaaS.com outbound triggers and Manual Sync. See the Zuper Connections and Settings and Zuper API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Zuper, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Zuper
← iPaaS.com reads the data from Zuper
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Zuper when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Zuper | Allow Initialization? |
Product | → | Product | |
Product Category | → | Product Category | |
Product Inventory | → | Product Stock | |
Location | → | Location | ✔️ |
Customer | ←→ | Customer | |
Employee | → | Employee | |
Invoice | ← | Invoice | |
Deposit Ticket | ← | Deposit Ticket | |
Job | ← | Job |
Customers carry their addresses. Invoices, deposit tickets, and jobs are captured from Zuper as transactions, with their line items, addresses, taxes, payments, and notes; the three are separated by filters (deposit tickets are invoices whose number ends in -D), and each has its own capture collection. Bulk initialization is available for Locations only; all other data is synchronized individually.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.
Version | Release Notes |
1.0 (current) | Sends products (with categories and stock), locations, customers, and employees to Zuper, and captures invoices, deposit tickets, and jobs from Zuper into iPaaS.com. |
Features by Release
The capabilities below reflect the current 1.0 integration. For the current behavior and any limitations of a given feature, see the linked reference articles and the Zuper Integration Known Limitations article.
Version 1.0 (current) — Field-service jobs, billing, and back-office sync
Product synchronization: products with their categories and standalone stock updates.
Locations: service locations, with support for a bulk initialization.
Customer synchronization: customers written to Zuper, and captured from Zuper into iPaaS.com.
Employee synchronization: employees written to Zuper.
Invoice capture: invoices captured from Zuper.
Deposit ticket capture: deposit tickets (invoices whose number ends in
-D).Job capture: field-service jobs captured from Zuper.