--- title: "Third Party Integrations" description: "A non-technical ecosystem overview of Third Party Integrations in RevCent, focused on how connected third-party services extend RevCent, how native integrations differ from custom Function-based integrations, and how integrations relate to AI Assistants, AI Voice Agents, Tax, external providers, automation, and the RevCent relationship graph." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/ThirdPartyIntegration.md" relationships: - name: "AI Assistant" url: "https://revcent.com/documentation/markdown/ecosystem/feature/AIAssistant.md" - name: "AI Voice Agent" url: "https://revcent.com/documentation/markdown/ecosystem/feature/AIVoiceAgent.md" - name: "Tax" url: "https://revcent.com/documentation/markdown/ecosystem/item/Tax.md" technical_links: web_app: "https://kb.revcent.com/en/integrations/third-party/third-party-integration" api: section: "https://revcent.com/docs/api/v2#section-third_party_integrations" operations: - name: "Get Site Third Party Integrations" operation_id: "GetSiteThirdPartyIntegrations" operation: "https://revcent.com/docs/api/v2#operation-GetSiteThirdPartyIntegrations" schema: "https://revcent.com/documentation/files/api/operation/GetSiteThirdPartyIntegrations.json" - name: "Get A Site Third Party Integration" operation_id: "GetSiteThirdPartyIntegration" operation: "https://revcent.com/docs/api/v2#operation-GetSiteThirdPartyIntegration" schema: "https://revcent.com/documentation/files/api/operation/GetSiteThirdPartyIntegration.json" - name: "Get User Third Party Integrations" operation_id: "GetUserThirdPartyIntegrations" operation: "https://revcent.com/docs/api/v2#operation-GetUserThirdPartyIntegrations" schema: "https://revcent.com/documentation/files/api/operation/GetUserThirdPartyIntegrations.json" - name: "Create A User Third Party Integration" operation_id: "CreateUserThirdPartyIntegration" operation: "https://revcent.com/docs/api/v2#operation-CreateUserThirdPartyIntegration" schema: "https://revcent.com/documentation/files/api/operation/CreateUserThirdPartyIntegration.json" - name: "Get A User Third Party Integration" operation_id: "GetUserThirdPartyIntegration" operation: "https://revcent.com/docs/api/v2#operation-GetUserThirdPartyIntegration" schema: "https://revcent.com/documentation/files/api/operation/GetUserThirdPartyIntegration.json" - name: "Edit A User Third Party Integration" operation_id: "EditUserThirdPartyIntegration" operation: "https://revcent.com/docs/api/v2#operation-EditUserThirdPartyIntegration" schema: "https://revcent.com/documentation/files/api/operation/EditUserThirdPartyIntegration.json" - name: "Delete A User Third Party Integration" operation_id: "DeleteUserThirdPartyIntegration" operation: "https://revcent.com/docs/api/v2#operation-DeleteUserThirdPartyIntegration" schema: "https://revcent.com/documentation/files/api/operation/DeleteUserThirdPartyIntegration.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewThirdPartyIntegration.md" operations: - name: "Get Site Third Party Integrations" operation_id: "GetSiteThirdPartyIntegrations" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSiteThirdPartyIntegrations.md" available_via_ai: true - name: "Get A Site Third Party Integration" operation_id: "GetSiteThirdPartyIntegration" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSiteThirdPartyIntegration.md" available_via_ai: true - name: "Get User Third Party Integrations" operation_id: "GetUserThirdPartyIntegrations" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetUserThirdPartyIntegrations.md" available_via_ai: true - name: "Create A User Third Party Integration" operation_id: "CreateUserThirdPartyIntegration" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateUserThirdPartyIntegration.md" available_via_ai: true - name: "Get A User Third Party Integration" operation_id: "GetUserThirdPartyIntegration" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetUserThirdPartyIntegration.md" available_via_ai: true - name: "Edit A User Third Party Integration" operation_id: "EditUserThirdPartyIntegration" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditUserThirdPartyIntegration.md" available_via_ai: true - name: "Delete A User Third Party Integration" operation_id: "DeleteUserThirdPartyIntegration" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteUserThirdPartyIntegration.md" available_via_ai: true --- # Third Party Integrations Third Party Integrations are RevCent records that connect a merchant's RevCent account to outside services. They exist because ecommerce businesses rarely operate inside one system. A merchant may use RevCent for commerce operations, payments, subscriptions, trials, refunds, tax, AI, voice, shops, customer communication, and automation while still needing to connect to outside tools such as tax providers, email platforms, accounting systems, fulfillment tools, alternate payment providers, AI providers, voice providers, CRMs, helpdesks, webhooks, or other business systems. In simple terms, a Third Party Integration is the bridge between RevCent and an external service. It helps answer: “Which outside service is connected to RevCent, what is it used for, and which RevCent features rely on it?” ## Why Third Party Integrations Are a Feature Third Party Integrations are a feature because they give merchants a reusable way to connect RevCent to outside services and then use those connections across the RevCent ecosystem. RevCent may support a native integration provider at the platform level, but the merchant still needs their own connected version of that integration. That connected version is what other parts of RevCent use. For ecosystem graphing, this distinction is useful: - RevCent may know how to connect to a type of provider. - The merchant creates their own connected integration for that provider. - RevCent features then reference the merchant's connected integration. That connected integration becomes part of the merchant's account graph. ## Core Purpose The core purpose of Third Party Integrations is to let RevCent work with outside systems in a structured way. Third Party Integrations can help a business: - Connect RevCent to native outside providers. - Use outside tax services for tax calculation. - Connect AI-related providers for AI Assistant workflows. - Connect voice-related providers for AI Voice Agent workflows. - Connect alternate payment providers where supported. - Connect shipping or tracking providers where supported. - Send customer or order activity to external systems. - Keep credentials and provider-specific settings organized. - Give RevCent features a reusable external-service connection instead of hard-coding provider details in each workflow. A Third Party Integration is not usually the business event itself. It is the connection that lets RevCent features interact with an outside provider when needed. ## Where Third Party Integrations Fit in RevCent Third Party Integrations sit in the integration layer of RevCent. They connect external service providers to the rest of the ecosystem. A connected integration may be used by features such as Tax, AI Assistants, AI Voice Agents, shipping workflows, alternate payment flows, and other provider-aware parts of RevCent. A useful way to view the graph is: - RevCent feature needs outside service. - Third Party Integration provides the connected outside account or provider configuration. - The feature uses that connection during its normal business workflow. - The result becomes visible in the related RevCent items, such as Tax, Sales, Subscriptions, customer interactions, support workflows, or lifecycle automation. ## Native RevCent Integrations Some integrations are native to RevCent. A native integration means RevCent already understands the provider well enough to present a guided setup path. RevCent can know what type of service it is, what credentials are needed, what options may need to be selected, and which RevCent features can use it. Examples of native integration purposes may include: - Tax calculation. - AI provider support. - AI voice provider support. - Alternate payment provider support. - Shipping or tracking provider support. - External services such as email, accounting, or webhook-style systems where supported. Native integrations are useful because the connection is more structured. Instead of treating every provider as a custom project, RevCent can help the user connect the provider and make that provider available to the appropriate RevCent features. ## Native Integration Definition vs Connected User Integration There are two related concepts behind Third Party Integrations. A native integration definition is RevCent's supported provider template. It describes the outside provider and the kind of RevCent use case it supports. A connected user integration is the merchant's actual connected version of that provider. This is the record that belongs to the merchant's RevCent account. Plain-language model: - Native integration definition: “RevCent supports this kind of provider.” - Connected user integration: “This merchant connected their account for that provider.” This matters because features usually need the merchant's connected integration, not just the fact that RevCent supports the provider generally. For example, a tax provider available in RevCent is not enough by itself. The merchant must connect their own tax provider account before a Tax Profile can use that provider for tax calculation. ## Third Party Integration Types Third Party Integrations are usually grouped by what they are meant to do. Common categories include: - AI integrations for AI Assistant and AI-related workflows. - AI voice integrations for AI Voice Agent workflows. - Tax integrations for tax calculation. - Shipping integrations for shipment or tracking-related workflows. - Offline or alternate payment integrations for payment methods outside standard card or PayPal flows. The category matters because a feature expects the correct kind of connected provider. For example, a Tax workflow should use a tax-oriented integration. An AI Voice Agent workflow should use a voice-oriented integration. A shipping workflow should use a shipping-oriented integration. This keeps the ecosystem clean and prevents a connected provider from being used in the wrong part of RevCent. ## Relationship to Tax Tax is one of the clearest examples of how Third Party Integrations fit into the RevCent graph. RevCent can calculate or store tax in different ways depending on the commerce flow. In some cases, a Third Party Shop such as WooCommerce may calculate tax during the initial storefront checkout. In other cases, RevCent may need to calculate tax later for a Subscription Renewal, Trial expiration payment, custom store flow, or other RevCent-driven lifecycle payment. When RevCent needs an external tax provider, the business can connect a tax-focused Third Party Integration. That connected integration can then support tax calculation through RevCent's tax configuration. Graph relationship: - Third Party Integration provides the connected tax provider. - Tax configuration uses that integration when RevCent is responsible for tax calculation. - Tax items are created or stored as part of Sales, Subscription Renewals, Trial expiration payments, Shipping, payments, or refunds. - Tax remains connected to the commerce records that produced it. This makes Third Party Integrations important not only as setup records, but as part of the tax relationship graph. ## Relationship to AI Assistants AI Assistants can use Third Party Integrations when an AI workflow depends on an outside provider. A Third Party Integration may support AI model access, provider-specific AI capabilities, or another external system that an AI Assistant needs to interact with. AI Assistants can also work alongside integrations by monitoring RevCent events, reviewing connected records, triggering workflows, summarizing outcomes, and coordinating with Functions when custom outside-system behavior is needed. Example business patterns include: - AI Assistant uses a connected AI provider where applicable. - AI Assistant reviews Tax, Sale, Subscription, refund, or customer context that was affected by an integration. - AI Assistant triggers a Function that sends data to a non-native provider. - AI Assistant creates internal follow-up when an integration-driven workflow needs human review. The relationship is important because AI Assistants are often orchestration tools. Third Party Integrations provide structured outside-service connections, while AI Assistants can decide when and how those connections should be used within approved workflows. ## Relationship to AI Voice Agents AI Voice Agents can also rely on Third Party Integrations. A voice-related integration may provide the underlying provider connection needed for inbound or outbound voice workflows. Once connected, the AI Voice Agent can use RevCent customer, Sale, Subscription, Trial, refund, payment, or support context during voice interactions. Example voice-related use cases include: - Customer support calls about orders, subscriptions, trials, refunds, or tax. - Outbound recovery calls for failed payments or overdue lifecycle events. - Calls that use provider-specific voice infrastructure. - Calls that trigger or depend on connected external services. Third Party Integrations help connect the outside provider layer, while AI Voice Agents provide the customer-facing or operational voice experience. ## Relationship to Functions Functions are important because they extend integration possibilities beyond native RevCent integrations. A native Third Party Integration is best when RevCent already supports the provider directly. It gives the user a guided, structured way to connect that provider. Functions are the broader extension layer. They can help users integrate with virtually any third-party service that supports APIs, webhooks, HTTP callbacks, or scheduled data exchange. This means RevCent is not limited to only the providers listed as native integrations. A practical rule: - Use a native Third Party Integration when RevCent already supports the provider directly. - Use Functions when the provider is custom, niche, internal, or not natively supported by RevCent. Functions can help users: - Send Sale activity to an external CRM. - Send customer data to a marketing platform. - Receive a webhook from a fulfillment partner. - Create a custom endpoint for another system to call. - Run a scheduled sync with an external service. - Add custom data to Email Templates. - Add custom tools for AI Assistants. - Add custom logic before or during AI Voice Agent workflows. - Route data to Slack, Teams, helpdesks, warehouses, ERPs, or internal systems. - Add custom payment, tax, shipping, support, or customer lifecycle behavior. For ecosystem understanding, Functions are the universal integration path. Third Party Integrations represent structured native provider connections; Functions represent custom extension and automation when native coverage is not enough. ## Native Integrations vs Function-Based Integrations Native integrations and Function-based integrations both connect RevCent to outside systems, but they serve different roles. Native integrations are best when the outside provider is supported directly by RevCent and is meant to plug into a specific RevCent feature. Examples include tax providers for tax calculation, AI providers for AI workflows, voice providers for AI Voice Agents, and provider categories that RevCent understands natively. Function-based integrations are best when the business wants custom behavior or needs to connect to a service that is not available as a native integration. The difference is less about whether RevCent can connect and more about how standardized the connection is: - Native integration: guided connection for a known provider and known feature use case. - Function-based integration: flexible custom logic for a broader set of external systems and business-specific needs. Both are part of the RevCent ecosystem. ## Relationship to Third Party Shops Third Party Shops and Third Party Integrations are related, but they are not the same concept. A Third Party Shop represents an external storefront or shopping cart connection, such as WooCommerce or a custom store context. It is about where commerce originates. A Third Party Integration represents a connected external service used by RevCent features. It is about provider services such as tax, AI, voice, shipping, alternate payments, or other external tools. A WooCommerce shop may originate a Sale, while a Third Party Integration may calculate tax, support AI, support voice, or connect to another provider involved in the lifecycle. Keeping the distinction clear helps the relationship graph stay useful: - Shop = storefront or commerce origin. - Integration = external provider connection. - Function = custom extension path for external systems. ## Relationship to Sales and Commerce Events Third Party Integrations may be involved before, during, or after commerce activity. They can support activities around: - New Sales. - Subscription Renewals. - Trial expiration payments. - Shipping and delivery updates. - Tax calculation. - Refund support. - Customer communication. - AI review and automation. - Voice support and recovery calls. - External CRM or accounting updates through native integrations or Functions. Even when the Third Party Integration is not the Sale itself, it may influence the services used during the Sale lifecycle or the follow-up workflows after the Sale is created. ## Relationship to Credentials and Options Many outside services require credentials, provider-specific choices, or account-level options. In non-technical terms, credentials prove that the merchant has permission to connect the outside account. Options tell RevCent how the merchant wants to use that connection. For example: - A marketing provider may require the correct audience or list. - A tax provider may need the correct account configuration. - A shipping provider may need the correct tracking or carrier setup. - An AI or voice provider may need the correct service connection. This is why a Third Party Integration is more than a name. It stores the business connection and the provider-specific setup needed for RevCent features to use the external service correctly. ## Why Third Party Integrations Matter Third Party Integrations matter because they let RevCent become the center of a broader ecommerce operating system. They help merchants: - Avoid disconnected manual workflows. - Keep provider connections reusable across RevCent features. - Use tax providers, AI providers, voice providers, shipping providers, and alternate payment providers in the right places. - Route important commerce activity to outside systems. - Connect RevCent lifecycle events to business tools outside RevCent. - Expand RevCent beyond native capabilities with Functions. - Preserve a clearer relationship graph between internal commerce records and external systems. Without integrations, outside systems often become isolated silos. With integrations, RevCent can keep the external-service relationship connected to the rest of the commerce lifecycle. ## Common Third Party Integration Patterns ### Tax Provider Integration A merchant connects a tax provider so RevCent can calculate tax when RevCent is responsible for tax calculation. This is especially useful for Subscription Renewals, Trial expiration payments, and custom flows where tax is not supplied by an external storefront. ### AI Provider Integration A merchant connects an AI-related provider for AI Assistant or AI-driven workflows. This connection can support automation, review, summarization, customer support workflows, and lifecycle decisions where AI is part of the process. ### AI Voice Provider Integration A merchant connects a voice-related provider so AI Voice Agents can support inbound or outbound calling workflows. This can help with support, recovery, retention, and customer communication. ### Alternate Payment Integration A merchant connects or maps an alternate payment provider so RevCent can represent payments that do not behave like standard credit card or PayPal payments. This may include payment methods such as buy-now-pay-later providers or other supported alternate payment services. ### Shipping or Tracking Integration A merchant connects a shipping or tracking provider so shipment-related activity can be enriched or updated by an outside service. This can help connect fulfillment and delivery status to RevCent's Shipping records and customer lifecycle. ### Webhook or External System Integration A business wants RevCent to send or receive information from another platform. If there is a native provider, the business can use a Third Party Integration. If there is no native provider, the business can use Functions to send data out, receive data in, or build a custom bridge. ## Functions as a Benefit Multiplier Functions make Third Party Integrations more powerful because they fill the gap between native provider support and real-world business needs. A merchant may start with a native tax, AI, voice, payment, or shipping integration, then use Functions to add custom behavior around it. For example: - A tax-related event can trigger a Function to notify an internal team. - A Sale can trigger a Function that sends data to a CRM. - A failed payment can trigger a Function that updates a helpdesk ticket. - A shipping update can trigger a Function that notifies a warehouse or customer service team. - An AI Assistant can call a Function to check an outside system before taking action. - An AI Voice Agent can use a Function before a call to decide whether the call should proceed. This combination lets native integrations handle standard provider connections, while Functions handle business-specific logic. ## Common Mistakes to Avoid A common mistake is assuming that RevCent can only connect to providers listed as native integrations. Native integrations are the structured path, but Functions can often connect RevCent to any third-party service with an API, webhook, or compatible endpoint. Another mistake is confusing Third Party Shops with Third Party Integrations. Shops are storefront or commerce-origin connections. Integrations are external provider connections used by RevCent features. Another mistake is using the wrong kind of integration for the wrong feature. A tax workflow should use a tax-oriented integration. A voice workflow should use a voice-oriented integration. An AI workflow should use an AI-oriented integration. Another mistake is treating integrations as one-time setup records and then forgetting which RevCent features depend on them. A disabled, incomplete, or misconfigured integration can affect the downstream workflows that rely on it. Another mistake is using a custom Function when a native integration already exists and would provide a more structured setup path. ## Ecosystem Relationship Summary Third Party Integration → AI Assistant: AI Assistants may use AI-related integrations and may also use Functions to interact with non-native third-party systems. Third Party Integration → AI Voice Agent: AI Voice Agents may use voice-related integrations and may also work with Functions for filtering, enrichment, and custom workflow behavior. Third Party Integration → Tax: Tax workflows can use a tax-focused connected integration when RevCent needs an external tax provider for tax calculation. Third Party Integration → Function: Functions extend RevCent beyond native integrations and can connect to nearly any third-party service with an API, webhook, or endpoint. Third Party Integration → Third Party Shop: Shops are storefront origins, while integrations are service-provider connections. Both can participate in the same Sale, Subscription, Trial, Tax, and customer lifecycle graph. Third Party Integration → Sale: Integrations may support services used during or after the Sale lifecycle, such as tax, communication, external data sync, shipping, AI, voice, or alternate payment context. Third Party Integration → Subscription Renewal: Integrations may support tax, payment, communication, recovery, AI, voice, or custom external workflows around recurring billing. Third Party Integration → Trial: Integrations may support trial expiration tax, failed-payment recovery, customer communication, AI review, voice follow-up, or custom external workflows. ## Summary Third Party Integrations are the connected external-service records that let RevCent work with outside providers. They help RevCent connect to native providers for tax, AI, voice, alternate payments, shipping, and other supported service categories. They also give other RevCent features a reusable provider connection instead of requiring each workflow to manage external-service setup separately. The most important ecosystem idea is that native Third Party Integrations and Functions work together. Native integrations provide structured connections to providers RevCent supports directly. Functions provide the flexible extension path for custom providers, internal systems, niche services, webhooks, APIs, scheduled jobs, AI tools, and business-specific workflows. Together, Third Party Integrations and Functions help RevCent act as the center of a connected ecommerce ecosystem rather than a standalone commerce tool. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.