Integration
DEFINITION
An integration is a connection that links a subscription or billing platform to an external system, such as a CRM, accounting tool, data warehouse, or support desk, so that data and actions can flow between them automatically.
RELATED TERMS
In a subscription or billing platform, an integration is a connection that links that platform to an external system, such as a CRM, accounting tool, data warehouse, or support desk, so that data or actions can flow between them without manual work.
An integration is sometimes called a connector. It lets an action in one system, like a subscription change, a support ticket, or an email send, happen automatically based on activity in another, and it keeps records in sync across both. Instead of exporting and re-uploading data by hand, or re-entering the same customer details across several tools, a business lets the integration move data and trigger actions on an ongoing basis. For a subscription business, integrations usually fall into a few practical categories: accounting and ERP systems, customer relationship management (CRM) tools, data warehouses, customer support platforms, and fraud or risk management tools.
Why it matters
A subscription business runs on data spread across more than one system: billing records in the subscription platform, customer records in a CRM, financial records in an accounting system, and support history in a helpdesk tool. Without integrations tying those systems together, teams reconcile records by hand, which is slow and error-prone. Integrations cut that manual work, keep customer and billing context consistent from team to team, and let one system trigger an action, like updating a subscription or sending a targeted message, based on what is happening elsewhere in the business. When a platform ships prebuilt connectors, a team can set up that connection by picking the connector, entering credentials, and turning it on, rather than building against an API from scratch.
How to use
Identify which external systems need to stay in sync with subscription and billing data, such as a CRM, accounting platform, or support desk.
Check whether the subscription platform offers a prebuilt integration or connector for that system.
Gather the credentials required to connect the two systems, such as API keys or client IDs and secrets.
Configure and activate the integration, then confirm data or events are flowing as expected between the systems.
Review integrations periodically, since access permissions, credentials, or the systems on either end can change over time.
Benefits and examples
Connecting systems through integrations cuts manual data entry and the errors that come with it. It also keeps teams working from the same information: a support agent, a finance team member, and a sales rep all see consistent, up-to-date customer and billing context instead of pulling from separate, disconnected records.
For example, a subscription business might link its billing platform to an accounting system so invoices and revenue flow straight into the general ledger, connect a CRM so sales and success teams see subscription status without leaving their own tool, or feed a data warehouse so finance and analytics teams can report across billing, usage, and marketing data in one place.
Recurly supports prebuilt integrations across the categories that matter most to a subscription business, including accounting and ERP systems such as Xero, NetSuite, and QuickBooks, CRM tools such as Salesforce, data warehousing through Snowflake, and support tools such as Zendesk.
Frequently asked questions
What is the difference between an integration and an API? An API is the technical interface a system exposes so other systems can connect to it. An integration is the actual connection built on that API, or a similar mechanism, to link two systems for an ongoing purpose, such as syncing billing data with an accounting system.
Do I need engineering resources to set up an integration? It depends. A prebuilt connector, like one offered inside a platform's settings, is usually built for a non-technical or lightly technical setup: credentials and configuration rather than custom code. A custom integration written directly against a platform's API generally does need development work.
What kinds of systems commonly integrate with a subscription billing platform? Common categories include accounting and ERP systems, CRM tools, data warehouses, customer support platforms, and fraud or risk management tools, along with payment gateways and processors.
What happens if an integration breaks or loses access? Depending on the integration, data may stop syncing, actions may stop triggering, or errors may appear until the connection is reauthorized or reconfigured, often because credentials expired or permissions changed on one side of the connection.
