Skip to main content
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 out to external systems:
  • Stripe
  • NetSuite
  • Paddle
  • Chargebee
  • QuickBooks
  • Xero
  • Salesforce
For some external systems, such as for a Salesforce integration, you can also choose to send operational data for entities in you m3ter Organization. When you have performed an integration set up for how data will be sent to and synchronized with an external system, the integration will be immediately available for use and listed on the Integrations page for that system in the m3ter Console. In the Integrations section, you can also create Outgoing Webhooks. These are used to create Notification Webhook Integrations:
  • Create a Notification rule to control when a Notification will be triggered on the basis of a system Event occurring.
  • Link the Notification rule to an Outgoing Webhook you’ve set up.
This section explains how to create and work with Native Integrations you can set up in the m3ter Console with your external systems and how to create and work with Notification Webhook Integrations. The first topic offers some introductory and general guidance on working with and managing both types of integration: The following topics then cover how to set up and create Native Integration configurations for outbound Bills into specific external systems: For Salesforce, you can also configure entity data sync integrations to send Accounts, Bills, Contracts, Prepayments/Commitments, or Balances data into your Salesforce system: You can create Native Integrations for sending out Bills to AWS Marketplace or Azure Marketplace. Once operational, m3ter also offers some very useful reconciliation features to support your Marketplace integrations: You can set up multiple destinations for Native Integrations: You can create Outgoing Webhooks for your Notification rules to link to: You can create Credentials to authenticate Native Integrations with your external 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 external systems with the m3ter platform, external system 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 an external 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 an integration, you can review and manage the integration using a full set of API Calls. See the Integrations section of our API Reference Docs.