n8n HubSpot Integration: Automate Deal Stages for Free

An n8n HubSpot integration connects n8n's workflow automation engine to HubSpot's CRM, letting you trigger automated actions (Slack alerts, task creation, follow-up emails) when deal stages change, without a paid HubSpot Professional plan. It replaces the native workflow builder that HubSpot locks behind its paid tiers.

HubSpot Professional tiers, the plans that include native workflow automation, start at $100/seat/month (monthly billing; $90/seat on annual) for Sales Hub and climb to $890/month for Marketing Hub Professional (per HubSpot's pricing page as of April 2026). For a small business running 20-50 active deals, that's a steep price when all you need is "when deal moves to X, do Y." With n8n, you can build that same trigger-action workflow on HubSpot Free, paying nothing for the workflow layer.

So here's the tradeoff: $100-$890/month to HubSpot for native automation, or a few hours of setup in n8n to build the same thing yourself. At Rain Automation, we've built 40+ n8n-to-HubSpot workflows for small business consulting clients since 2024, and every one of them runs on HubSpot Free or Starter (based on Rain Automation consulting engagements, 2024-2026).

Disclosure: Some links in this post are affiliate links. If you sign up through them, Rain Automation may earn a commission at no extra cost to you.

What HubSpot Free Does (and Does Not) Automate

HubSpot's Free CRM gives you contact management, deal tracking, and basic reporting, but it does not include workflow automation. Any trigger-based action ("when deal moves to X, do Y") requires a Professional-tier plan, starting at $100/seat/month for Sales Hub (HubSpot pricing).

That pricing makes sense for enterprise teams managing thousands of deals. For a small business running 20-50 active deals, it's hard to justify. The n8n Community and HubSpot Community forums are full of people asking the same question: "I just want HubSpot to send a Slack message when a deal stage changes. Why do I need a paid plan for that?"

n8n is the answer. It sits between HubSpot and your other tools, listening for deal events and firing downstream actions. The workflow we're building in this guide does exactly what HubSpot Professional's workflow builder does, and it runs on n8n Cloud or a free self-hosted instance. If you want a clear picture of exactly which HubSpot plan is required for each alert type before you start building, this breakdown maps the limitations by tier.

If you haven't connected n8n to HubSpot at all yet, start with our n8n HubSpot integration tutorial for lead capture. That guide covers getting contacts into HubSpot. This one picks up where it left off: automating what happens after leads are already in your pipeline.

One thing to nail down before you start: which events should actually trigger a notification. It is easy to wire up a stage-change webhook and miss the three other trigger classes that drive most pipeline failures. See a breakdown of the notification trigger types most HubSpot teams overlook for the full picture.

What You Need Before Setting Up Your n8n HubSpot Integration

You need four things to build this workflow: an n8n instance, a HubSpot account (Free tier works), a HubSpot Developer App, and about 45 minutes. No paid plans required on either side.

Here's your checklist:

• n8n instance (self-hosted or n8n Cloud). Cloud is simpler because your webhook URL is publicly accessible out of the box. Self-hosted requires a reverse proxy or tunnel like ngrok for the HubSpot Trigger to reach your instance.
• HubSpot account on any tier, including Free. You need at least one deal pipeline with stages defined.
• HubSpot Developer App created through the Developer Platform in your HubSpot account. As of September 2025, HubSpot unified the developer experience into your main portal (more on this in the next section). This is different from a Private App.
• Basic n8n familiarity. If you've built one workflow before, you'll be fine. If n8n is brand new, our n8n CRM integration tutorial covers the fundamentals.

One thing worth noting: the n8n Community forums have multiple threads from users who set up a Private App in their regular HubSpot portal, added scopes, and still got authorization failures. The fix isn't adding more scopes to the Private App. The fix is using the right app type entirely. That's a Developer App, not a Private App.

The HubSpot n8n Decision Stack: Trigger vs Action vs Direct API

The HubSpot Trigger node listens for events in real time (deal stage changed, contact created). The standard HubSpot node performs actions on demand (create contact, update deal). They serve different purposes and require different authentication setups.

Every other n8n HubSpot tutorial in the top search results tells you to create a Private App in your HubSpot portal and copy the API token into n8n. That approach works for the standard HubSpot node but fails entirely for the Trigger node. The Trigger node requires a Developer App, a fundamentally different app type, and no tutorial in the current top-10 search results explains this distinction clearly. That confusion is the root cause of most setup failures we see in the community forums.

This distinction trips up more people than any other part of the n8n HubSpot integration. Here's how to decide which approach to use: if your workflow starts with "when something changes in HubSpot," you need the Trigger node and a Developer App. If your workflow ends with "push this data to HubSpot," you need the standard node and a Private App token. If you need bulk operations or an endpoint the built-in nodes don't cover, use the HTTP Request node.

Feature	HubSpot Trigger Node	Standard HubSpot Node	HTTP Request Node (HubSpot API)
Purpose	Listen for CRM events in real time	Perform CRM actions (CRUD)	Any HubSpot API endpoint
Direction	HubSpot pushes to n8n	n8n pulls/pushes to HubSpot	n8n pulls/pushes to HubSpot
Auth method required	Developer App (OAuth or app token)	Private App token or OAuth	Private App token or OAuth
HubSpot plan needed	Free (any tier)	Free (any tier)	Free (any tier)
n8n plan needed	Any (Cloud or self-hosted)	Any	Any
Use case	"When a deal moves to Contract Sent, do X"	"Create a contact with these fields"	Bulk operations, endpoints not covered by nodes
Webhook required	Yes (auto-registered by n8n)	No	No
Setup complexity	Medium (Developer App required)	Low (Private App token)	High (manual API calls)

The community threads on HubSpot and n8n are filled with users who tried to use a Private App token with the Trigger node. It won't work. The Trigger node registers a webhook subscription through HubSpot's developer API, which requires a Developer App, not a Private App.

For a deeper look at how n8n connects with CRMs beyond HubSpot, check out our guide to integrating your CRM with n8n and Make.

n8n vs Zapier vs Make for HubSpot Integration

n8n is the best option for teams that want full control over HubSpot deal automation without per-task pricing. Zapier is simpler but charges per execution. Make sits in the middle with visual flows and moderate pricing.

If you're evaluating automation tools for HubSpot, here's how the three most popular platforms compare for deal-stage workflows specifically:

Feature	n8n	Zapier	Make (Integromat)
HubSpot Free CRM support	Yes	Yes	Yes
Deal stage trigger	HubSpot Trigger node (webhook-based)	HubSpot trigger (polling, 1-15 min delay)	HubSpot module (webhook or polling)
Trigger latency	Near real-time (webhook push)	1-15 minutes on most plans	Near real-time with instant triggers
Self-hosted option	Yes (free, unlimited)	No	No
Free tier	Self-hosted: unlimited; Cloud: 14-day trial	Free: 100 tasks/month	Free: 1,000 ops/month
Paid starting price	EUR 24/month (~$26 USD) (Cloud Starter)	$29.99/mo (Starter)	$9/mo (Core)
Per-execution pricing	No (plan-based)	Yes (task-based)	Yes (operation-based)
Open source	Yes (fair-code license)	No	No
Custom code nodes	Yes (JavaScript, Python)	Yes (Code by Zapier, limited)	Yes (JavaScript, limited)
HubSpot webhook limit workaround	Switch node routing (covered in this guide)	Not needed (uses polling)	Router module

For small businesses that want deal-stage automation on HubSpot Free without per-execution costs, n8n's self-hosted option is the clear winner. Zapier is the easiest to set up but the per-task pricing adds up fast once you're processing more than a handful of deals per day. Make offers a middle ground with lower per-operation costs than Zapier but less flexibility than n8n for complex routing. For a broader comparison, see our n8n vs Make for small business automation guide.

Step 1: Create a HubSpot Developer App

You need a Developer App (not a Private App) to use the HubSpot Trigger node in n8n. Since September 2025, HubSpot's Developer Platform is integrated directly into your main portal account, so you no longer need a separate developer account at a different URL.

Here's the background. Before September 2025, HubSpot maintained a separate developer portal at developers.hubspot.com where you'd create a standalone developer account. That's changed. HubSpot's unified Developer Platform now lives inside your regular HubSpot account. You access developer tools through your existing portal login.

As of April 2026, the steps are:

1. Log into your regular HubSpot account at app.hubspot.com.
2. In the top navigation, go to Settings (gear icon), then find Integrations > Developer Platform (or search for "Developer Platform" in the settings search bar). If you don't see this option, visit developers.hubspot.com/get-started to enable developer tools on your account.
3. Click Create app (or Manage apps if you've already created one).
4. Name it something recognizable ("n8n Deal Automation" works).
5. Go to the Auth tab in your new app's settings.
6. Under Scopes, grant the following:
   • crm.objects.deals.read (required to receive deal events)
   • crm.schemas.deals.read (required for deal property metadata)
   • oauth (if using OAuth flow)
7. Copy the App ID and Client Secret from the Auth tab. You'll need these in n8n.
8. Under Webhooks in the app settings, you'll see a subscriptions panel. n8n handles this registration automatically when you activate the workflow, but this is where you can verify it happened.

The key distinction remains the same as it always has been: Private Apps give you an API token for server-to-server calls. Developer Apps give you webhook subscription capabilities. The Trigger node needs the latter. The HubSpot Developer Documentation explains this distinction in detail.

I built a deal-stage automation for a five-person SaaS sales team last year that shows exactly why this matters. They came to us after three hours of troubleshooting a "wrong scopes" error. They had added every available scope to their Private App in the regular HubSpot portal. The problem wasn't scopes. The problem was that Private Apps can't register webhook subscriptions at all. Five minutes after switching to a Developer App, the trigger fired. Now their workflow pushes Slack alerts to their sales channel within 8 seconds of a deal stage change (based on Rain Automation consulting engagement, 2025). Before that, they were on Zapier's polling plan, where deal notifications arrived anywhere from 5 to 15 minutes late.

Step 2: Set Up the HubSpot Trigger Node in n8n

In n8n, add a HubSpot Trigger node to your canvas, connect it to your Developer App credentials, and configure it to listen for deal property changes on the dealstage property. When activated, n8n automatically registers the webhook with HubSpot.

Here's the node configuration, field by field:

1. Open n8n and create a new workflow. Add a HubSpot Trigger node (search for it in the node panel; it's under Trigger nodes, separate from the regular HubSpot node).
2. Credentials: Click the credential dropdown and select "Create new." Choose "HubSpot Developer API" as the credential type. Enter the App ID and Client Secret from your Developer App (Step 1 above). If you're using n8n Cloud, the OAuth redirect URL is handled automatically. Self-hosted users need to set the redirect URL to https://your-n8n-domain.com/rest/oauth2-credential/callback per the n8n HubSpot credentials docs.
3. Event: Select Deal as the object type.
4. Event type: Select Property Changed.
5. Property: Enter dealstage in the property filter field. This tells HubSpot to only send webhook events when the deal stage changes, not when other deal properties (like amount or close date) are modified.
6. Save and activate the workflow. When you activate it, n8n sends an API call to HubSpot that registers your webhook URL. You can verify this by going back to your Developer App in HubSpot > Webhooks > Subscriptions, where you'll see a new subscription listed.

The n8n HubSpot Trigger node documentation covers additional event types beyond deal stage changes (contact creation, company updates, etc.). But for this workflow, dealstage property changes are what we want.

One important difference to understand: the Trigger node is event-driven. HubSpot pushes data to n8n when something happens. The standard HubSpot node is action-driven, meaning n8n pulls data from or pushes data to HubSpot on a schedule or when triggered by another node. Both have their place. For the n8n send email node tutorial we published earlier, the standard node works fine because you're initiating the action. But for "react when something changes in HubSpot," the Trigger node is what you need.

Step 3: Handle the One-Webhook Limitation With a Switch Node

HubSpot only allows one registered webhook URL per Developer App. If you need to listen for multiple event types (deal stage changes, contact creation, company updates), you route them all through a single HubSpot Trigger node and use an n8n Switch node to fan out by event type.

This limitation is documented in the HubSpot Developer docs on webhooks but almost never mentioned in tutorials. It catches people off guard when they try to add a second HubSpot Trigger node for a different event type and their first trigger stops working. The second subscription overwrites the first.

Here's the workaround:

1. Keep one HubSpot Trigger node as your single entry point. Configure it to listen broadly (you can subscribe to multiple event types within the same Trigger node by adding multiple subscriptions in the Trigger node's settings, or you can set it at the broadest useful level).
2. Add a Switch node immediately after the Trigger node.
3. Configure the Switch node with routing rules based on the incoming event payload.

The Switch node configuration:

• Mode: Rules
• Data Type: String
• Value: {{ $json.propertyName }} (this is the property that changed)
• Rule 1: Equal to dealstage (routes to your deal stage automation branch)
• Rule 2: Equal to email (routes to contact email change branch, if needed)
• Fallback output: Routes unmatched events to a logging node or trash

For deal stage routing specifically, you can add a second Switch node after the first one to route by the actual stage value:

• Value: {{ $json.propertyValue }}
• Rule 1: Equal to contractsent
• Rule 2: Equal to closedwon
• Rule 3: Equal to closedlost

Here are the default deal stage IDs for a standard HubSpot Sales pipeline:

Stage Name	Stage ID	Pipeline Position
Appointment Scheduled	appointmentscheduled	1
Qualified to Buy	qualifiedtobuy	2
Presentation Scheduled	presentationscheduled	3
Decision Maker Bought In	decisionmakerboughtin	4
Contract Sent	contractsent	5
Closed Won	closedwon	6
Closed Lost	closedlost	7

To find your actual stage IDs (if you've customized your pipeline), go to HubSpot > Settings > Objects > Deals > Pipelines, click on a stage, and look at the internal value in the URL or use the HubSpot Deals API endpoint GET /crm/v3/pipelines/deals to list them.

Now your single webhook feeds into a routing layer that can handle any event type HubSpot sends. Want to learn how other CRM tools handle similar pipeline automation? Our guide on automating your deal pipeline covers the strategy side.

Here's the bottom line on what makes this setup different from every other n8n HubSpot tutorial. The Trigger node requires a Developer App (not a Private App), which is the single biggest source of "wrong scopes" errors. HubSpot limits you to one webhook URL per app, so you route through a single Trigger into a Switch node instead of creating multiple triggers. The Decision Stack table above tells you which node type to use for which job. And the cost to run all of this on n8n self-hosted is $0, compared to $100-$890/month for HubSpot's native workflow builder. That combination of correct auth setup, one-webhook routing, and zero automation cost is what this guide delivers.

Step 4: Build the Downstream Actions

Each branch of your Switch node connects to a specific action: Slack alert for Contract Sent, HubSpot task creation for Closed Won, follow-up email for Closed Lost. These three cover the highest-value automations for a small sales team.

Here's each one with the exact node configuration.

Action 1: Slack Notification When Deal Moves to "Contract Sent"

This is the most-requested automation in the HubSpot community threads. When a deal hits Contract Sent, your team needs to know immediately.

• Node type: HTTP Request
• Method: POST
• URL: Your Slack incoming webhook URL (create one at api.slack.com > Your Apps > Incoming Webhooks)
• Body (JSON):

{
  "text": "Deal moved to Contract Sent: {{ $json.objectId }}\nDeal ID: {{ $json.objectId }}\nChanged by: {{ $json.changeSource }}"
}

You can enrich this by adding a HubSpot node before the HTTP Request to fetch the deal name and contact details using the objectId from the trigger payload. Add a HubSpot node (standard, not Trigger) with action "Get a Deal" and pass {{ $json.objectId }} as the Deal ID.

Action 2: Create a HubSpot Task When Deal Moves to "Closed Won"

When a deal closes, someone needs to handle onboarding. Instead of hoping your team remembers, create the task automatically.

• Node type: HubSpot (standard node)
• Resource: Task
• Operation: Create
• Task body: "Onboarding follow-up for deal {{ $json.objectId }}. Schedule kickoff call within 48 hours."
• Due date: Set to 2 days from now using an expression: {{ $now.plus(2, 'days').toISO() }}
• Associated object: Use the deal's objectId to link the task to the deal record.

This pairs well with an automated follow-up sequence if you want to build out a full post-close workflow.

Action 3: Send Follow-Up Email When Deal Moves to "Closed Lost"

Lost deals aren't dead. A well-timed re-engagement email sent 24 hours after a deal goes Closed Lost can reopen conversations.

• Node type: Wait (set to 24 hours)
• Followed by Send Email node (SMTP)
• To address: Pull from the associated contact using a HubSpot node lookup
• Subject: "Quick question about [deal name]"
• Body: A brief, non-pushy check-in asking what changed and whether there's anything you can help with down the road.

For more on configuring n8n's email capabilities, see our n8n Send Email node tutorial.

These three actions cover the most common post-pipeline automations. But the pattern is extensible. Want to automate CRM task creation for your sales team? Add another Switch branch. Need to update a Google Sheet with closed deal data? Add an automated reporting node. The Switch node pattern scales to as many branches as your sales process needs. If you want ready-made timing logic for stale-deal thresholds and escalation alerts across every pipeline stage, Rain Automation's breakdown of n8n deal pipeline automation covers those patterns end to end.

Error Handling: What Happens When HubSpot Sends a Bad Payload

Add an Error Trigger node to catch failed executions, log the payload to a Google Sheet or email, and alert your team. The most common failure is a "wrong scopes" error caused by using Private App credentials instead of Developer App credentials.

Here's how to set up error handling:

1. Add an Error Trigger node to your workflow (it's a separate trigger that fires when any node in the workflow fails).
2. Connect it to a Google Sheets node that logs: timestamp, error message, the raw JSON payload, and the node that failed.
3. Add a Send Email node after the Google Sheets node to alert you or your team when a failure occurs.

The three most common errors you'll encounter:

Error	Cause	Fix
"Authorization failed because the provided scopes are missing"	Using Private App credentials with the Trigger node	Switch to Developer App credentials (HubSpot community thread)
Webhook not receiving events	n8n instance not publicly accessible	Use n8n Cloud or configure reverse proxy/ngrok for self-hosted
Events received but propertyValue is null	Subscribed to wrong property or event type	Verify dealstage is set as the property filter in the Trigger node

In my experience building these integrations for consulting clients, the scopes error accounts for about 80% of first-time setup failures. The fix is always the same: Developer App, not portal Private App. If you've read this far, you already know that, so you're ahead of most people troubleshooting in the forums.

Testing Your n8n HubSpot Integration Workflow

You don't need to close a real deal to test this workflow. Manually move a test deal through your pipeline stages in HubSpot and watch the n8n execution log for each trigger event.

Step-by-step testing process:

1. Create a test deal in HubSpot. Name it something obvious like "TEST - n8n Automation" so you can find it later.
2. Activate your n8n workflow if it isn't already running.
3. Move the test deal from its current stage to "Contract Sent" in HubSpot.
4. Check the n8n execution log (click "Executions" in the left sidebar). You should see a new execution within 5-30 seconds.
5. Click into the execution and inspect each node's output. Verify the Switch node routed to the correct branch and the downstream action (Slack message, task, or email) completed successfully.
6. Move the test deal to "Closed Won" and then "Closed Lost" to test the other branches.
7. Check your Slack channel for the notification. Check HubSpot for the created task. Check your email inbox for the follow-up email.

If the trigger doesn't fire, check these in order:

• Is the workflow active in n8n? (Green toggle in the top-right corner)
• Is your Developer App's webhook subscription showing as "Active" in HubSpot's developer settings?
• For self-hosted n8n: can HubSpot reach your webhook URL? Try hitting it manually from your browser.
• Did you subscribe to Deal events with the dealstage property filter?

Once testing passes, delete your test deal and the workflow is production-ready. For teams tracking HubSpot workflow automation examples, this deal-stage trigger is the foundation that most other automations build on.

n8n HubSpot Integration Cost Comparison

Building deal stage automation in n8n costs $0-EUR 24/month (~$26 USD)nth depending on your setup, compared to $100-$890/month for a HubSpot Professional plan's equivalent native workflow feature.

Here's the breakdown:

Approach	Monthly Cost	What You Get
HubSpot Sales Hub Professional	$100/seat/mo (annual billing, HubSpot pricing)	Native workflow builder, email sequences, deal automation, reporting
HubSpot Marketing Hub Professional	$890/mo for 3 seats (annual, HubSpot pricing)	Workflows, email marketing, 2,000 marketing contacts, omnichannel automation
n8n Cloud Starter	EUR 24/month (~$26 USD) (n8n pricing)	2,500 executions, 5 active workflows, hosted webhook URL
n8n Cloud Trial	$0 for 14 days	Full feature access during trial period (not a permanent free plan)
n8n Self-Hosted	$0/mo	Unlimited workflows and executions, requires your own server infrastructure

The tradeoff is real. HubSpot Professional gives you a polished drag-and-drop builder, deeper CRM integrations, and support. But if your primary need is "trigger action X when deal reaches stage Y," n8n covers that use case at a fraction of the cost. Our own Rain Automation n8n instance runs approximately 200 HubSpot-related workflow executions per month across internal operations and client demo environments, at zero additional HubSpot cost (based on Rain Automation n8n instance metrics, Q1 2026).

For small businesses running lean operations, this is a practical path. And it pairs well with the broader CRM automation strategies we've covered elsewhere on the blog.

Frequently Asked Questions

Does this n8n HubSpot integration work with HubSpot Free?

Yes. The HubSpot Trigger node and all standard CRM API endpoints work with HubSpot's Free tier. You don't need a paid HubSpot plan to receive webhook events for deal stage changes. HubSpot's paid Professional tiers only become necessary if you want to use HubSpot's built-in workflow builder. With n8n handling the automation layer, Free is enough.

Why does my HubSpot Trigger say "wrong scopes" in n8n?

This error almost always means you're using a Private App token created in your regular HubSpot portal. The Trigger node requires credentials from a Developer App created through HubSpot's Developer Platform. Developer Apps can register webhook subscriptions; Private Apps cannot. Switch your n8n credential to use Developer App authentication and the error resolves. The HubSpot community thread on this issue confirms this fix.

Can I have multiple HubSpot triggers in the same n8n instance?

You can, but each one needs its own Developer App in HubSpot because of the one-webhook-per-app limitation. The better approach is to use a single Trigger node that receives all event types and route them with a Switch node. This uses one Developer App and one webhook URL, avoiding the overwrite problem where a second trigger silently kills the first.

What is the difference between the HubSpot node and the HubSpot Trigger node in n8n?

The HubSpot node is an action node: it creates, reads, updates, or deletes CRM records when triggered by another node in your workflow. The HubSpot Trigger node is an event listener: it starts a workflow when something changes in HubSpot (deal stage change, new contact, property update). Use the Trigger when you need "when X happens in HubSpot, do Y." Use the standard node when you need "take this data and push it to HubSpot." See the n8n HubSpot node docs and Trigger node docs for the full API reference.

Do I need a paid n8n plan for this workflow?

Not necessarily. Self-hosted n8n is free with unlimited workflows, though you need your own server. n8n Cloud offers a 14-day free trial to test the setup, and the EUR 24/month (~$26 USD)nth Starter plan covers most small business needs with 2,500 executions per month. If your deal volume is under 100 deals/month, the free self-hosted option handles it easily.

Where do I find my HubSpot deal stage IDs?

Go to HubSpot > Settings (gear icon) > Objects > Deals > Pipelines. Click on your pipeline, then click on individual stages to see their internal names. Alternatively, use the HubSpot Deals API: send a GET request to /crm/v3/pipelines/deals with your API token to get a JSON response listing all pipelines and their stage IDs.

What to Build Next

You now have a working n8n HubSpot integration that reacts to deal stage changes and fires real downstream actions. The next step is expanding the downstream branches or connecting additional tools.

Here are practical next steps:

• Add lead scoring logic before the Switch node to prioritize high-value deals. Our real estate lead scoring guide covers the approach (the pattern works for any industry, not just real estate).
• Enrich contacts as they flow in. If you're on HubSpot and want company and person data filled in automatically, see adding HubSpot Breeze Intelligence enrichment to your contact capture pipeline so your deal records are complete before sales ever touches them.
• Build a lead nurturing sequence for deals stuck in the middle of the pipeline. The automated lead nurturing guide walks through the sequence design.
• Connect your email marketing for Closed Lost re-engagement campaigns. Email marketing automation for small businesses covers the strategy.
• If you're handling IDX property inquiries from a real estate website, see the n8n workflow for IDX leads feeding into HubSpot, which applies this same deal-stage logic to real estate lead sources.

If you want someone to build this for you (or wire up a more complex multi-tool workflow), schedule a call with our team. We design custom n8n workflows for small businesses, and HubSpot deal automation is one of the most common requests we get.

Already have contacts flowing into HubSpot and need the lead capture side? Read our companion guide: n8n HubSpot Integration Tutorial: Connect Leads to Your CRM.

The information in this post is for educational purposes. Specific pricing, features, and API behavior may change. Verify current details on HubSpot's pricing page and n8n's documentation before making purchasing decisions.