# Automation & Billing Events Checkout automation, billing events, failed payment recovery, CRM workflows, webhooks, and dunning automation for Spiffy purchases. Purchases, renewals, failed payments, card updates, upsells, CRM actions, fulfillment, and webhooks can all trigger automatically from the checkout and billing events Spiffy already sees. [Get Started](/pricing/) [Learn More](#automation-overview) Try Spiffy risk-free for 30 days. Image: Spiffy checkout automations screen showing purchase and checkout flow complete automation actions Automation overview ## Connect what people buy to what should happen next. Spiffy automations cover the purchase moment and the billing lifecycle that follows. Use them for customer communication, access, CRM data, webhooks, and payment recovery without adding another disconnected workflow tool. [Read the automation guide](https://university.spiffy.co/automation/intro-to-automations/) ### Purchase events Run actions from Purchase, Checkout Flow Complete, product purchase, option purchase, and accepted upsells. ### Billing events Respond to Payment Failed, Card Expiring, Card Updated, Subscription Payment, and Payment Plan Payment events. ### Payment recovery Pair failed payment retries with reminders and card updater links from the customer portal. ### CRM workflows Apply tags, start sequences, update lists, and keep customer records aligned with the actual sale. ### Webhooks Send checkout and billing events into custom tools, Zapier, Make, or your internal systems. ### Account coverage Use account-level rules, product rules, option rules, subscription rules, and payment plan rules where each one makes sense. Post-purchase automations ## Purchase happens. Everything else follows. Set actions on the exact purchase event that matters: the checkout purchase, the selected option, the accepted upsell, or the completed checkout flow after every offer has been accepted or declined. Use the same automation model across the funnel. Spiffy product and option automations come from the same event/action setup used in the app. Choose the event, add the integration action, then keep an eye on activity through automation logs. - Purchase - Checkout Flow Complete - Post-Purchase Upsell - Option purchase - Automation Logs - Tag and segment buyers Send the right customer data to ActiveCampaign, Keap, HubSpot, or your CRM. - Start the right onboarding Trigger different welcome flows for buyers, VIP options, upgrades, or add-ons. - Pass clean data downstream Notify fulfillment, membership tools, reporting tools, or custom endpoints. Image: Spiffy automation diagram showing checkout options mapped to follow-up workflows Product options can branch into different automation actions after the same checkout purchase. Image: Spiffy upsell automation diagram showing accepted offer follow-up Accepted upsells and downsells can run their own fulfillment, tagging, and follow-up logic. Billing events ## More than 25 billing events, without a separate setup. Account automations and billing events are built around the same operational idea: when the payment state changes, the right follow-up can run immediately. Use broad account rules for standard recovery, or add specific rules for [subscriptions](/product/subscriptions/) and [payment plans](/product/payment-plans/) when those offers need different handling. [See Billing Automation](https://university.spiffy.co/automation/billing-automation/) ### Common billing triggers - Payment Failed Start retry, reminder, and dunning follow-up. - Card Expiring or Card Updated Ask customers to update details or sync the new payment method state. - Subscription Payment Update customer records, revenue reporting, or access after renewals. - Payment Plan Payment Follow up around installments, missed payments, upcoming payments, and completion. - Consent and lifecycle events Keep email preferences, disputes, cancellations, and other account events connected. Failed payment recovery ## Recover failed payments without manual chasing. Build dunning automation for subscriptions and payment plans with smart retries, customer reminders, and card updater links through the [Customer Portal](/product/customer-portal/). - Smart retries - Card updater links - Customer reminders - Recovered payment follow-up ### How recovery can play out - 1 Payment attempt fails The billing event fires as soon as the payment fails. - 2 Retry is scheduled Retry logic keeps the next attempt organized. - 3 Card updater link is sent Customers get a direct path to fix the payment method. - 4 Reminder follow-up runs Your email or CRM flow keeps the customer moving. - 5 Payment is recovered Billing status, access, and customer data stay in sync. Automation actions ### Add the action once, then let events run it. The app's automation UI is built around event groups and action rows, so the setup stays familiar across checkout and billing workflows. - Apply CRM tags Segment buyers by checkout, option, subscription, payment plan, or offer. - Start sequences Send welcome flows, recovery reminders, onboarding, or win-back messaging. - Grant access Connect the successful purchase to membership, fulfillment, or internal delivery steps. - Send webhooks Push purchase and billing data to custom systems that need to react quickly. - Use integrations Keep your marketing, CRM, analytics, and ops tools tied to the transaction. - Review automation logs See the event, related customer, order, subscription, payment plan, and actions that ran. Trigger levels ### Choose the trigger level that matches the job. You do not need every workflow to live in the same place. Use broad rules for broad billing logic, and specific rules where the buyer path matters. - Checkout purchases Run actions when an order completes through a specific checkout. - Product options Apply different logic for tiers, packages, payment choices, or add-ons. - Upsells and downsells Route accepted offers into the right fulfillment and follow-up workflows. - Subscriptions Respond to renewals, trials, plan changes, unpaid status, and cancellations. - Payment plans Follow up around installments, failed payments, upcoming payments, and completions. - Account billing Handle account-level failed payments, card updates, disputes, and consent events. ## Automation questions? Need help mapping your workflows? [Get in touch](mailto:support@spiffy.co?subject=Spiffy%20Automations%20question). How do Spiffy automations get set up? Automations are configured around purchase and billing events. Choose the event, connect the relevant integration or webhook action, then let Spiffy run it when the event happens. [Read the setup guide](https://university.spiffy.co/automation/intro-to-automations/). Which events can I send to my CRM or automation tool? Purchases, checkout-flow completion, upsells, failed payments, card updates, trials, subscription events, payment plan events, consent, and more can be used in automation workflows. Can automations be different by product, option, or checkout? Yes. You can use checkout-level, option-level, upsell-level, product-level, subscription, payment plan, and account-level triggers depending on how specific the workflow needs to be. Can Spiffy automatically retry failed payments? Yes. Spiffy supports failed-payment recovery with retry logic, customer reminders, and card updater links so recovery does not have to depend on manual follow-up. [See billing automation](https://university.spiffy.co/automation/billing-automation/). Can I use webhooks or Zapier-style workflows? Yes. Spiffy can send events into connected tools and custom webhook endpoints so your checkout and billing data can keep the rest of your stack updated. See the [Zapier guide](https://university.spiffy.co/integrations/zapier/) or [custom webhooks guide](https://university.spiffy.co/integrations/custom-webhooks/custom-webhooks-overview/). ### Automate your checkout workflows. Turn purchases, billing events, and failed payments into connected follow-up without adding more manual admin. [Get Started](/pricing/)