These are the release notes for features Syncari introduced in March 2022. If you have any questions about these items, please contact customer support.
Each month, we highlight newly released features.
Here’s the list for this month:
- Custom Synapse: Build your own Synapse
- Syncari API: Control Syncari from your code
- Chargebee: A new Synapse for subscription billing
Custom Synapse: Build your own Syncari connector
With over 40 Synapses, Syncari connects to popular CRMs, databases, product data, and financial systems. But what if the data you want to align, activate and analyze lives in a system Syncari doesn’t have a Synapse for? Last month, we introduced Custom Actions, which can be used to send data from Syncari to any end system with an HTTP API. With the March release, we’re taking custom extensibility even further.
Introducing the Syncari Custom Synapse. With a few lines of python code, you can now connect any system to Syncari where it can be unified in our operational data hub and multi-directionally synced. To ensure your Custom Synapse works as intended, we’ll have our experts review it for you as a last step before go-live!
Syncari lets you register your custom Synapse so that it can be used inside the platform
Syncari API: Embed Syncari in your product
At Syncari, we know that custom code doesn’t stop at our Synapses. Many of our customers want to enable Syncari’s rich data sync capabilities for their customers. So we built the Syncari API to let them do just that.
The Syncari API lets you authenticate securely against your Syncari instance and kick off the processes you need without using the user interface. This means you can use Syncari to unify data among multiple systems or update go-to-market systems with updated information from other systems. If you’d like to login to your Syncari instance with the regular login, you can still do that. This Syncari API lets you specify an API-only user that can act on your behalf using code triggered by your external system. Creating and activating synapses, updating pipelines, retrieving schema about entities, and updating datasets are some of the things you can do with the API.
Syncari’s developer API enables you to connect Syncari to your existing code
Chargebee Synapse: Making Subscriptions Easier
Chargebee is a SaaS solution that makes it possible for you to facilitate payments for all kinds of online subscriptions, whether they are product, entitlement, or usage based. Chargebee automates the lead-to-ledger financial process so that you can spend more time on the strategy of your business and less time handling payments.
Our new Chargebee Synapse enables you to integrate Chargebee invoices, orders, and quotes into your Syncari Data Hub. With the Chargebee Synapse, fulfill the revenue promised by a Salesforce or Hubspot opportunity, or create a monthly invoice based on product usage. It’s also easy to take Chargebee information and share that data with your other go-to-market systems to help Customer Success know product behavior or give sellers the information they need to craft compelling new offers.
Connect the Chargebee Synapse to get Chargebee information
We’ve updated these articles in the Syncari Help Center:
These are some of the minor improvements we made to Syncari in March 2022:
- We added a security role for customers who manage multiple instances of Syncari
- We improved visibility for the original function/action name when node name is changed
- Added information to better display the field type on the field pipeline
- Added the ability to see the isReadOnly and isCreateOnly columns in Schema Studio
- Improved the support for the Netsuite synapse to include billing address support, price book fields, and subscription price interval objects
- Synapse nodes are now automatically arranged
We also resolved some issues in the Syncari platform, including:
- Fixed an issue with reviewing details on a merge transaction in the error log
- Improved the “save as…” filter controls in Data Studio
- Prevented a case where reference datasets could be added with a blank name
- Fixed an issue with schema refresh when a Salesforce synapse was active
- Jira pipelines were not syncing correctly when mapped to components
- Fixed a performance issue with syncing where references existed to deleted objects
- An issue where sending values to a custom picklist in Jira caused an error