1import{j as l}from"./app-ClSEMX7D.js";function b(){return[{href:route("auth.register"),label:__("Start Free Trial"),tone:"primary"},{href:"/demo",label:__("Book Demo"),tone:"secondary"},{href:"/integrations",label:__("View All Integrations"),tone:"ghost"}]}function c({checklistOwner:e,milestone:o,name:i}){return{eyebrow:__("Launch checklist"),title:__("What needs to be true before you switch this on"),description:__("The fastest launches happen when the milestone is clear, the owner is known, and the data already lives where your team works."),items:[{iconName:"database",title:__("Clean records in the source system"),description:__(`Make sure ${i} already contains the customer or conversion data you want to use for referral operations.`)},{iconName:"link",title:__("A simple enrolment path"),description:__("Decide whether you want to generate links from existing records, sign people up through a form, or support both motions.")},{iconName:"reward",title:__(`One qualifying milestone: ${o}`),description:__("Pick a milestone the business already trusts so rewards are tied to real commercial progress instead of guesswork.")},{iconName:"automation",title:__("Automation ownership"),description:__(`Assign one ${e} to own mappings, qualification rules, and what should happen after a referral converts.`)},{iconName:"shield",title:__("Review and exception handling"),description:__("Decide which scenarios can run automatically and which ones should pause for review before a reward is issued.")},{iconName:"analytics",title:__("A reporting loop"),description:__("Track enrolments, referred leads, qualification rate, and issued rewards so the team can improve the workflow instead of babysitting it.")}]}}function d({capabilities:e,checklistOwner:o,faq:i,finalCta:n,fit:h,hero:m,metaDescription:p,metaTitle:u,milestone:w,name:f,variant:s="integration_detail",whyItMatters:g,workflow:_}){return{variant:s,metaTitle:u,metaDescription:p,hero:{buttons:b(),...m},whyItMatters:{...g,eyebrow:__("Why this matters"),pill:s==="integration_api"?__("Custom workflow control"):__("Operational leverage")},capabilities:{...e,eyebrow:s==="integration_api"?__("What you can orchestrate"):__("What this unlocks"),pill:s==="integration_api"?__("Developer-ready"):__("Built for live programs")},workflow:{..._,eyebrow:s==="integration_api"?__("Event flow"):__("How the workflow runs")},fit:{...h,eyebrow:s==="integration_api"?__("Best fit"):__("Who this fits best")},checklist:c({checklistOwner:o,milestone:w,name:f}),finalCta:{...n,eyebrow:__("Next step")},faq:{...i,eyebrow:__("FAQ")}}}function t(e,o){return{question:__(e),answer:__(o)}}function y(e,o,i,n){return{title:__("Questions teams ask before they wire this into a live program"),description:__("The pattern only works when qualification, routing, and reward rules are clear. These are the questions most teams need answered before rollout."),items:[t(`What does the ${e} integration actually automate?`,`${e} helps you ${o}. The point is to move referral operations into the same workflow the team already trusts instead of creating a second admin process.`),t(`Do we have to change the way we already use ${e}?`,i),t(`What should count as a qualified referral in ${e}?`,`Use one milestone the business already believes in, such as ${n}. When the qualifying event is obvious, rewards become easier to defend and easier to automate.`),t("Who should own the setup?",`Give ownership to the person closest to the ${e} workflow. They should understand the data, the milestone, and what the team wants to happen after a referral is qualified.`)]}}function a(e){return d({name:e.name,metaTitle:`${e.name} Referral Program Integration | Referral Factory`,metaDescription:e.metaDescription,milestone:e.milestone,checklistOwner:e.checklistOwner,hero:{eyebrow:__("Integration"),titleLead:__("Connect"),titleHighlight:__(e.name),titleTrail:__("to the referral workflow you already run."),description:__(e.heroDescription),timingNote:__(e.timingNote),sideCards:[e.sourceCard,{value:__("Milestone"),label:__("Qualification rule"),description:__(`Tie referral qualification to ${e.milestone} so rewards only move when the commercial milestone is real.`),tone:"yellow"}],visual:{accentLabel:__("Live workflow"),iconId:e.iconId,image:e.heroImage,alt:e.heroImageAlt}},whyItMatters:{title:__(`Why ${e.name} is a practical referral operations layer`),description:__(e.whyDescription),items:e.whyItems,bullets:[__("The strongest integrations remove handoffs between customer data, qualification logic, and reward operations."),__("A clean milestone is more useful than a flashy automation because it protects both ops and unit economics."),__("Teams get more value when the referral workflow runs where they already track the customer relationship.")]},capabilities:{title:__(`What ${e.name} unlocks once Referral Factory is connected`),description:__("The useful pattern is simple: enrol the right people, route the right referrals, and qualify the right outcomes without spreadsheet cleanup."),items:e.capabilities},workflow:{title:__(`How the workflow runs when ${e.name} is the source of truth`),description:__(e.workflowDescription),steps:e.workflowSteps},fit:{title:__(`Best fit for teams already operating in ${e.name}`),description:__(e.fitDescription),items:e.fitItems},finalCta:{title:__(`Put ${e.name} to work in the referral channel`),description:__(e.finalDescription),image:e.heroImage,imageAlt:e.heroImageAlt,features:[{title:__("Use existing data"),description:__(`Keep customer, lead, or payment context inside ${e.name} instead of rebuilding the workflow somewhere else.`)},{title:__("Qualify on real outcomes"),description:__(`Base rewards on ${e.milestone} so the business can trust the trigger.`)},{title:__("Reduce admin drag"),description:__("Give the team a cleaner referral workflow without creating one more system to monitor manually.")}]},faq:y(e.name,e.automationSummary,e.processSummary,e.milestone)})}const r=[{key:"hubspot",name:"HubSpot",iconId:"hubspot",metaDescription:"Use HubSpot and Referral Factory together to enrol customers, route referred leads, and qualify referrals from pipeline milestones without manual cleanup.",heroDescription:"If your customer data, lifecycle logic, and pipeline milestones already live in HubSpot, that is where your referral operations should connect. The goal is not another dashboard to babysit. The goal is a referral workflow your marketing and revops teams can actually run.",timingNote:"Best when the team already trusts HubSpot lifecycle stages, deal stages, or custom properties.",heroImage:"/assets/images/webp/web/integrations/hubspot-2.webp",heroImageAlt:"HubSpot referral workflow",sourceCard:{value:__("CRM"),label:__("Source of truth"),description:__("Use the HubSpot records your team already works in to keep referral enrolment and lead qualification tied to the same commercial data."),tone:"dark"},whyDescription:"HubSpot is a strong referral operations layer when your team already uses it to manage customer lifecycle, handoffs, and revenue stages. It keeps attribution and action in the same place.",whyItems:[{title:__("Referrals land where the team already works"),description:__("New referred leads can move into the same pipelines, ownership rules, and follow-up motions the team already runs every day."),image:"/assets/images/webp/web/integrations/hubspot-1.webp"},{title:__("Qualification can follow real pipeline progress"),description:__("Instead of guessing which referrals converted, you can qualify from lifecycle stages, deal stages, and custom property changes the business already respects."),image:"/assets/images/webp/web/integrations/hubspot-2.webp"},{title:__("RevOps does not have to rebuild the workflow"),description:__("Referral operations become another clean motion inside HubSpot rather than another spreadsheet-driven process no one wants to own."),image:"/assets/images/webp/web/integrations/hubspot-video.webp"}],capabilities:[{title:__("Generate referral links from HubSpot contacts"),description:__("Enrol the customers you already manage in HubSpot so they receive links and tracking without a manual export-import routine."),image:"/assets/images/webp/web/integrations/hubspot-1.webp"},{title:__("Route referred leads into your existing funnel"),description:__("Push new referrals into the same lifecycle and ownership model your revenue team already understands."),image:"/assets/images/webp/web/integrations/hubspot-2.webp"},{title:__("Qualify on pipeline milestones"),description:__("Trigger qualification when the referral reaches the lifecycle stage, deal stage, or custom property threshold that matters commercially."),image:"/assets/images/webp/web/integrations/hubspot-video.webp"}],workflowDescription:"The cleanest setup uses HubSpot for the commercial signal and Referral Factory for the referral mechanics. That separation keeps each system doing the job it is already good at.",workflowSteps:[{title:__("Sync the right contacts into the program"),description:__("Start with the segments already most likely to refer so the program is relevant from day one."),image:"/assets/images/webp/web/integrations/hubspot-1.webp"},{title:__("Capture new referrals into HubSpot"),description:__("Send referred people into your live follow-up workflow rather than
1into an isolated referral inbox."),image:"/assets/images/webp/web/integrations/hubspot-2.webp"},{title:__("Watch for a trusted lifecycle or deal signal"),description:__("Use HubSpot status changes to decide when a referral becomes commercially real."),image:"/assets/images/webp/web/integrations/hubspot-video.webp"},{title:__("Issue the reward without a manual audit trail"),description:__("Once the qualification rule is met, your team can trigger reward operations with far less admin."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"This is strongest for teams that already treat HubSpot as the operating layer for customer lifecycle and revenue movement.",fitItems:[{title:__("Marketing teams running lifecycle-driven campaigns"),description:__("Good fit when referral enrolment should happen from customer segments, usage milestones, or post-sale moments already stored in HubSpot.")},{title:__("RevOps teams that care about clean qualification"),description:__("Good fit when the business wants one clear source of truth for when a referred lead actually becomes qualified.")},{title:__("Sales teams managing handoffs in HubSpot"),description:__("Useful when referred leads should move through the same ownership and pipeline process as any other revenue opportunity.")}],milestone:"the correct lifecycle stage, deal stage, or custom property change",checklistOwner:"revops or marketing ops owner",finalDescription:"If HubSpot already drives how your team qualifies demand, it can also drive how referral demand gets enrolled, routed, and rewarded without extra operational drag.",automationSummary:"enrol customers from HubSpot, send referred people into your live funnel, and qualify them from pipeline movement that already matters to the business",processSummary:"No. The better setup keeps your existing HubSpot workflow intact and uses Referral Factory to add referral-specific tracking and reward logic around it."},{key:"stripe",name:"Stripe",iconId:"stripe",metaDescription:"Use Stripe and Referral Factory together to qualify referrals from payment events, support Stripe promo code redemption when needed, issue rewards faster, and run a cleaner revenue-linked referral workflow.",heroDescription:"Stripe is powerful when revenue events are the signal that matters most. If your team cares about charges, subscriptions, invoices, customer payment state, or Stripe promo code redemption, Stripe gives you a clean way to decide when a referral has actually converted.",timingNote:"Best when payment success, subscription state, or invoice completion is the milestone that matters.",heroImage:"/assets/images/webp/web/integrations/stripe-2.webp",heroImageAlt:"Stripe referral automation",sourceCard:{value:__("Payments"),label:__("Commercial signal"),description:__("When Stripe already tells you who paid, renewed, subscribed, or redeemed a Stripe promo code, it becomes a strong place to decide when a referral is real."),tone:"dark"},whyDescription:"A Stripe-led referral workflow is useful because it qualifies the thing finance and growth teams actually care about: paid conversion.",whyItems:[{title:__("Referral qualification can follow real revenue"),description:__("You can stop guessing whether a referred lead converted and instead qualify from payment events that already exist in Stripe."),image:"/assets/images/webp/web/integrations/stripe-1.webp"},{title:__("Stripe promo codes can support code-based referrals"),description:__("If your checkout uses Stripe promo codes, Referral Factory can generate referrer-specific codes and connect redemption back to the referral workflow."),image:"/assets/images/webp/web/integrations/stripe-2.webp"},{title:__("Subscription businesses get a natural milestone"),description:__("Paid signup, first invoice, or successful renewal can become the qualification event instead of a manual follow-up task."),image:"/assets/images/webp/web/integrations/stripe-video.webp"}],capabilities:[{title:__("Enrol paying customers into your referral program"),description:__("Generate referral links for the customers who already bought so the referral ask happens from a real customer base instead of a broad list."),image:"/assets/images/webp/web/integrations/stripe-1.webp"},{title:__("Generate Stripe promo codes when checkout needs a code"),description:__("Referral codes are not only for Stripe users, but Str
1ipe is the automated path when you want unique promotion codes to be redeemed directly in Stripe checkout."),image:"/assets/images/webp/web/integrations/stripe-2.webp"},{title:__("Qualify from payment behaviour"),description:__("Use Stripe events such as paid checkout, successful invoice, or active subscription to decide when the referral qualifies."),image:"/assets/images/webp/web/integrations/stripe-video.webp"}],workflowDescription:"The simplest Stripe setup uses payment activity as the qualification layer and keeps referral tracking separate from billing logic, but connected to it. Stripe promo codes are optional for businesses that want the code redemption itself to happen in Stripe.",workflowSteps:[{title:__("Enrol the right customer cohort"),description:__("Use customers who already completed the product purchase or subscription start you care about."),image:"/assets/images/webp/web/integrations/stripe-1.webp"},{title:__("Capture new referred signups"),description:__("Let Referral Factory track who referred whom while Stripe continues to handle the billing event. If the program uses Stripe promo codes, the code can also identify the referrer."),image:"/assets/images/webp/web/integrations/stripe-2.webp"},{title:__("Listen for the commercial milestone"),description:__("Use the payment, invoice, or subscription event that marks the referral as commercially real."),image:"/assets/images/webp/web/integrations/stripe-video.webp"},{title:__("Trigger reward logic after payment is confirmed"),description:__("That keeps the program tied to revenue instead of premature lead activity, whether the referral started from a link or a code."),image:"/assets/images/webp/web/rewards/stripe.webp"}],fitDescription:"This is strongest when the business wants referral qualification to stay tied directly to billing or subscription data.",fitItems:[{title:__("SaaS and subscription businesses"),description:__("Useful when activation and payment already live in Stripe and you want referral rewards tied to the paid milestone.")},{title:__("Ecommerce brands using Stripe checkout"),description:__("Useful when referred buyers should qualify only after the actual order or invoice clears.")},{title:__("Growth teams prioritising clean revenue attribution"),description:__("Good fit when finance and marketing both want clarity on when a referred customer became real revenue.")}],milestone:"a successful payment, invoice, or active subscription event",checklistOwner:"growth or revenue operations owner",finalDescription:"When Stripe already holds the commercial event, you can build a referral workflow around paid conversion instead of chasing down whether a lead really bought.",automationSummary:"enrol paying customers, track referred signups, support Stripe promo code redemption when needed, and qualify referrals against the payment events that already matter to the business",processSummary:"No. Stripe stays the billing layer. Referral Factory adds referral enrolment, tracking, optional Stripe promo code generation, and reward logic around the payment milestones you already use."},{key:"salesforce",name:"Salesforce",iconId:"salesforce",metaDescription:"Use Salesforce and Referral Factory together to route referred leads into the CRM, qualify them from pipeline movement, and reduce referral admin.",heroDescription:"If the sales team already runs pipeline, stage movement, and account ownership in Salesforce, that is where referral qualification should anchor. The integration works best when referral activity becomes part of the same operating model the team already trusts.",timingNote:"Best when qualification should follow opportunity stages, lead status, or account-level workflow.",heroImage:"/assets/images/webp/web/integrations/salesforce-2.webp",heroImageAlt:"Salesforce referral workflow",sourceCard:{value:__("CRM"),label:__("Revenue workflow"),description:__("Salesforce already carries ownership, stage progression, and commercial status for many teams. That makes it a strong qualification layer."),tone:"dark"},whyDescription:"Salesforce is valuable here because it lets referral qualification follow the same enterprise sales process already used for normal pipeline management.",whyItems:[{title:__("Referred leads stay inside the sales workflow"),description:__("The team can handle referred demand without inventing a separate operating motion outside the CRM."),image:"/assets/images/webp/web/integrations/salesforce-1.webp"},{title:__("Qualification maps to stages leadership already trusts"),description:__("Opportunity and status milestones can become the trigger instead of manual status chasing."),image:"/assets/images/webp/web/integrations/salesforce-2.webp"},{title:__("Enterprise teams get cleaner governance"),description:__("Referral logic becomes easier to defend internally when it runs against existing CRM states rather than
1informal spreadsheets."),image:"/assets/images/webp/web/integrations/salesforce-video.webp"}],capabilities:[{title:__("Generate referral links from CRM records"),description:__("Start from the contacts or customers you already track rather than building a separate enrolment workflow from scratch."),image:"/assets/images/webp/web/integrations/salesforce-1.webp"},{title:__("Route referred people into Salesforce"),description:__("Let the team pick up referred demand inside the same routing and follow-up process it already uses."),image:"/assets/images/webp/web/integrations/salesforce-2.webp"},{title:__("Qualify from stage changes and custom data"),description:__("Tie referral outcomes to the Salesforce milestones the revenue organisation already uses for reporting."),image:"/assets/images/webp/web/integrations/salesforce-video.webp"}],workflowDescription:"This pattern works best when Salesforce remains the source of truth for whether a referral turned into real pipeline or revenue.",workflowSteps:[{title:__("Enrol existing customers or advocates"),description:__("Use your CRM records as the start point for who can refer and when."),image:"/assets/images/webp/web/integrations/salesforce-1.webp"},{title:__("Create referred leads inside Salesforce"),description:__("Keep the handoff to sales inside the same system that already manages ownership and follow-up."),image:"/assets/images/webp/web/integrations/salesforce-2.webp"},{title:__("Qualify from a stage the business already tracks"),description:__("Use opportunity or status movement to mark when the referral became commercially meaningful."),image:"/assets/images/webp/web/integrations/salesforce-video.webp"},{title:__("Reward from a trusted CRM signal"),description:__("This removes most of the manual reconciliation between the sales team and whoever owns rewards."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for teams where Salesforce is already the trusted home for customer, lead, and pipeline operations.",fitItems:[{title:__("B2B sales teams with longer sales cycles"),description:__("Good fit when qualification needs to wait for a real CRM milestone instead of a top-of-funnel action.")},{title:__("Revenue operations teams"),description:__("Good fit when governance, reporting, and ownership all need to align with the CRM.")},{title:__("Enterprise teams avoiding shadow workflows"),description:__("Useful when referral demand must fit the same process discipline as any other lead source.")}],milestone:"the agreed opportunity stage, lead status, or account-level milestone",checklistOwner:"sales or revenue operations owner",finalDescription:"If Salesforce already decides when revenue is real, it should also decide when a referral has earned progression and reward logic.",automationSummary:"enrol advocates from Salesforce, route new referred leads into the CRM, and qualify them from the same pipeline movement the sales team already uses",processSummary:"No. The better approach is to preserve the current Salesforce process and let Referral Factory add referral attribution and reward logic around it."},{key:"intercom",name:"Intercom",iconId:"intercom",metaDescription:"Use Intercom and Referral Factory together to launch referral prompts from customer moments, route referred leads cleanly, and qualify from live customer data.",heroDescription:"Intercom is useful when referral growth should stay close to the customer lifecycle. If your team already uses Intercom to manage onboarding, engagement, support, and account signals, it can become the place where referral timing and qualification feel much more natural.",timingNote:"Best when referral prompts and qualification should follow customer engagement or lifecycle signals.",heroImage:"/assets/images/webp/web/integrations/intercom-2.webp",heroImageAlt:"Intercom referral workflow",sourceCard:{value:__("Lifecycle"),label:__("Customer moment"),description:__("Intercom works well when the referral ask should happen close to onboarding, support wins, and product engagement."),tone:"dark"},whyDescription:"Intercom is a strong referral operations layer when the team wants referral timing to match live customer moments instead of running on a generic schedule.",whyItems:[{title:__("Referral asks can follow real engagement"),description:__("Ask too early and the customer has no confidence. Ask too late and the moment is gone. Intercom helps you time the prompt better."),image:"/assets/images/webp/web/integrations/intercom-1.webp"},{title:__("Customer-facing teams can stay in one workflow"),description:__("Support, lifecycle, and onboarding teams do not need a second system just to understand what happened with a referral."),image:"/assets/images/webp/web/integrations/intercom-2.webp"},{title:__("Qualification can follow customer signals"),description:__("Use lifecycle state, conversation outcomes, or custom data the team already trusts when deciding what counts as real progress."),image:"/assets/images/webp/web/integrations/intercom-video.webp"}],capabilities:[{title:__("Enrol customers from the lifecycle you already run"),description:__("Move the right customers into referral prompts from the same customer operating layer you use for messaging and support."),image:"/assets/images/webp/web/integrations/intercom-1.webp"},{title:__("Send referred people into an existing follow-up path"),description:__("Make referrals visible to the team without creating another inbox or another handoff queue."),image:"/assets/images/webp/web/integrations/intercom-2.webp"},{title:__("Qualify from customer state changes"),description:__("Use the engagement and lifecycle logic already in Intercom to help decide when a referral should progress."),image:"/assets/images/webp/web/integrations/intercom-video.webp"}],workflowDescription:"This setup works best when customer success, onboarding, or lifecycle teams already think in Intercom-first terms.",workflowSteps:[{title:__("Target the right customer moment"),description:__("Choose the points where customers are most likely to share, not just the points where the system can send a message."),image:"/assets/images/webp/web/integrations/intercom-1.webp"},{title:__("Track the referral inside Referral Factory"),description:__("Keep attribution and referral mechanics separate from the messaging layer, but connected to it."),image:"/assets/images/webp/web/integrations/intercom-2.webp"},{title:__("Watch for the customer milestone that matters"),description:__("Use Intercom data to signal when the referred person became meaningful enough to qualify."),image:"/assets/images/webp/web/integrations/intercom-video.webp"},{title:__("Trigger reward or follow-up logic"),description:__("Once the lifecycle c
1ondition is met, the team no longer has to manually reconcile referral success."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for teams that already manage customer engagement, onboarding, or support-led growth inside Intercom.",fitItems:[{title:__("Customer success teams"),description:__("Useful when referral prompts should align with successful onboarding, support wins, or usage momentum.")},{title:__("Lifecycle marketing teams"),description:__("Useful when referral asks should be segmented and timed according to the customer journey.")},{title:__("Product-led businesses"),description:__("Good fit when customer engagement data is already the best indicator of who is ready to refer.")}],milestone:"the lifecycle, engagement, or custom data signal that proves the referral is progressing",checklistOwner:"customer success or lifecycle owner",finalDescription:"If the team already uses Intercom to spot the right customer moment, it can also become the operating layer that tells referral automation what should happen next.",automationSummary:"time referral enrolment around real customer moments, surface referred people to the right team, and qualify progress from the lifecycle signals already in Intercom",processSummary:"No. Intercom remains the customer lifecycle layer. Referral Factory adds referral tracking and reward logic without asking the team to leave the workflow it already uses."},{key:"monday",name:"Monday.com",iconId:"monday",metaDescription:"Use Monday.com and Referral Factory together to route referrals into operational boards, qualify them from live status changes, and keep the handoff clean.",heroDescription:"When your team already lives in boards, statuses, and operational workflows, Monday.com can become the system that tells your referral program what changed and what needs to happen next.",timingNote:"Best when teams qualify progress through board status, work stages, or structured ops workflows.",heroImage:"/assets/images/webp/web/integrations/monday-2.webp",heroImageAlt:"Monday.com referral workflow",sourceCard:{value:__("Ops"),label:__("Workflow layer"),description:__("Monday.com is useful when the referral handoff needs to fit a structured internal workflow rather than a pure CRM or billing motion."),tone:"dark"},whyDescription:"Monday.com becomes valuable when the team wants referrals to move through the same operational stages already used to manage work and follow-up.",whyItems:[{title:__("Referrals can follow the board structure the team already runs"),description:__("That makes ownership, visibility, and follow-up much clearer than pushing referrals into a disconnected inbox."),image:"/assets/images/webp/web/integrations/monday-1.webp"},{title:__("Qualification can follow live status changes"),description:__("Use the board state that already reflects progress instead of relying on someone to remember a manual update."),image:"/assets/images/webp/web/integrations/monday-2.webp"},{title:__("Cross-functional teams get cleaner handoffs"),description:__("Marketing, sales, and ops can all see the same referral state without building a shadow workflow."),image:"/assets/images/webp/web/integrations/monday-video.webp"}],capabilities:[{title:__("Generate links for the customers you already manage"),description:__("Keep referral enrolment tied to the people the team already tracks in Monday.com."),image:"/assets/images/webp/web/integrations/monday-1.webp"},{title:__("Route new referred people into an operating board"),description:__("That gives the internal team a visible next step instead of a disconnected referral record."),image:"/assets/images/webp/web/integrations/monday-2.webp"},{title:__("Qualify from board progress"),description:__("Use the stage or status that already means something internally to trigger qualification and reward decisions."),image:"/assets/images/webp/web/integrations/monday-video.webp"}],workflowDescription:"This works best when Monday.com already reflects how the team measures progress and ownership in the real world.",workflowSteps:[{title:__("Start with the right customer cohort"),description:__("Enrol customers or partners the team already tracks in the board structure."),image:"/assets/images/webp/web/integrations/monday-1.webp"},{title:__("Capture referred people into the active workflow"),description:__("Move the referral into the same operating board instead of creating a separate process to watch."),image:"/assets/images/webp/web/integrations/monday-2.webp"},{title:__("Qualify from a trusted status change"),description:__("Use the board state the team already relies on when deciding whether work actually progressed."),image:"/assets/images/webp/web/integrations/monday-video.webp"},{title:__("Keep rewards tied to the operational milestone"),description:__("That reduces disputes about whether the referral really completed the step that matters."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for teams that already run cross-functional work in Monday.com and want referrals to fit those same internal stages.",fitItems:[{title:__("Operations-led teams"),description:__("Useful when the operational board is already the source of truth for what happened next.")},{title:__("Cross-functional growth teams"),description:__("Useful when marketing, sales, and ops all need visibility into referral progress.")},{title:__("Service businesses with structured workflows"),description:__("Good fit when referrals need to move through an internal process before they should qualify.")}],milestone:"the board status or work stage that marks a commercially meaningful outcome",checklistOwner:"operations owner",finalDescription:"If Monday.com already tells the team what changed, who owns it, and whether it progressed, it can also tell your referral workflow when to move and when to reward.",automationSummary:"enrol the right people, route referred contacts into active boards, and qualify them from the status changes the team already uses to run work",processSummary:"No. Monday.com remains the operational layer. Referral Factory adds referral tracking and qualification logic around the board states your team already trusts."},{key:"zoho",name:"Zoho",iconId:"zoho",metaDescription:"Use Zoho and Referral Factory together to route referrals into CRM workflows, qualify them from live data, and run cleaner referral operations.",heroDescription:"Zoho is a good fit when your team already uses CRM workflow, status logic, and custom properties to run day-to-day commercial activity. Referral qualification becomes much simpler when it is tied to data the team already updates.",timingNote:"Best when Zoho already carries the customer lifecycle or pipeline milestone that matters.",heroImage:"/assets/images/webp/web/integrations/zoho-2.webp",heroImageAlt:"Zoho referral workflow",sourceCard:{value:__("CRM"),label:__("Live pipeline"),description:__("Zoho can become the operating layer for referral qualification when the team already relies on it to track lead and deal progression."),tone:"dark"},whyDescription:"Zoho works well here because it gives the business one place to manage customer records, follow-up workflow, and the qualification signal for referral outcomes.",whyItems:[{title:__("Customer and referral data stay close together"),description:__("That reduces handoffs and makes it easier for the team to see what happened to a referred lead."),image:"/assets/images/webp/web/integrations/zoho-1.webp"},{title:__("Qualification can use live CRM movement"),description:__("Use the statuses and properties already driving work in Zoho instead of maintaining a separate referral spreadsheet."),image:"/assets/images/webp/web/integrations/zoho-2.webp"},{title:__("Reward operations become easier to justify"),description:__("When the CRM milestone is clear, the business can defend why a reward was or was not issued."),image:"/assets/images/webp/web/integrations/zoho-video.webp"}],capabilities:[{title:__("Enrol existing contacts into the referral program"),description:__("Generate referral links from the contacts already managed inside Zoho."),image:"/assets/images/webp/web/integrations/zoho-1.webp"},{title:__("Push referred people into live CRM workflow"),description:__("The team can then manage referrals inside the same sales or service motion it already understands."),image:"/assets/images/webp/web/integrations/zoho-2.webp"},{title:__("Use Zoho milestones to qualify and trigger rewards"),description:__("Tie qual
1ification to the data points the business already trusts rather than inventing a second decision layer."),image:"/assets/images/webp/web/integrations/zoho-video.webp"}],workflowDescription:"The best Zoho setup keeps qualification tied to real CRM progression and keeps referral mechanics out of ad hoc admin work.",workflowSteps:[{title:__("Pick the customer cohort to enrol"),description:__("Use the records already most likely to refer rather than sending broad untargeted referral asks."),image:"/assets/images/webp/web/integrations/zoho-1.webp"},{title:__("Capture referred people into Zoho"),description:__("That keeps follow-up, assignment, and lifecycle movement inside the same CRM."),image:"/assets/images/webp/web/integrations/zoho-2.webp"},{title:__("Qualify from the CRM milestone"),description:__("Use the stage or custom property that already marks real progress for the team."),image:"/assets/images/webp/web/integrations/zoho-video.webp"},{title:__("Run reward logic after the milestone is met"),description:__("This keeps referral ops and commercial ops aligned instead of creating two versions of the truth."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for teams that already use Zoho as the working system for customer, lead, or sales workflow.",fitItems:[{title:__("SMB sales teams"),description:__("Useful when the CRM already manages ownership, stage progression, and commercial context.")},{title:__("Service teams working from CRM records"),description:__("Useful when referrals should flow into existing contact and deal operations instead of creating extra admin.")},{title:__("Operators who need clear reward triggers"),description:__("Good fit when internal trust matters and rewards should only move after a clearly defined CRM state change.")}],milestone:"the Zoho stage, status, or custom property that marks real progress",checklistOwner:"CRM or operations owner",finalDescription:"If Zoho already holds the customer truth, it can also hold the qualification truth for referrals so the team does not need to reconcile two systems manually.",automationSummary:"enrol contacts from Zoho, route referred leads into the CRM, and qualify them from live stage or property changes already used by the team",processSummary:"No. Zoho remains the CRM system of record. Referral Factory layers referral tracking and reward logic around the milestones the team already uses."},{key:"zapier",name:"Zapier",iconId:"zapier",metaDescription:"Use Zapier and Referral Factory together to connect referral workflows across the rest of your stack without hand-coding every integration path.",heroDescription:"Zapier is useful when the real workflow spans multiple tools. Instead of forcing everything into one system, you can use Zapier to move referral events between the tools your team already depends on.",timingNote:"Best when your referral workflow needs to cross tools instead of living entirely inside one CRM or billing platform.",heroImage:"/assets/images/webp/web/integrations/zapier-2.webp",heroImageAlt:"Zapier referral workflow",sourceCard:{value:__("Automation"),label:__("Cross-tool workflow"),description:__("Zapier works best when the referral process needs to bridge systems rather than rely on one source of truth alone."),tone:"dark"},whyDescription:"Zapier matters when the real barrier is not referral tracking. It is the number of tools involved in getting a referral from sign-up to qualification.",whyItems:[{title:__("You can connect the rest of the stack"),description:__("Move referral data between forms, CRMs, email tools, and internal systems without asking engineering to custom-build every handoff."),image:"/assets/images/webp/web/integrations/zapier-1.webp"},{title:__("Qualification can still stay rule-based"),description:__("Even across multiple tools, you can keep one clear qualifying event rather than creating a messy chain of assumptions."),image:"/assets/images/webp/web/integrations/zapier-2.webp"},{title:__("Teams can move faster on operational changes"),description:__("This is useful when the workflow changes often and the business needs a flexible automation layer rather than a fixed point integration."),image:"/assets/images/webp/web/integrations/zapier-video.webp"}],capabilities:[{title:__("Push referral events into the tools you already use"),description:__("Use Zapier as the relay layer when referrals need to reach more than one system."),image:"/assets/images/webp/web/integrations/zapier-1.webp"},{title:__("Bring qualifying events back into Referral Factory"),description:__("When another tool confirms the outcome, Zapier can pass the signal back cleanly."),image:"/assets/images/webp/web/integrations/zapier-2.webp"},{title:__("Reduce engineering dependency"),description:__("For many teams, the win is not just automation. It is being able to change the workflow without a development ticket every time."),image:"/assets/images/webp/web/integrations/zapier-video.webp"}],workflowDescription:"The strongest Zapier setup uses one clear qualifying event and treats Zapier as the transport layer between the tools that matter.",workflowSteps:[{title:__("Choose the systems that need to talk"),description:__("Map where customers start, where referred people should go, and where the qualifying event actually happens."),image:"/assets/images/webp/web/integrations/zapier-1.webp"},{title:__("Send referral events out of Referral Factory"),description:__("Use Zapier to move those events into the CRM, helpdesk, database, or internal tool that needs them."),image:"/assets/images/webp/web/integrations/zapier-2.webp"},{title:__("Watch for the conversion event in the right tool"),description:__("Do not guess. Pick one event that clearly means the referral should qualify."),image:"/assets/images/webp/web/integrations/zapier-video.webp"},{title:__("Pass the qualification signal back cleanly"),description:__("That allows rewards and downstream referral logic to run without manual stitching."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for teams with multi-tool workflows that do not want to custom-build every single referral handoff.",fitItems:[{title:__("Lean teams without heavy engineering bandwidth"),description:__("Useful when the business wants to connect tools quickly and iterate without code-heavy implementation work.")},{title:__("Teams operating across multiple apps"),description:__("Useful when customer data, lead handling, and qualification already live in different systems.")},{title:__("Operators who value flexibility over one fixed integration"),description:__("Good fit when the workflow changes often and the automation path needs to adapt with it.")}],milestone:"the event in your stack that clearly proves the referral converted",checklistOwner:"ops or automation owner",finalDescription:"If the referral workflow crosses more than one tool, Zapier gives you a practical way to move the signal between them without turning the setup into a custom engineering project.",automationSummary:"send referral events into the rest of your stack, watch for the qualifying event in the right tool, and return the signal when the referral should progress",processSummary:"Usually not. Zapier is most useful when it adapts to the workflow you already have rather than forcing the team into a
1new operating model."},{key:"pipedrive",name:"Pipedrive",iconId:"pipedrive",metaDescription:"Use Pipedrive and Referral Factory together to route referrals into your pipeline, qualify them from deal progress, and keep the process easy for sales teams to run.",heroDescription:"Pipedrive is strongest when the sales pipeline is the real source of truth. If the team already measures progress in deal stages and ownership, referral qualification should use the same motion rather than a parallel process.",timingNote:"Best when referred demand should qualify from deal stage movement in Pipedrive.",heroImage:"/assets/images/webp/web/integrations/pipedrive-2.webp",heroImageAlt:"Pipedrive referral workflow",sourceCard:{value:__("Pipeline"),label:__("Sales signal"),description:__("Pipedrive works well when the team already treats deal stages as the clearest sign of commercial progress."),tone:"dark"},whyDescription:"Pipedrive matters here because it lets the team qualify referrals from the same pipeline logic already used to run core sales work.",whyItems:[{title:__("Referred leads land in the pipeline the team already runs"),description:__("That reduces the chance that referral leads are treated differently from other opportunities."),image:"/assets/images/webp/web/integrations/pipedrive-1.webp"},{title:__("Deal stage becomes the qualifying milestone"),description:__("You can tie rewards to the point where the business already believes the deal became meaningful."),image:"/assets/images/webp/web/integrations/pipedrive-2.webp"},{title:__("Sales teams get less admin"),description:__("The cleaner the workflow inside the CRM, the less time the team spends explaining whether a referral really counted."),image:"/assets/images/webp/web/integrations/pipedrive-video.webp"}],capabilities:[{title:__("Generate referral links from existing contacts"),description:__("Start from real customers already tracked in Pipedrive rather than a broad export list."),image:"/assets/images/webp/web/integrations/pipedrive-1.webp"},{title:__("Route referred leads into the active pipeline"),description:__("Keep ownership and next steps inside the same sales workflow the team already follows."),image:"/assets/images/webp/web/integrations/pipedrive-2.webp"},{title:__("Qualify from deal stage movement"),description:__("Use the deal progression that already means something commercially instead of maintaining a separate referral status log."),image:"/assets/images/webp/web/integrations/pipedrive-video.webp"}],workflowDescription:"This setup works best when the sales team already trusts Pipedrive to show whether an opportunity became real.",workflowSteps:[{title:__("Enrol the customer group most likely to refer"),description:__("Give existing customers a clean path into the referral program from the records you already have."),image:"/assets/images/webp/web/integrations/pipedrive-1.webp"},{title:__("Push referred leads into the pipeline"),description:__("Make sure referred demand follows the same ownership and follow-up rules as any other deal."),image:"/assets/images/webp/web/integrations/pipedrive-2.webp"},{title:__("Qualify from the deal stage that matters"),description:__("Do not overcomplicate it. Pick one stage that clearly means the referral reached a real commercial threshold."),image:"/assets/images/webp/web/integrations/pipedrive-video.webp"},{title:__("Trigger reward logic once the deal reaches that stage"),description:__("That keeps sales reporting and referral reporting aligned."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for sales teams that already treat Pipedrive as the working system for opportunity progression and ownership.",fitItems:[{title:__("Sales-led SMB teams"),description:__("Useful when referrals should behave like normal pipeline opportunities instead of a separate demand source.")},{title:__("Operators who want simpler qualification"),description:__("Useful when one deal stage can serve as the clean rule for when rewards should progress.")},{title:__("Teams avoiding spreadsheet reconciliation"),description:__("Good fit when the main pain is manually connecting referral attribution to sales movement.")}],milestone:"the Pipedrive deal stage that marks a qualified commercial outcome",checklistOwner:"sales owner",finalDescription:"If Pipedrive already tells your team when a deal became meaningful, it can also tell the referral program when to qualify and when to move rewards forward.",automationSummary:"generate links from existing contacts, route referred leads into the active pipeline, and qualify them from deal stage movement",processSummary:"No. Pipedrive should remain the sales workflow. Referral Factory adds referral-specific tracking and reward operations around the pipeline process the team already uses."},{key:"servicetitan",name:"ServiceTitan",iconId:"servicetitan",metaDescription:"Use ServiceTitan and Referral Factory together to route referrals into your home-service workflow, qualify them from booked or c
1ompleted work, and cut admin.",heroDescription:"For many home-service teams, the real milestone is not a form fill. It is the booked job, completed job, or revenue event that happens inside ServiceTitan. That makes it a practical place to anchor referral qualification.",timingNote:"Best when booked work, completed work, or another ServiceTitan milestone should decide qualification.",heroImage:"/assets/images/webp/web/integrations/servicetitan-2.webp",heroImageAlt:"ServiceTitan referral workflow",sourceCard:{value:__("Jobs"),label:__("Service workflow"),description:__("ServiceTitan is useful when the operational truth is the booked or completed job, not just the initial lead record."),tone:"dark"},whyDescription:"ServiceTitan is powerful in referral programs because it connects the lead to the real operational outcome the business actually gets paid for.",whyItems:[{title:__("Qualification can wait for a real service milestone"),description:__("That protects margins and reduces the risk of rewarding too early on low-quality referrals."),image:"/assets/images/webp/web/integrations/servicetitan-1.webp"},{title:__("Home-service teams stay in the system they already run"),description:__("Dispatch, sales, and operations do not need a second process to understand where the referral went."),image:"/assets/images/webp/web/integrations/servicetitan-2.webp"},{title:__("Referral ops line up with real job outcomes"),description:__("That makes both reporting and reward logic easier to trust."),image:"/assets/images/webp/web/integrations/servicetitan-video.webp"}],capabilities:[{title:__("Enrol existing customers after completed work"),description:__("Start from customers who already experienced the service instead of asking every lead to become a referrer."),image:"/assets/images/webp/web/integrations/servicetitan-1.webp"},{title:__("Route referred opportunities into the service workflow"),description:__("Make referrals visible where the team already books, manages, and follows through on the work."),image:"/assets/images/webp/web/integrations/servicetitan-2.webp"},{title:__("Qualify from the job milestone that matters"),description:__("Use the stage that already proves the referral turned into actual business."),image:"/assets/images/webp/web/integrations/servicetitan-video.webp"}],workflowDescription:"The cleanest ServiceTitan setup lets referral attribution and operational completion work together instead of existing in separate admin flows.",workflowSteps:[{title:__("Enrol satisfied customers"),description:__("Target the people who already had the positive service moment most likely to create a referral."),image:"/assets/images/webp/web/integrations/servicetitan-1.webp"},{title:__("Capture new referred jobs or opportunities"),description:__("Move them into the live service workflow instead of handling them in a disconnected referral list."),image:"/assets/images/webp/web/integrations/servicetitan-2.webp"},{title:__("Use the job milestone to qualify"),description:__("Choose the ServiceTitan stage that clearly marks a successful commercial outcome."),image:"/assets/images/webp/web/integrations/servicetitan-video.webp"},{title:__("Trigger reward action only after real work happens"),description:__("That keeps the economics clean and prevents premature reward handling."),image:"/assets/images/webp/web/unique/integrations.webp"}],fitDescription:"Best for home-service businesses where ServiceTitan already reflects the real operational and commercial outcome.",fitItems:[{title:__("Plumbing, HVAC, and field-service teams"),description:__("Useful when booked or completed jobs are the milestone that actually matters for referral quality.")},{title:__("Operations-led businesses"),description:__("Useful when dispatch, job progression, and follow-through are already managed centrally in ServiceTitan.")},{title:__("Teams that want to pay rewards later, not earlier"),description:__("Good fit when margin protection matters and rewards should only move after a real operational outcome.")}],milestone:"the booked, completed, or revenue-linked ServiceTitan job milestone you trust",checklistOwner:"service operations owner",finalDescription:"If ServiceTitan already tells the business when a referred customer turned into real work, it should also tell the referral program when to qualify and when to reward.",automationSummary:"enrol satisfied customers, send referred opportunities into the service workflow, and qualify them from booked or c
1ompleted job milestones",processSummary:"No. ServiceTitan remains the operations system. Referral Factory adds referral attribution and reward logic around the service milestones that already matter."},{key:"make",name:"Make.com",iconId:"make",metaDescription:"Use Make.com and Referral Factory together to build multi-step referral automations across your stack with more control than a single fixed integration.",heroDescription:"Make.com is useful when the referral workflow needs branching logic, multiple systems, or more control than a single direct integration gives you. It becomes the orchestration layer around the referral events.",timingNote:"Best when the workflow spans several apps or needs more custom branching than a single point integration.",heroImage:"/assets/images/webp/web/integrations/make-2.webp",heroImageAlt:"Make.com referral workflow",sourceCard:{value:__("Scenarios"),label:__("Orchestration layer"),description:__("Make.com works well when the business needs to connect referral events to several actions across several systems."),tone:"dark"},whyDescription:"Make.com matters when the referral workflow is more complex than one source system and one qualifying milestone.",whyItems:[{title:__("You can design the referral flow end to end"),description:__("That matters when referral events need branching logic, extra enrichment, or multiple destinations."),image:"/assets/images/webp/web/integrations/make-1.webp"},{title:__("Multi-system setups stay manageable"),description:__("Make.com gives operations teams a way to keep the logic visible instead of hiding it in custom scripts."),image:"/assets/images/webp/web/integrations/make-2.webp"},{title:__("Qualification signals can come from anywhere in the flow"),description:__("As long as the event is clear, you can still bring the qualifying signal back into Referral Factory cleanly."),image:"/assets/images/webp/web/integrations/zoho-video.webp"}],capabilities:[{title:__("Send referral events into multi-step scenarios"),description:__("Use Make.com when the handoff needs more than just a single direct push into one destination."),image:"/assets/images/webp/web/integrations/make-1.webp"},{title:__("Transform and route data before it lands"),description:__("This is useful when the target systems need the referral data shaped differently or enriched first."),image:"/assets/images/webp/web/integrations/make-2.webp"},{title:__("Return a clear qualification event"),description:__("Bring the right status back once the flow reaches the event that should qualify the referral."),image:"/assets/images/webp/web/unique/integrations.webp"}],workflowDescription:"The strongest Make.com setup treats Referral Factory as the referral engine and Make.com as the orchestration layer around it.",workflowSteps:[{title:__("Map the systems involved"),description:__("Identify where enrolment starts, where referred people should go, and where the qualifying event is produced."),image:"/assets/images/webp/web/integrations/make-1.webp"},{title:__("Build the scenario that routes the event"),description:__("Use Make.com to move, enrich, and branch referral data as needed."),image:"/assets/images/webp/web/integrations/make-2.webp"},{title:__("Wait for the conversion event that matters"),description:__("Keep the qualifying signal explicit so the reward rule does not become ambiguous."),image:"/assets/images/webp/web/unique/integrations.webp"},{title:__("Pass the signal back into Referral Factory"),description:__("That keeps qualification and reward logic consistent even in a more complex automation flow."),image:"/assets/images/webp/web/integrations/webhook.webp"}],fitDescription:"Best for operations teams that need more control, more branching logic, or more multi-system coordination than a direct integration offers.",fitItems:[{title:__("Ops teams running several systems"),description:__("Useful when referral data needs to touch a CRM, database, helpdesk, and internal tool in the same flow.")},{title:__("Teams with custom automation needs"),description:__("Useful when the business wants more logic and transformation than a fixed app-to-app path can provide.")},{title:__("Operators who want visibility into the flow"),description:__("Good fit when it matters that the team can actually understand and change the automation later.")}],milestone:"the scenario event that clearly marks the referral as commercially qualified",checklistOwner:"automation owner",finalDescription:"If the referral workflow needs orchestration across more than one system, Make.com gives you a practical way to build that flow without hiding the logic in custom code.",automationSummary:"send referral events into multi-step scenarios, transform or route them across the stack, and return the clean qualifying signal when it happens",processSummary:"Usually not. Make.com is most useful when it adapts around your existing systems rather than replacing them with a new monolithic workflow."}],v=a(r.find(e=>e.key==="hubspot")),k=a(r.find(e=>
1e.key==="stripe")),q=a(r.find(e=>e.key==="salesforce")),S=a(r.find(e=>e.key==="intercom")),I=a(r.find(e=>e.key==="monday")),R=a(r.find(e=>e.key==="zoho")),C=a(r.find(e=>e.key==="zapier")),T=a(r.find(e=>e.key==="pipedrive")),D=a(r.find(e=>e.key==="servicetitan")),M=a(r.find(e=>e.key==="make")),U=d({variant:"integration_api",name:"Webhooks and API",metaTitle:"Referral Program API and Webhooks | Referral Factory",metaDescription:"Use the Referral Factory API and webhooks to push referral events into your own systems, qualify conversions from custom milestones, and run developer-controlled referral workflows.",milestone:"the custom event or backend state your product team already treats as truth",checklistOwner:"product, engineering, or technical operations owner",hero:{eyebrow:__("Developer workflow"),titleLead:__("Build referral operations"),titleHighlight:__("into your own stack"),titleTrail:__("without giving up control."),description:__("When your customer data, business rules, or conversion logic live in custom systems, the API and webhooks give you the control to wire Referral Factory into that reality. Use it when direct no-code integrations are too narrow for the workflow you need."),timingNote:__("Best when qualification lives in your own backend, product events, or custom operational logic."),sideCards:[{value:__("API"),label:__("Developer-controlled"),description:__("Create users, generate links, issue rewards, and manage referral data from your own product or backend when the workflow needs full control."),tone:"dark"},{value:__("Webhooks"),label:__("Event transport"),description:__("Send new referrals out, receive qualifying events back, and keep the referral engine stitched into the rest of your stack."),tone:"yellow"}],visual:{accentLabel:__("Flexible integration path"),iconId:"api",image:"/assets/images/webp/web/integrations/webhook.webp",alt:"Referral Factory API and webhook workflow"}},whyItMatters:{title:__("Why teams choose API and webhooks instead of a fixed integration"),description:__("The developer path is not about making things harder. It is about fitting Referral Factory into systems, rules, and product logic that are already unique to your business."),items:[{title:__("Your product already owns the customer truth"),description:__("If enrolment, conversion, or reward logic already lives in your own backend, the cleanest approach is to integrate directly with that source of truth."),image:"/assets/images/webp/web/integrations/macbook.webp"},{title:__("Qualification can follow custom business events"),description:__("Use the event that actually matters in your system, whether that is a funded account, approved workflow, completed action, or internal state change."),image:"/assets/images/webp/web/integrations/webhook.webp"},{title:__("You keep control of the orchestration"),description:__("Engineering teams can decide how events move, how data is shaped, and how tightly referral logic fits the rest of the platform."),image:"/assets/images/webp/web/unique/integrations.webp"}],bullets:[__("Use the API when your system needs to create or update referral participants directly."),__("Use webhooks when referral events should feed your own services or trigger downstream automation."),__("Bring the qualifying event back only when the business rule is truly satisfied.")]},capabilities:{title:__("What your team can orchestrate with the developer path"),description:__("The useful pattern is to let your own systems stay in control of customer truth while Referral Factory handles the referral mechanics and reward state."),items:[{title:__("Create users and generate referral links programmatically"),description:__("Your backend can enrol users in real time instead of waiting for a manual sync or a UI-driven workflow."),image:"/assets/images/webp/web/integrations/macbook.webp"},{title:__("Send referral events out to internal systems"),description:__("Use webhooks to push new referrals into your own processing layer, data warehouse, CRM, or queue-based architecture."),image:"/assets/images/webp/web/integrations/webhook.webp"},{title:__("Qualify and reward from custom events"),description:__("Once your system knows a referral met the business rule, push that event back so the referral workflow can progress cleanly."),image:"/assets/images/webp/web/unique/integrations.webp"}]},workflow:{title:__("How the developer workflow should be structured"),description:__("Keep the boundary clean: your system owns the product logic, Referral Factory owns the referral state, and events move explicitly between them."),steps:[{title:__("Create or sync participants from your backend"),description:__("Enrol users at the moment that makes sense inside your product instead of forcing a separate manual action."),image:"/assets/images/webp/web/integrations/macbook.webp"},{title:__("Receive and route referral events"),description:__("Use webhooks when new referrals need to enter your internal processing flow immediately."),image:"/assets/images/webp/web/integrations/webhook.webp"}
1,{title:__("Wait for the real internal conversion signal"),description:__("Qualify only when your own product or business logic says the referral truly reached the required outcome."),image:"/assets/images/webp/web/unique/integrations.webp"},{title:__("Push qualification and reward actions back intentionally"),description:__("That keeps your architecture explicit and avoids brittle assumptions about state."),image:"/assets/images/webp/web/integrations/macbook.webp"}]},fit:{title:__("Who should choose the API and webhook path"),description:__("This path makes sense when the business needs more control than a direct integration or no-code tool can realistically provide."),items:[{title:__("Product teams with custom backend logic"),description:__("Use this when the important milestones live inside your own application or database rather than in a third-party tool.")},{title:__("Technical operations teams"),description:__("Use this when the workflow spans several systems and the team wants explicit event handling instead of an opaque point integration.")},{title:__("Businesses with unique qualification rules"),description:__("Good fit when referral success depends on custom underwriting, verification, approval, or product behaviour the off-the-shelf integrations cannot express cleanly.")}]},finalCta:{title:__("Wire Referral Factory into the system you already trust"),description:__("If your business logic already lives in your own stack, the API and webhooks let you keep that architecture intact while still running a real referral engine."),image:"/assets/images/webp/web/integrations/macbook.webp",imageAlt:"Referral Factory API setup",features:[{title:__("Keep your own source of truth"),description:__("Do not flatten custom business logic into a workflow that cannot express it properly.")},{title:__("Move events explicitly"),description:__("Use the systems and queues you already trust instead of adding hidden handoffs.")},{title:__("Qualify from real business state"),description:__("Reward only when the internal event that matters has actually happened.")}]},faq:{title:__("Questions technical teams usually ask first"),description:__("The API path gives you flexibility, but the implementation still needs clear ownership and clean event boundaries."),items:[t("When should we choose the API path instead of a direct integration?","Choose the API or webhook path when your qualification logic, customer records, or orchestration needs already live in your own systems and a direct integration would force the wrong architecture."),t("What can we do through the API?","You can create and manage participants, generate referral links, work with referral data, and drive parts of the referral lifecycle programmatically from your own backend."),t("What are webhooks useful for?","Webhooks are useful when referral events need to trigger activity in your own systems immediately, or when your own systems need to send a clean qualifying event back once the business milestone is complete."),t("Who should own the implementation?","Give ownership to the team that understands both the business rule and the architecture boundary. In most cases that means product engineering or technical operations, not a marketing-only owner.")]}}),x=[{badge:__("Rewards"),title:__("Rewards"),description:__("Automate how incentives trigger, what people receive, and how reward operations stay tied to real outcomes."),href:"/rewards"},{badge:__("CRM"),title:__("HubSpot"),description:__("Use lifecycle and pipeline movement to route and qualify referrals inside your existing CRM workflow."),href:"/integrations/hubspot"},{badge:__("Payments"),title:__("Stripe"),description:__("Qualify referrals from payment and subscription events, and use Stripe promo codes when checkout needs a code-based referral path."),href:"/integrations/stripe"},{badge:__("CRM"),title:__("Salesforce"),description:__("Keep referred demand inside the revenue workflow the team already runs and reports on."),href:"/integrations/salesforce"},{badge:__("Lifecycle"),title:__("Intercom"),description:__("Trigger referral activity from real customer moments and lifecycle signals instead of generic asks."),href:"/integrations/intercom"},{badge:__("Ops"),title:__("Monday.com"),description:__("Route referrals into board-driven operational workflows and qualify them from live status movement."),href:"/integrations/monday"},{badge:__("Developer"),title:__("Webhooks and API"),description:__("Push referral events into your own systems and qualify them from custom product or backend logic."),href:"/integrations/webhook-api"},{badge:__("CRM"),title:__("Zoho"),description:__("Manage referral enrolment, lead routing, and qualification from the CRM states your team already trusts."),href:"/integrations/zoho"},{badge:__("Automation"),title:__("Zapier"),description:__("Connect referral workflows across the rest of your stack without hand-coding every path."),href:"/integrations/zapier"},{badge:__("Pipeline"),title:__("Pipedrive"),description:__("Tie referral qualification to deal stage movement so the sales team has one operating truth."),href:"/integrations/pipedrive"},{badge:__("Jobs"),title:__("ServiceTitan"),description:__("Qualify referrals from booked or c
1ompleted work instead of rewarding too early in the home-service cycle."),href:"/integrations/servicetitan"},{badge:__("Automation"),title:__("Make.com"),description:__("Orchestrate referral events across several systems when a fixed point integration is not enough."),href:"/integrations/make"}],P={variant:"integration_hub",metaTitle:"Referral Program Integrations and Rewards | Referral Factory",metaDescription:"Referral marketing software integrations for mid-market, enterprise, and multi-location teams connecting referral programs to CRM, payments, automation, and APIs.",hero:{eyebrow:__("Integrations"),titleLead:__("Integrations and rewards should make"),titleHighlight:__("referral programs easier"),titleTrail:__("to operate."),description:__("Referral Factory is referral marketing software for mid-market companies, enterprise teams and multi-location businesses that need to launch, manage and scale customer referral programs. Connect customer records, qualification events and reward operations to the systems your teams already use."),buttons:[{href:route("auth.register"),label:__("Start Free Trial"),tone:"primary"},{href:"/demo",label:__("Book Demo"),tone:"secondary"},{href:"/rewards",label:__("Explore Rewards"),tone:"ghost"}],sideCards:[{value:__("CRM"),label:__("Customer and pipeline workflows"),description:__("Use the systems your team already trusts for customer context, sales progression, or lifecycle qualification."),tone:"dark"},{value:__("Payments"),label:__("Revenue-linked qualification"),description:__("Tie referral success to the commercial milestone that actually matters instead of a vague top-of-funnel event."),tone:"yellow"},{value:__("Rewards"),label:__("Automated incentive operations"),description:__("Run reward strategy, triggering, and fulfilment without turning the team into spreadsheet operators."),tone:"white"}],visual:{accentLabel:__("Acquisition workflow set"),image:"/assets/images/webp/web/unique/integrations.webp",alt:"Referral Factory integrations"}},navigation:{eyebrow:__("Choose the right workflow layer"),title:__("Start with the system that already owns the truth"),description:__("The cleanest referral automation happens when you anchor it to the system that already holds the customer, revenue, or operational milestone your business believes in."),cards:x},capabilities:{eyebrow:__("What a good integration strategy should do"),pill:__("Built for live programs"),title:__("The point is not more tooling. It is less admin."),description:__("Every page in this section should help the team do one of three things better: enrol the right people, qualify on the right milestone, and issue the right reward without a cleanup project."),items:[{title:__("Keep qualification close to the real commercial event"),description:__("Whether that event is a paid invoice, a deal stage, or a completed job, the strongest setup uses the milestone the business already trusts."),image:"/assets/images/webp/web/integrations/stripe-2.webp"},{title:__("Reduce the number of manual handoffs"),description:__("If a referral program creates another spreadsheet or another queue to reconcile, the workflow is not finished yet."),image:"/assets/images/webp/web/integrations/hubspot-2.webp"},{title:__("Tie reward operations to real outcomes"),description:__("Rewards work better when triggering rules are obvious, auditable, and easy for the team to explain internally."),image:"/assets/images/webp/web/unique/reward-couple.webp"}],bullets:[__("Choose direct integrations when one system already owns the right milestone."),__("Choose automation tools when the workflow crosses multiple apps."),__("Choose API and webhooks when your own stack owns the business logic.")]},workflow:{eyebrow:__("How to choose"),title:__("A practical selection flow for the integration layer"),description:__("Do not choose based on feature lists alone. Choose based on where your team already decides that a referral became commercially real."),steps:[{title:__("Find the source of truth"),description:__("Identify the system that already carries the customer or conversion milestone the business trusts most."),image:"/assets/images/webp/web/integrations/hubspot-1.webp"},{title:__("Choose the cleanest handoff path"),description:__("Use a direct integration when possible, then fall back to automation or API only when the workflow genuinely requires it."),image:"/assets/images/webp/web/integrations/zapier-2.webp"},{title:__("Define one qualifying milestone"),description:__("Make the trigger obvious so rewards, reporting, and operations all stay aligned."),image:"/assets/images/webp/web/integrations/stripe-1.webp"},{title:__("Design rewards around that milestone"),description:__("The integration and the reward strategy should reinforce each other rather than operate as separate decisions."),image:"/assets/images/webp/web/rewards/stripe.webp"}]},finalCta:{eyebrow:__("Start with the workflow, not the logo"),title:__("Choose the connection that matches how y
1our team already works"),description:__("If the integration layer fits your existing customer, sales, billing, or operations workflow, the referral program becomes easier to launch, easier to qualify, and much easier to keep running."),image:"/assets/images/webp/web/unique/integrations.webp",imageAlt:"Referral Factory integrations and rewards",imageFrameTone:"white",features:[{title:__("Cleaner handoffs"),description:__("Keep referrals inside the workflow the team already uses instead of adding another disconnected process.")},{title:__("Better qualification"),description:__("Use the milestone the business already trusts to decide when a referral really converted.")},{title:__("Faster reward operations"),description:__("When the qualifying event is clear, reward logic becomes much easier to automate and defend.")}]},faq:{eyebrow:__("FAQ"),title:__("Questions teams ask before choosing an integration path"),description:__("Most implementation mistakes come from anchoring the workflow to the wrong system or using too many handoffs. These are the questions that help prevent that."),items:[t("How do we know which integration path to choose?","Choose the system that already holds the business milestone you trust most. If one tool already tells you when the referral really converted, start there."),t("When should we choose automation tools like Zapier or Make instead of a direct integration?","Choose automation tools when the workflow genuinely spans several systems and no single direct integration covers the full path cleanly."),t("How does rewards fit into this section?","Rewards are part of the same operating workflow. Qualification, automation, and rewards only work well when they are designed together instead of as separate systems."),t("Do we need to use every integration at once?","No. The strongest setup usually starts with one clean qualification layer, one reward rule, and one clear owner. Complexity should be earned, not assumed.")]}},F={variant:"rewards",metaTitle:"Referral Rewards and Incentives | Referral Factory",metaDescription:"Referral reward software for mid-market, enterprise, and multi-location teams that need flexible incentives, qualification rules, approvals, and scalable fulfilment.",hero:{eyebrow:__("Rewards"),titleLead:__("Design"),titleHighlight:__("reward operations"),titleTrail:__("that are easy to run and easy to trust. Over 200 types of rewards."),description:__("Referral Factory is referral marketing software for mid-market companies, enterprise teams and multi-location businesses that need to launch, manage and scale customer referral programs. Connect reward strategy, qualification, approvals and fulfilment in one operating flow."),timingNote:__("The strongest rewards are tied to a real milestone, explained clearly, and issued without manual ambiguity."),buttons:[{href:route("auth.register"),label:__("Start Free Trial"),tone:"primary"},{href:"/demo",label:__("Book Demo"),tone:"secondary"},{href:"/integrations",label:__("See Integration Paths"),tone:"ghost"}],sideCards:[{value:__("Cash"),label:__("Strongest default in many markets"),description:__("Cash works because it is simple, immediate, and easy for both sides to understand without explanation."),tone:"dark"},{value:__("Choice"),label:__("Flexible fulfilment options"),description:__("Use credits, coupons, gift cards, discounts, cash, or custom rewards when that fits the economics better."),tone:"white"}],visual:{accentLabel:__("Reward operations"),image:"/assets/images/webp/web/unique/reward-girl.
1webp",alt:"Referral rewards"}},whyItMatters:{eyebrow:__("Why reward design matters"),pill:__("Commercial discipline"),title:__("The reward strategy changes participation, conversion, and margin"),description:l.jsxs(l.Fragment,{children:[__("Rewards do more than motivate sharing. They shape how easy the offer is to explain, when the referred person responds, and whether the team can run the program without operational drag. Use the guide to "),l.jsx("a",{href:"/learn/calculating-the-value-of-a-referral-reward",className:"font-semibold text-[#1D81D9] underline underline-offset-4",children:"calculate the value of a referral reward"}),__(" before you lock in an incentive amount.")]}),items:[{title:__("A clear reward increases participation"),description:__("Customers share more when they instantly understand what they get and when they get it."),image:"/assets/images/webp/web/rewards/cash.webp"},{title:__("A good friend-facing offer improves conversion"),description:__("Reward mechanics work best when the referred person also has a reason to act, not just the referrer."),image:"/assets/images/webp/web/rewards/coupon.webp"},{title:__("A clean trigger protects margin"),description:__("If the reward only fires after a real commercial milestone, the business can scale the program with much more confidence."),image:"/assets/images/webp/web/rewards/stripe.webp"}],bullets:[__("The reward should be easy to explain in one sentence."),__("The trigger should match the business milestone that already matters internally."),__("Fulfilment should be fast enough that people trust the program after they participate.")]},rewardTypes:{eyebrow:__("Reward types"),pill:__("Flexible fulfilment"),title:__("Choose the reward type that fits your economics and audience"),description:__("The best reward is the one the audience values and the business can operate confidently. There is no universal default, but there is usually a practical best fit for each program."),items:[{title:__("Cash rewards"),description:__("Use fixed payouts or commissions when simplicity and universal appeal matter more than brand-specific reward mechanics."),image:"/assets/images/webp/web/rewards/cash.webp"},{title:__("Gift cards and vouchers"),description:__("Useful when you want broad consumer appeal with easier fulfilment options across different regions."),image:"/assets/images/webp/web/rewards/gift.webp"},{title:__("PayPal"),description:__("Send cash-style referral rewards through PayPal when you want flexible fulfilment that customers already understand."),image:"/assets/images/svg/web/rewards/paypal-card.svg"},{title:__("Stripe credits and billing incentives"),description:__("Useful for subscription or ecommerce businesses that want the reward to flow directly through the payments layer."),image:"/assets/images/webp/web/rewards/stripe.webp"},{title:__("Discounts, freebies, and swag"),description:__("Useful when brand value, perceived exclusivity, or product love matters more than direct cash."),image:"/assets/images/webp/web/rewards/discount.webp"},{title:__("Custom rewards like points or tokens"),description:__("Useful when the business already runs a points, loyalty, or token system that customers understand naturally."),image:"/assets/images/webp/web/rewards/custom.webp"}]},workflow:{eyebrow:__("How reward operations should run"),title:__("A practical reward flow for live referral programs"),description:__("The reward system should feel simple to the customer and disciplined to the team operating it."),steps:[{title:__("Pick the reward and the friend-facing offer"),description:__("Decide what the referrer gets and what the referred person sees before you worry about fulfilment mechanics."),image:"/assets/images/webp/web/rewards/cash.webp"},{title:__("Define the exact qualification milestone"),description:__("Tie the reward to the moment that actually matters commercially, not the earliest possible action."),image:"/assets/images/webp/web/rewards/stripe.webp"},{title:__("Choose whether rewards are automatic or reviewed"),description:__("Some programs can issue instantly, while others should pass through an approval step first."),image:"/assets/images/webp/web/rewards/custom.webp"},{title:__("Fulfil quickly once the rule is satisfied"),description:__("Speed matters because people trust the program more when the reward arrives without confusion or delay."),image:"/assets/images/webp/web/unique/reward-couple.webp"}]},strategy:{eyebrow:__("Strategy"),title:__("Three reward decisions matter more than the rest"),description:__("Most referral reward problems come from weak strategic choices, not from fulfilment tooling. Lock these decisions down early."),items:[{title:__("Single-sided vs double-sided"),description:__("Double-sided rewards often improve participation because both people see value, but the economics need to support it. Choose the mechanic intentionally, not by habit.")},{title:__("Generic value vs branded value"),description:__("Cash is easy to understand, while credits, product rewards, and discounts can align better with brand or margin. Pick the tradeoff you actually want.")},{title:__("Instant fulfilment vs reviewed fulfilment"),description:__("Some programs should issue automatically. Others need review to protect margins or prevent low-quality referrals from triggering rewards too early.")}]}
1,checklist:c({name:"your reward system",milestone:"the commercial event that truly justifies the reward",checklistOwner:"growth, ops, or program manager"}),finalCta:{eyebrow:__("Next step"),title:__("Run reward mechanics the team can actually scale"),description:__("The strongest referral programs do not just have appealing rewards. They have reward operations that are easy to explain, easy to trigger, and easy to fulfil without constant manual intervention."),image:"/assets/images/webp/web/unique/reward-couple.webp",imageAlt:"Referral rewards",features:[{title:__("Stronger participation"),description:__("Use a reward people understand instantly instead of making them decode the value proposition.")},{title:__("Cleaner triggers"),description:__("Tie rewards to a real milestone so qualification stays consistent and defensible.")},{title:__("Less admin"),description:__("Keep fulfilment connected to the live referral workflow instead of relying on spreadsheets and manual follow-up.")}]},faq:{eyebrow:__("FAQ"),title:__("Questions teams ask when they redesign rewards"),description:__("Reward mechanics affect acquisition, operations, and margin at the same time. These are the questions that usually matter most before launch."),items:[t("What reward type performs best?","There is no universal answer, but cash is often the cleanest default because it is easy to understand. The better question is which reward your audience values and your business can fulfil confidently."),t("Should we offer double-sided rewards?","Often yes, if the economics support it. Double-sided rewards can make the program easier to share because the referred person also gets an obvious benefit."),t("When should rewards trigger?","Trigger rewards after the commercial milestone that matters to the business, not at the earliest possible lead event. That keeps margin, reporting, and trust aligned."),t("Should rewards issue automatically?","Use automatic fulfilment when the qualifying event is reliable and low-risk. Use review when the program needs more control, fraud checking, or margin protection.")]}},W={integrations:P,rewards:F,hubspot:v,stripe:k,salesforce:q,intercom:S,monday:I,zoho:R,zapier:C,pipedrive:T,servicetitan:D,make:M,webhookApi:U};
1export{W as acquisitionPageContent,v as hubspotPageContent,P as integrationsPageContent,S as intercomPageContent,M as makePageContent,I as mondayPageContent,T as pipedrivePageContent,F as rewardsPageContent,q as salesforcePageContent,D as serviceTitanPageContent,k as stripePageContent,U as webhookApiPageContent,C as zapierPageContent,R as zohoPageContent};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.