Important
This integration is still under active development, and some setup steps may not yet be available for self-service configuration. If you encounter an error or are unable to proceed, please don't hesitate to contact our support team at support@maxio.com for help.
Note
This integration supports Maxio Core-only implementations. Subscriptions through Advanced Billing are not required. If Maxio CPQ Sign + Pay functionality is needed Maxio Core users must convert to the Maxio Platform Billing Portal with assistance from Maxio Implementation.
RevOps.io is a revenue operations platform that streamlines quote management, pricing approvals, and e-signatures to help SaaS companies automate their quote-to-cash process. This integration synchronizes RevOps.io, Maxio Core, and Advanced Billing. It can generate, approve, and e-sign quotes in RevOps.io while automatically creating Sales Orders, Subscriptions, and Transactions in Maxio, without manual data re-entry.
Here are some of the supported features of this integration:
Sales Order automation
Subscription creation (Advanced Billing only)
Optional Dropbox upload of signed contracts
Payment tokenization for Core and AB billing workflows
Integration Setup
In RevOps.io
Go to Settings > Integrations > Maxio.
Enter the following values:
Namespace – Maxio Core subdomain
Tenant – Maxio Core account name (from your Maxio URL)
Advanced Billing Site URL
Advanced Billing API Key (if applicable)
Maxio.js (formerly Chargify.js) Keys (only if processing payments)
Click Save to confirm the connection.
In Maxio Core
Navigate to Config > Integrations > RevOps.
Click Enable to make the integration available.
Enter your RevOps API Key. (You'll need to make one in RevOps, and make the key type secret)
After validation, your Org ID displays automatically.
(Optional) Enable Auto-Process Sales Orders to process signed deals from RevOps automatically.
Note
You can disconnect or reconnect the integration at any time. Disconnecting clears credentials and pauses data sync.
Advanced Billing Configuration
An integration with Advanced Billing currently requires assistance from a Maxio team member. Please contact your Maxio representative or our support team to see how to enable this integration for your Advanced Billing site.
How It Works
The RevOps.io integration connects your quoting and approval workflows in RevOps.io directly to your Maxio environment. When a deal in RevOps.io reaches the Signed stage, the integration automatically creates or updates the corresponding Sales Order, Customer, and (if applicable) Subscription in Maxio.
During this process, RevOps.io passes essential deal and product information to Maxio, while Maxio enriches the data with CRM context from Salesforce or HubSpot. This ensures accurate, real-time synchronization across your quote, billing, and revenue systems—eliminating manual data entry and maintaining a single source of truth for customer and order data.
SKU Configuration & Product Catalog Mapping
To support correct quoting and downstream sync behavior in CPQ, product codes must be configured to align with their respective systems.
Advanced Billing:
For workflows that rely on Advanced Billing, the first two digits of the product code determine routing logic and system behavior. Use the format:
CP[product_id]for ProductsCC[component_id]for Component
Maxio Core:
For items in Maxio Core, please enter the item code with no prefix.
Optional: CSV Import
For a CSV import, you will need export Maxio product catalog and reformat to match RevOps import format.
Syncing and Connection Health
Once integrated, you can sync deals and Sales Orders automatically or manually.
| Sync Option | Description |
|---|---|
| Auto-Process Sales Orders | Automatically creates Sales Orders when a RevOps deal reaches the “Signed” stage. |
| Manual Sync | Available for testing or troubleshooting. Only Signed deals will sync. |
| Sync Now | Immediate sync available through Maxio Core. If InstaSync is enabled, deals appear automatically once signed. |
Signed Document Handling
Signed agreements are automatically stored as attachments in Maxio. These include the PDF, signature audit trail, and deal metadata. Attachments appear under Customers and Contracts.
Optional Dropbox Integration
If Dropbox is connected, a copy of the signed document automatically uploads to the configured Dropbox folder when the Sales Order processes.
CRM Integration Behavior and Best Practices
The integration supports connected workflows between RevOps, Salesforce, and HubSpot.
When a RevOps deal includes a Salesforce or HubSpot Deal ID and reaches the Signed stage:
The deal is sent to Maxio.
Maxio enriches the Sales Order using native CRM integrations, pulling additional attributes.
The Sales Order processes automatically if auto-processing is enabled.
Field Mapping Reference
| RevOps CPQ Field | Mapped To in Maxio | Description |
|---|---|---|
| Deal ID (Salesforce or HubSpot) | Sales Order ID | Unique identifier of the quote or deal from CRM |
| Deal Name | Sales Order Name | The name or title of the sales order |
| Subtotal from Quote | Order Total | Total value of the quote before taxes and discounts |
| Customer Legal Name | Customer Name | Official name of the company purchasing the service |
| Contact First Name | Customer First Name | First name of the primary contact |
| Contact Last Name | Customer Last Name | Last name of the primary contact |
| Contact Email (Billing or Lead Contact) | Customer Email | Email address of the main billing or sales contact |
| Business Account ID | CPQ Customer ID | Internal reference for the customer in RevOps |
| Salesforce Account ID | Salesforce CRM Customer ID | CRM-specific identifier for the customer (Salesforce) |
| HubSpot Company ID | HubSpot CRM Customer ID | CRM-specific identifier for the customer (HubSpot) |
| Billing Street | Billing Street Address | Customer’s billing street |
| Billing City | Billing City | City listed in billing address |
| Billing State | Billing State | State listed in billing address |
| Billing Postal Code | Billing ZIP Code | ZIP or postal code in billing address |
| Billing Country or Country Code | Billing Country | Country listed in billing address |
| Shipping Street | Shipping Street Address | Customer’s shipping street |
| Shipping City | Shipping City | City listed in shipping address |
| Shipping State | Shipping State | State listed in shipping address |
| Shipping Postal Code | Shipping ZIP Code | ZIP or postal code in shipping address |
| Shipping Country or Country Code | Shipping Country | Country listed in shipping address |
| Currency | Subscription Currency | The billing currency for the subscription |
| Payment Token | Payment Method Token | Tokenized representation of the customer's payment info (e.g., credit card) |
| Payment Type (e.g., Credit Card, ACH) | Payment Method Type | The type of payment method used |
| If Payment Info Exists | Collection Method (Automatic or Remittance) | Defines if Maxio should auto-collect or invoice manually |
Comments
Article is closed for comments.