Setting Up and Managing Native and Notification Integrations

A native integration in m3ter is one that you can set up yourself directly in the Console. In the Integrations section you can define native integrations to control how Bills generated in m3ter are sent outbound to these 3rd-party systems:

  • Stripe

  • NetSuite

  • Paddle

  • Chargebee

  • QuickBooks

  • Xero

  • Salesforce

When you have performed the integration set up for how Bill data will be sent to and synchronized with your 3rd-party system as the Destination, the Native Integration Configuration will be immediately available for use and listed on the Integration Configurations page.

Warning! Test Beta Native Integrations in your Sandbox: m3ter Native Integrations for outbound billing flow into 3rd-party systems are in Beta release. We strongly recommend that you carry out testing in your m3ter Sandbox or QA environment to check your Native Integration implementation before releasing it to your Production environment. Please see section 7 of our Terms of Service for details on Beta release usage.

You can also create Notification Integration Configurations:

  • Create a Notification Rule for when a Notification will be triggered on the basis of a system Event occurring.

  • Link the Notification Rule to an integration Destination you've set up. Note that currently, only a webhook can be used as the Destination for a Notification.

  • When you link a Notification Rule to a Destination, this creates a Notification Integration Configuration, which is then listed on the Integration Configurations page.

Tip: Creating Notification Integration Configurations? See the Utilizing Events and Notifications section for more details.

This section explains how to create and work with Integration Configurations you can set up in the m3ter Console for native integrations with your 3rd-party systems or for Notifications to webhooks:

The following topics then cover how to set up and create Native Integration Configurations for outbound Bills into specific external systems:

You can set up multiple destinations for native integrations with a 3rd-party system:

You can create Destinations for your integrations to link to:

In the Credentials page you can create Credentials, which you can then use to authenticate integrations with your 3rd-party systems:

Five system Events are generated for errors that might occur with your integrations and you can review, troubleshoot, and resolve these:

When you integrate 3rd-party systems with the m3ter platform, 3rd-party entities and fields are mapped to m3ter entities and fields. External Mappings are created and act as mapping reference lookups for which objects and fields have been mapped across systems:

If you've set up an integration with a 3rd-party system, you can review details of the integration runs that have been performed for the integration:

Tip: Integrations API Calls? When you have set up a native integration, you can review and manage the integration using a full set of API Calls. See the Integrations section of our API Reference Docs.

Additional Support

Login to the Support portal for additional help and to send questions to our Support team.