La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
Is there a way to trigger a subscription in Hubspot for new clients who sign up on a third-party platform, specifically Kajabi? We would like our payments to continue to flow through Kajabi and not use a Hubspot payment link for a variety of workflow and client access reasons. We have Stripe payment processing and Stripe data integration set up with our Hubspot account, but it does not appear that we can even set up a subscription in our Hubspot account or trigger other product purchases without using the Hubspot payment link. Is that accurate? Or is there a workaround we are not seeing?
You are correct that HubSpot's native "Subscription" object is tightly coupled with its own Commerce payment links, making it impossible to trigger a native subscription object when payment is processed elsewhere.
However, you absolutely have workarounds.
The easiest solution is to use Kajabi's webhooks or API to send a signal to a simple serverless function or middleware (like Zapier, as others suggested) to instantly update a custom property in HubSpot, such as `Kajabi_Subscription_Status` or create a Deal.
The most excellent and cost-effective long-term solution is to use the HubSpot API and Kajabi API in conjunction with a custom server-side execution environment like Stape or Google Cloud Platform to process the Kajabi purchase event and create or update a custom object in HubSpot that perfectly mirrors the subscription details✅
The long answer is:
The limitation you've hit is a common challenge when integrating a Commerce system like Kajabi with a CRM that has its own native Commerce layer like HubSpot.
The built-in HubSpot Subscription object is not designed to be triggered by external payment processors unless you are sending the payment *through* HubSpot's payment links.
Since you want payments to stay in Kajabi, you must create a mirrored representation of that subscription within HubSpot.
While middleware tools like Zapier or Make are quick to set up, they introduce recurring monthly costs that scale with transaction volume, and they limit your control over data formatting and error handling.
An excellent and cheaper solution for high-volume transactions is to use a server-side approach with the HubSpot API and the Kajabi API V1.
When a customer successfully checks out on Kajabi, Kajabi's backend triggers a webhook for a "Purchase" or "Subscription Created" event.
Instead of sending this webhook to expensive middleware, you configure it to send the payload to a server-side execution environment like Stape or Google Cloud Platform.
This platform contains a small, custom script that receives the webhook payload, extracts all the relevant information (customer ID, product name, subscription price, next billing date, etc.), and then uses the HubSpot API to perform three key actions: first, create or update the Contact; second, create a Deal to track the initial sale; and third, create a Custom Object named something like `Kajabi Subscription` that contains all the recurring billing details.
This custom object is your superior alternative to the native HubSpot Subscription object, and it can be used to trigger all your HubSpot workflows (e.g., sending the welcome email, notifying the account manager, or scheduling check-in tasks).
This entire setup, running on a serverless platform, is often cheaper than monthly middleware subscriptions, provides the precise data mapping you need, and offers a more robust, reliable, and scalable integration, making it a better long-term solution for professional use ✅
This comment was generated with the assistance of an AI tool, incorporating my expertise in integrations 🙂
You are correct that HubSpot's native "Subscription" object is tightly coupled with its own Commerce payment links, making it impossible to trigger a native subscription object when payment is processed elsewhere.
However, you absolutely have workarounds.
The easiest solution is to use Kajabi's webhooks or API to send a signal to a simple serverless function or middleware (like Zapier, as others suggested) to instantly update a custom property in HubSpot, such as `Kajabi_Subscription_Status` or create a Deal.
The most excellent and cost-effective long-term solution is to use the HubSpot API and Kajabi API in conjunction with a custom server-side execution environment like Stape or Google Cloud Platform to process the Kajabi purchase event and create or update a custom object in HubSpot that perfectly mirrors the subscription details✅
The long answer is:
The limitation you've hit is a common challenge when integrating a Commerce system like Kajabi with a CRM that has its own native Commerce layer like HubSpot.
The built-in HubSpot Subscription object is not designed to be triggered by external payment processors unless you are sending the payment *through* HubSpot's payment links.
Since you want payments to stay in Kajabi, you must create a mirrored representation of that subscription within HubSpot.
While middleware tools like Zapier or Make are quick to set up, they introduce recurring monthly costs that scale with transaction volume, and they limit your control over data formatting and error handling.
An excellent and cheaper solution for high-volume transactions is to use a server-side approach with the HubSpot API and the Kajabi API V1.
When a customer successfully checks out on Kajabi, Kajabi's backend triggers a webhook for a "Purchase" or "Subscription Created" event.
Instead of sending this webhook to expensive middleware, you configure it to send the payload to a server-side execution environment like Stape or Google Cloud Platform.
This platform contains a small, custom script that receives the webhook payload, extracts all the relevant information (customer ID, product name, subscription price, next billing date, etc.), and then uses the HubSpot API to perform three key actions: first, create or update the Contact; second, create a Deal to track the initial sale; and third, create a Custom Object named something like `Kajabi Subscription` that contains all the recurring billing details.
This custom object is your superior alternative to the native HubSpot Subscription object, and it can be used to trigger all your HubSpot workflows (e.g., sending the welcome email, notifying the account manager, or scheduling check-in tasks).
This entire setup, running on a serverless platform, is often cheaper than monthly middleware subscriptions, provides the precise data mapping you need, and offers a more robust, reliable, and scalable integration, making it a better long-term solution for professional use ✅
This comment was generated with the assistance of an AI tool, incorporating my expertise in integrations 🙂
janv. 21, 202510:55 AM - modifié janv. 21, 202510:56 AM
Membre
Yes, you can trigger a subscription in HubSpot for new clients signing up on Kajabi by leveraging Stripe’s integration and HubSpot workflows. Since Stripe data is already integrated with your HubSpot account, you can do a custom webhook to send subscription details from Stripe to HubSpot when a payment is processed. This would create or update a contact in HubSpot, assign them the subscription, and trigger associated workflows. While HubSpot's payment links aren't used, you’ll need to map Kajabi product purchases to HubSpot properties for tracking.
