Mark new Stripe customers in HubSpot
Each morning, everyone whose Stripe subscription started yesterday becomes a HubSpot customer with their plan on the contact.
Combine HubSpot + Stripe and move payment data into HubSpot, or CRM data into Stripe. Just ask Letaido's AI agent and watch it do the work.
Use this HubSpot Stripe integration for new customers, cancellations, failed payments, won deals and trials ending.
Each morning, everyone whose Stripe subscription started yesterday becomes a HubSpot customer with their plan on the contact.
When a Stripe subscription is canceled, the agent marks the customer's HubSpot company as churned with the reason and gives the owner a win-back task.
When a Stripe payment fails, the agent gives the customer's HubSpot contact owner a task with the amount, the retry date and the invoice link.
Every hour, won HubSpot deals become Stripe subscriptions billed by invoice at Stripe list prices, so deal discounts aren't carried over.
Every Monday, contact owners get HubSpot tasks for Stripe trials ending within 7 days, with the plan and whether a default payment method is set.
HubSpot's Stripe sync copies records, and Stripe payment processing takes payments in HubSpot. Leta runs jobs with your rules.
| Option | Stripe data on contacts | Creates things in Stripe | Works without you | Applies your own rules | Reacts to a Stripe event |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | Yes | |
| HubSpot's Stripe data sync | Yes | Partly | Yes | Partly | Partly |
| Stripe as HubSpot's payment processor | Partly | No | Yes | No | No |
| Zapier | Yes | Yes | Yes | Yes | Yes |
| Option | Which way data goes | How a run begins | Good at | Keep in mind |
|---|---|---|---|---|
| Letaido AI agent | Stripe into HubSpot as contacts, company fields and tasks, and HubSpot into Stripe as customers and subscriptions | A Stripe event such as a failed payment or a cancellation, a set time such as every hour or every Monday, or a request in chat | New customers on contacts, churn and its reason on companies, owner tasks for failed payments and ending trials, subscriptions for won deals | Not a record sync. Stripe events need a webhook endpoint in Stripe and its signing secret in Letaido. HubSpot changes start jobs only on a schedule |
| HubSpot's Stripe data sync | Customers and contacts both ways. Invoices, products, subscriptions and payment transactions into HubSpot only | Its own sync: records update within 10 minutes of a change | Keeping Stripe customers, invoices and subscriptions in HubSpot for lists, workflows and reports | It copies records and fields. Subscriptions and payments arrive as custom objects, and custom field mappings need Data Hub Starter or higher |
| Stripe as HubSpot's payment processor | Payments taken in HubSpot go through your Stripe account | A buyer paying a HubSpot quote, invoice, payment link or subscription | Taking one-time and recurring payments from HubSpot and reporting on them there | A 0.75% HubSpot platform fee per transaction. One Stripe account per HubSpot account. Invoices and subscriptions made in HubSpot aren't created in Stripe |
| Zapier | Either way: Stripe actions include Create Customer, Create Subscription and Create Invoice | A Stripe event such as New Customer, New Payment, Failed Payment or Canceled Subscription, or a HubSpot trigger, many of which poll | Templates such as HubSpot contacts from new Stripe payments, or HubSpot deals from new Stripe invoices | Each Zap is a set of steps you build and maintain, and each successful action step counts as a task |
A job can start when a Stripe subscription is canceled or a Stripe invoice payment fails, like “Canceled Stripe subscriptions flagged in HubSpot”.
Saved as an automation, like these jobs: every morning at 7am, every hour or every Monday at 8am.
Ask in chat; Leta picks from 130 actions.
Allow all read operations once per app; approve each kind of write once.
Find contact · List contacts · Create or update contact · Find custom object
Delete coupon · Create customer · API request · Create coupon
Yes. HubSpot's own Stripe data sync copies customers, invoices, products and subscriptions into HubSpot, and Stripe can process payments for HubSpot quotes and invoices. Leta, Letaido's AI agent, adds jobs those don't do, such as churn flags with the reason, owner tasks for failed payments and Stripe subscriptions for won deals.
For HubSpot, create a Service Key in HubSpot and paste it into Letaido. For Stripe, create a restricted API key in the Stripe Dashboard and paste it into Letaido. For jobs that start on a Stripe event, also add a webhook endpoint in Stripe and paste its signing secret.
Yes. A Stripe event, such as a failed invoice payment or a canceled subscription, starts the job when Stripe sends it. A change in HubSpot can't start a job here. The other jobs run on a schedule, such as every hour or every Monday at 8am, or when you ask.
Each morning, Leta can mark people whose Stripe subscription started yesterday as HubSpot customers and write their plan to a 'Stripe plan' contact property. When a subscription is canceled, it sets stripe_status to churned and stripe_churn_reason on the company. Create those properties in HubSpot first.
Yes. Every hour, Leta turns won deals into Stripe subscriptions billed by invoice, matching each line item's SKU to the lookup key of a recurring Stripe price. Stripe list prices apply, so deal discounts aren't carried over, and a deal with an unmatched SKU is skipped and you're told why.
Only if you want its record sync and reports. The jobs here call HubSpot and Stripe themselves, so they run whether the data sync is on or off.
Allow all read operations once per app; approve each kind of write once.
Connect HubSpot and Stripe, then ask for a job like "Mark new Stripe subscribers as HubSpot customers each morning". Leta gets it done on your schedule, or the moment you ask.
Get Letaido