Comparison

Make vs Zapier: Features, Pricing and Best Fit

Make vs Zapier: compare visual workflow building, integrations, routing, credits vs tasks, plan limits, and real automation costs.

Make logo

Make

Workflow Automation Software

4.5
Research-based
Features and capabilities4.8
Usability and implementation4.2
Pricing and value transparency4.4
Integrations, security and trust4.6
Best for
Operations specialists and technically comfortable marketers automating multi-app processes with branching logic, API calls and detailed data transformations.
Pricing
Free plan
Key features
Make AI Agents betaFull-text execution log search on ProAnnual pooled credits on Pro and TeamsConditional route filtersUnlimited active scenarios on Core and up
View Make
VS
Zapier logo

Zapier

Workflow Automation Software

4.5
Research-based
Features and capabilities4.8
Usability and implementation4.7
Pricing and value transparency3.8
Integrations, security and trust4.8
Best for
Marketers, sales operations and business teams connecting SaaS applications with no-code Zaps, lead-routing workflows and shared automation.
Pricing
Free plan
Key features
Enterprise app governanceSAML SSO and role controls on TeamFormatter field transformationsMulti-step workflows on paid plansScheduled and polling workflows
View Zapier
Make vs Zapier Toollers comparison featured image

Make and Zapier both connect business apps so an event in one system can start work in another. They share a real use case: automating repetitive steps across CRM, marketing, sales, finance, and operations tools.

Make emphasizes a visual scenario canvas with modules, routers, iterators, and detailed data mapping. Zapier emphasizes Zaps that connect triggers to actions, with Filters, Paths, and other tools for more complex logic.

The largest practical difference is how usage is counted. Make measures credits across executed modules, while Zapier generally bills successful action tasks. The same automation can therefore consume different units on the two platforms.

This comparison examines workflow building, app integrations, branching, usage metering, reliability, collaboration, and total costs. It is based on official product and support documentation, not a claimed hands-on benchmark.

Quick verdict

Quick verdict

Choose Make when you need a visual map of multi-route workflows, detailed record transformations, and granular control of modules. Budget for all metered module executions, including scheduled trigger checks. Choose Zapier when the main goal is to connect supported apps quickly, with simple Zaps and conditional Paths when needed. Its trigger checks and standard Filter, Paths, and Formatter steps generally do not use tasks; completed actions do. At the observed US monthly Make price selection, Core is $12, Pro $21, and Teams $38 for 10,000 credits. Zapier lists Professional from $19.99/month and Team from $69/month with annual billing. These are not equal usage bundles. Compare a real monthly run log before calling either cheaper.

Key takeaways

  • Both Make and Zapier automate app-to-app workflows, but their design models and billing units differ.
  • Make scenarios have visual routers, filters, iterators, aggregators, data stores, and error handlers.
  • Zapier Zaps use triggers, actions, Filters, Paths, Formatter, and optional loops or code.
  • Make Free currently lists 1,000 credits/month; Zapier Free lists 100 tasks/month and two-step Zaps.
  • Make generally charges one credit for each ordinary module operation, including scheduled trigger checks, although routers and filters do not use credits.
  • Zapier generally counts completed action steps and excludes polling triggers, Filters, Paths, Formatter, and several built-in tools.
  • Make AI modules and code may use special credit rates; Zapier AI, MCP, code, and SDK activity can have different task rates or upcoming changes.
  • Make Core, Pro, and Teams entry prices cannot be compared directly with Zapier Professional and Team without matching usage tiers, billing cycles, and seats.
  • Shortlist the required exact app actions and run a realistic sample with failures, filters, and peak volume before choosing.

Make vs Zapier at a glance

AreaMakeZapier
Common purposeAutomate events and actions across applicationsAutomate events and actions across applications
Workflow objectVisual scenarioZap workflow
Builder styleCanvas connecting multiple modules and routesTrigger and action sequence with Paths for branching
BranchingRouters and filtersFilters and Paths
Data reshapingMapping, iterators, aggregators, data storesFormatter, Looping, Tables, Code and app actions
Usage unitCredits, usually per ordinary module operationTasks, generally per successful action
Idle pollingScheduled trigger checks generally consume creditsTrigger polling does not consume tasks
Routers or PathsRouters and filters do not consume credits, downstream modules canFilter and Paths steps do not count as tasks, downstream actions can
Free allowance1,000 credits per month100 tasks per month
Reference paid priceCore $12, Pro $21, Teams $38 monthly at the 10k-credit displayProfessional from $19.99 and Team from $69 monthly equivalent, annual billing
CollaborationTeams tier has team roles and shared scenario templatesTeam tier has up to 25 seats, shared Zaps and app connections
App selectionMake advertises 3,500+ apps on pricing pageZapier advertises 9,000+ apps in its ecosystem
Extra usageExtra credit packs or plan upgrade; auto-purchase available on eligible tiersPaid tiers may use pay-per-task billing or larger task tiers
Best first evaluationComplex, branching, transformation-heavy workflowsStraightforward cross-app actions and quick setup

Published app counts are vendor-reported and can change. More catalog entries do not necessarily mean that a particular app supports the trigger, update, lookup, or webhook action your business requires.

The paid prices above use different plan selections and payment terms. They are reference points for planning, not a controlled price-per-automation comparison.

Workflow building: scenarios vs Zaps

Make visual scenario builder

Make calls a workflow a scenario. You connect modules on a canvas and map data as it moves between apps, searches, filters, and transformations.

A scenario can watch a CRM for a lead, search a spreadsheet for existing records, update the correct row, and route different lead types to separate destinations.

Routers make multiple branches visible at once. This helps when a process has approval rules, region-specific actions, or several error-handling routes.

Modules can expose input bundles and output bundles. Inspecting those intermediate records helps a technical operator understand why a specific item did or did not reach its destination.

The canvas is flexible, but a large scenario can become difficult to maintain if it combines many unrelated processes. Naming, version control, and clear ownership still matter.

Zapier Zap builder

A Zap begins with a trigger and continues through actions. For a standard lead workflow, users can select a CRM trigger, map fields, add an email or spreadsheet action, and turn the Zap on.

Zapier includes built-in steps for formatting values, filtering records, and branching. Its Professional plan unlocks multi-step Zaps and premium app connections.

This design can be easier to hand to a nontechnical employee when the automation is linear. The employee can usually read the trigger and subsequent actions from top to bottom.

When the workflow needs several conditional outcomes, Zapier Paths group the alternatives. The sequence remains understandable, but extensive nesting deserves the same documentation as any other automation logic.

Zapier also offers Tables, Forms, and AI-oriented capabilities. Those products can extend a workflow, but should be evaluated as separate components with their own usage rules.

Practical builder example

Consider a contact form that sends prospects to a CRM, creates a sales task for qualified leads, and alerts support when an existing customer asks for help.

Make can represent this as a single visible scenario with filters and a router. Zapier can use Paths to direct the form response into the correct action sequence.

The right test is not whether both can draw the workflow. Compare how quickly an operator can fix a missing field, update an app connection, and replay a failed record.

Integrations and connector depth

Make app connectors

Make advertises thousands of app integrations. Its module-level builder can mix an app trigger with a search, a data transformation, and an action in another platform.

Make also supports HTTP/API modules and custom application connections. This can be useful when a business system offers an API but lacks the exact prebuilt action you need.

Some enterprise app connectors belong to higher service tiers. Check the exact connector and action against the plan, especially for finance, HR, and large enterprise software.

Zapier app connectors

Zapier advertises a larger integration catalog. Popular marketing, CRM, communication, commerce, and productivity apps usually have direct Zap integrations.

Paid Zapier plans include access to premium apps and webhooks. In the Free tier, a supported app might still be unavailable in the exact way required for an automation.

A connector can support creating a record without supporting the update or lookup you need. Read the list of available triggers and actions before committing to either service.

How to test integration quality

  • Confirm the required trigger and destination action exist for both tools.
  • Check whether a search or lookup module returns the expected unique record.
  • Test attachment handling, field mapping, API limits, and required scopes.
  • Disconnect the source app and confirm alerts and reconnection behavior.
  • Verify the same record is not created twice after a retry.

Native integration counts are less useful than these checks. A single missing search step can force a custom API call or a second workflow, changing both maintenance and usage costs.

Branching, filtering, and data transformation

Make routers and filters

Make Routers split data into routes. Each route can have filters that allow only matching bundles to proceed to its modules.

The router module and filters do not consume credits. The ordinary action modules executed after the router generally do consume credits, often once for every bundle they process.

Make also offers iterators that split arrays into bundles and aggregators that join data together. Those transformation modules can be billable even when no external app is updated.

A search module may run once and return many bundles. Subsequent actions may run for every returned bundle, so the total credit consumption can rise sharply.

This makes Make expressive for processes such as processing invoice line items or multiple order products. It also makes bundle counts an essential part of cost estimation.

Zapier Paths and Filters

Zapier Filters can stop a run that fails a condition. Paths allow different actions depending on the record, such as sending enterprise leads to an account manager.

Zapier says standard Filters, Paths, and Formatter steps do not use tasks. Successful action steps inside a running branch generally do.

Paths are not a promise that every branch runs simultaneously. Zapier documents sequential path execution, with special considerations for delays, looping, and nested branches.

A branch that does not run does not consume tasks for its skipped actions. This is useful when many incoming records are filtered out before any paid action.

Advanced features depend on plan eligibility. Do not infer that Free Zaps include the same multi-step Paths and premium-app capabilities as Professional.

Which branching model wins?

Make is a strong candidate for complex conditional routing and record transformation when a team values seeing the full process on one canvas.

Zapier is a strong candidate for clear business rules within established app connections, particularly when a majority of incoming events are filtered before paid actions.

These are editorial fit assessments. Neither is a measured speed or reliability victory without a controlled workflow test on the intended accounts.

Usage metering: credits vs tasks

How Make credits work

Make now uses credits as its billing unit. A standard non-AI module operation usually costs one credit, while specific AI and code features can use different rates.

A scheduled trigger generally costs a credit each time it checks the source, even when it finds no new item. Search modules also use credits, and action modules repeat for each processed bundle.

Routers, filters, and certain error-handling or scenario modules are exceptions. Their no-credit treatment does not remove the cost of the connected action modules.

Make documents additional dynamic credit rules for built-in AI features. Make Code has a separate execution-time rate, so an AI-heavy or code-heavy flow needs more than a simple module count.

An annual Make subscription changes how credits are allocated. Make says Core retains monthly allocations, while annual Pro and Teams packages provide a larger yearly credit pool.

How Zapier tasks work

Zapier generally counts one task when an ordinary action step completes successfully. A Zap that creates a contact and then sends a message uses two tasks for that successful run.

Trigger checks do not use tasks. Filters and Paths are excluded, and several built-in tools such as Formatter, Delay, and Looping have special no-task treatment.

Some actions have special rates. Zapier publishes different rules for AI by Zapier, Code, MCP, and other products, so a task estimate must identify which components are used.

Zapier has announced some additional charging changes effective December 1, 2026 for Next Gen Zaps and SDK activity. Those future rules should not be described as already effective on this review date.

On qualifying paid plans, pay-per-task billing can keep Zaps running after included usage is exhausted. If it is off, Zapier can hold new runs instead.

Why these units are not equivalent

One Make credit is not the same unit as one Zapier task. Make often counts trigger and intermediate module executions, while Zapier generally counts completed actions after its free trigger and logic steps.

A scenario with many searches and data operations can use more Make credits than Zapier tasks. A workflow with many external successful actions can be expensive under either model.

There is no universal credit-to-task conversion ratio. Model the exact actions, modules, runs, branching outcomes, and polling frequency.

Two worked usage examples

Example 1: 1,000 new leads from an instant trigger

Assume each lead starts a workflow, creates one CRM record, and sends one team notification. No AI processing, retries, or optional searches are used.

Under a simplified Make model, one trigger execution and two ordinary action modules cost about three credits per lead, or roughly 3,000 credits for 1,000 leads.

Under Zapier’s normal task model, the trigger is free and the two successful actions use two tasks per lead. That is approximately 2,000 tasks for 1,000 leads.

The figures are usage estimates, not an assertion that two vendor flows have identical implementations. Check whether the actual Make trigger is webhook-based and how it bills per incoming bundle.

Example 2: scheduled polling with no new data

Suppose an automation checks a source every 15 minutes for 30 days and finds no new records. There are 96 checks daily, or 2,880 checks over the period.

Make documents a credit for each scheduled trigger check, even with no results. An ordinary polling trigger could therefore use around 2,880 credits before any new records are processed.

Zapier says its polling triggers do not count toward task usage. The same idle period would use zero ordinary action tasks, subject to any other tools in the flow.

This example is important for low-volume workflows that poll frequently. It is not a guarantee that every Make connector polls or that every Zapier integration has an equivalent trigger.

What changes at larger volume?

Increase the first example to 5,000 qualifying leads and the simplified estimates become roughly 15,000 Make credits versus 10,000 Zapier tasks.

Neither figure equals a subscription price. The next step is to select the vendor tier that covers that usage, add seats, and model how the account handles overages.

If every lead also updates a second system, the estimate changes again. For Make, add the applicable module executions; for Zapier, add the successful paid action tasks.

Make pricing and plan limits

Free, Core, Pro, Teams, and Enterprise

Make’s pricing page lists Free with up to 1,000 credits per month, access to its visual builder, routers, filters, and a 15-minute minimum scheduling interval.

At the US monthly price selection for 10,000 credits, its indexed pricing card shows Core at $12/month, Pro at $21/month, and Teams at $38/month.

Core adds more scenario capacity, faster scheduling, and Make API access. Pro adds features such as priority execution, custom variables, and more capable log search.

Teams adds roles and shared scenario templates. Enterprise pricing is custom and includes additional security, administration, and enterprise integration features.

Those displayed prices are tied to a 10,000-credit selection. Other volumes and annual billing produce different charges, and available regional prices may vary.

Buying extra Make credits

Make supports extra credit packages and optional auto-purchasing on eligible paid plans. Its support documentation says extra credits carry a 25% premium versus included plan credits.

Usage also affects data-transfer and storage allowances. Make states that usage entitlements scale with purchased credits, so large file transfers deserve separate evaluation.

A workflow may stop when credits are exhausted and no additional credits are available. Webhooks can queue up to the account limit, but that is not a substitute for capacity planning.

Zapier pricing and plan limits

Free, Professional, Team, and Enterprise

Zapier lists Free at $0 with 100 tasks per month, unlimited Zaps, and two-step workflows. The free plan suits basic tests and a small number of recurring actions.

Zapier lists Professional from $19.99 per month when paid annually. Its published price guide uses an entry Professional allowance of 750 tasks per month.

The Team plan is listed from $69 per month on annual billing. It adds up to 25 users, shared app connections, shared Zaps and folders, roles, and SAML SSO.

Enterprise pricing requires a quote. It adds broader administrative controls, observability, governance, and tailored support features.

Task quantity is a separate tier selector. Professional and Team starting prices should not be taken as a price for 10,000 or more tasks without checking the task-volume selector.

Pay-per-task overages

Zapier can charge for usage beyond a paid plan’s included tasks when pay-per-task billing is enabled. The applicable task rate and monthly limit depend on the account and plan.

If overage billing is disabled, new runs can be held when the limit is reached. The buyer must choose between controlled spend and continuity of automation.

AI, MCP, SDK, and code steps deserve separate inspection. Vendor documentation describes special task rates and future effective dates that can change an otherwise simple budget.

Make vs Zapier total automation costs

ScenarioMake cost considerationZapier cost consideration
Free testing1,000 credits/month; idle polling may consume allowance100 tasks/month; trigger polls do not count
Solo paid startCore $12/month for 10k credits at observed monthly selectionProfessional from $19.99/month billed annually, with entry task tier
Advanced solo workflowPro $21/month for 10k credits at observed monthly selectionProfessional paid task-volume tier, not automatically the entry allotment
Team sharingTeams $38/month for 10k credits at observed monthly selectionTeam from $69/month billed annually, task tier selected separately
Burst or excess usageExtra credits or larger tier, with documented premium for extrasPay-per-task charges if enabled, otherwise held runs
AI or codeSpecific modules can have dynamic or execution-time credit ratesSpecific AI, MCP, code, and SDK features can have distinct task rates

These are published reference prices with different billing intervals and meters. A cheaper entry subscription can become more expensive when the volume tier, required features, and overages are included.

A practical cost worksheet

  • Count incoming events and distinguish instant triggers from polling.
  • List every Make module run, including searches, iterators, actions, and AI steps.
  • List every successful Zapier action, plus any special-rate AI or MCP step.
  • Estimate ordinary, peak, retry, and replay traffic separately.
  • Check the minimum plan that enables the specific connector, scheduling, or branch.
  • Include paid collaborators, transfer allowances, and potential overage charges.

Build the estimate for three months: average usage, busiest expected month, and an unexpected volume spike. Annual billing discounts only help if the plan fits all three cases.

A workflow that fails after the allowance is exhausted may cost more in lost leads or manual cleanup than the subscription price difference. Document what happens at the limit.

Reliability, debugging, and maintenance

Make scenario logs and error handling

Make allows users to inspect executions and records passed between modules. It also documents incomplete executions and error-handling routes for managing interrupted work.

For complex workflows, being able to identify the failed module and affected bundle can save time. The administrator still needs a policy for retries, duplicates, and alert ownership.

Zapier Zap history and replay

Zapier provides Zap history and management features, with access varying by tier. Paid plans add more tools for failed runs, versions, alerts, and replay-related workflows.

A Zap can trigger additional successful actions during a full replay, which may consume tasks again. Replays should therefore be included in operational and cost testing.

Common reliability tests

Run a duplicate lead, an expired app authorization, a missing required field, and a rate-limited API response through the planned automation.

Confirm whether failures stop a route, alert the owner, queue a retry, or create an incomplete record. Review whether reprocessing updates an existing record or creates a duplicate.

These are recommended tests for a future trial. Toollers did not execute those scenarios on paid Make or Zapier accounts for this article.

Team collaboration and administration

Make’s Teams tier is designed for staff who share scenario management. It adds team roles and shared scenario templates; enterprise arrangements add further controls.

Zapier Team supports shared Zaps, folders, app connections, and up to 25 users. Professional is a single-user plan, even if the workflows affect multiple colleagues.

When an automation is owned by one employee, an expired account or staff departure can interrupt work. Both platforms need appropriate service accounts, permissions, and owner review.

Before buying, test how another authorized teammate finds a failed run, updates a field mapping, and reconnects an app without exposing unnecessary access credentials.

For larger organizations, verify SSO, audit logs, regional requirements, data retention, and contractual support in the proposed tier. Do not assume enterprise controls are included in entry pricing.

Make pros and cons

Pros

  • Pros
  • Visual multi-branch scenarios are well suited to complex data flows; routers and filters do not consume credits; iterators, aggregators, and granular mappings support transformation-heavy work; API and error-handling options support advanced workflows

Cons

  • Cons
  • Frequent polling can consume credits without new records; intermediate processing modules can increase credit use; a large scenario requires disciplined maintenance; AI/code and extra-credit rules complicate forecasting; some governance and enterprise connectors require higher tiers

Zapier pros and cons

Pros

  • Pros
  • Clear trigger-to-action workflows are approachable; broad app catalog supports common business tools; standard polling triggers, Filters, Paths, and Formatter steps do not use tasks; Professional adds multi-step Zaps and premium apps; Team provides shared connections and roles

Cons

  • Cons
  • Successful action volume can make high-throughput plans expensive; Free is limited to two-step Zaps and 100 tasks; advanced team capabilities require Team or Enterprise; special AI/MCP/code task rates need care; overage billing or held runs require an explicit policy

Who should choose Make?

  • Operations teams designing multiple branches around one event.
  • Builders who need granular data mapping, iterators, and aggregators.
  • Teams that can monitor credits and optimize scheduling or webhooks.
  • Organizations willing to maintain visual scenarios with documented owners.

Make may be a poor first choice when a simple workflow is mostly idle polling and the operator has no time to monitor credits, retries, or changing app connections.

Who should choose Zapier?

  • Small businesses connecting familiar SaaS products with minimal setup.
  • Marketing and sales teams building mostly linear workflows.
  • Users whose triggers fire rarely but need frequent polling checks.
  • Teams that value shared Zaps and account administration on the right plan.

Zapier may be less attractive when many completed actions must run for every event and the required task tier becomes expensive compared with an optimized Make scenario.

Expert tips before choosing

Expert tip

Build the same small lead-routing flow in both trial accounts. Use 100 representative records, including duplicates and records that fail a filter. Record Make credits by module and Zapier tasks by completed action. Then project those actual units to your busiest month. Keep polling checks, AI calls, retries, team seats, and paid connector requirements in separate budget rows. This avoids treating one Make credit as equivalent to one Zapier task.

If the source app supports instant webhooks, compare that design with frequent polling in Make. If the workflow uses many Zapier Paths, verify how many actions execute in each route.

The strongest buying decision comes from the data flow you can maintain and afford, not from the number of integrations displayed on a pricing page.

Final recommendation

Choose Make for detailed visual automation when routing, transformation, and module-level control matter most. Its lower observed entry price for a 10,000-credit tier can be attractive, but the credit meter includes more than final app actions.

Choose Zapier for straightforward app automations and a task model that does not charge for standard trigger polling or many built-in logic steps. Watch the task-tier requirement as completed action volume grows.

For either platform, verify the exact connector actions and obtain a plan quote using an expected usage range. Both vendors can handle the shared use case; their total cost depends on workflow shape.

How Toollers prepared this comparison

Testing methodology

This comparison was prepared on 2026-11-07 using Make’s official pricing and credit documentation, including module-level counting, router and filter exceptions, annual-credit behavior, and extra credits. We also reviewed Zapier’s official plan page, task-measurement documentation, Paths guidance, and current pricing explanations. We checked plan distinctions and upcoming rule effective dates. No paid-account hands-on benchmark, independent connector reliability measurement, production automation deployment, or verified invoice comparison was performed. Hypothetical usage examples state their assumptions. Live Toollers product IDs, media mapping, and selected-region checkout prices remain unconfirmed; the article is therefore a draft.

Pricing and usage rules can change by region, billing term, product rollout, account history, and task or credit tier. Recheck vendor checkout and help documentation before publication or procurement.

Official sources

Read the Make Toollers profile for more details.

Read the Zapier Toollers profile for more details.

Frequently asked questions

Is Make better than Zapier?
Make is a strong fit for visual, complex workflows with routing and data transformations. Zapier is a strong fit for familiar app connections and clear trigger-to-action automations. Neither is universally cheaper because credits and tasks count different work.
What is the main difference between Make and Zapier?
Make builds scenarios from connected modules on a canvas and generally charges credits for executed module operations. Zapier builds Zaps from triggers and actions and generally counts tasks for successfully completed actions.
Does Make charge credits if no new data is found?
Usually yes for scheduled polling trigger modules. Make states that a trigger check uses one credit even when no records are returned. Routers and filters are exceptions that do not consume credits.
Does Zapier charge tasks for polling and Filters?
Zapier says standard trigger polling, Filter steps, Paths, and Formatter actions do not count as tasks. Successful downstream actions do, and certain AI, code, MCP, or SDK features have specific charging rules.
How much does Make cost?
Make Free includes up to 1,000 credits per month. Its observed US monthly pricing selection for 10,000 credits lists Core at $12, Pro at $21, and Teams at $38 monthly. Other credit tiers and annual billing change the price.
How much does Zapier cost?
Zapier Free provides 100 tasks monthly. Its published starting annual-billing equivalents are $19.99 per month for Professional and $69 per month for Team. The price depends on the task-volume tier and billing period.
Is one Make credit equal to one Zapier task?
No. Make can charge for trigger checks, searches, iterators, and action modules, while Zapier typically excludes trigger polling and several built-in steps. Model your specific module runs and successful actions.
Can Make and Zapier both create branching workflows?
Yes. Make uses routers and filters to split scenario routes. Zapier uses Paths and Filters. Make and Zapier both say the branching control steps themselves generally do not consume credits or tasks, although downstream operations may.
Which has more integrations, Make or Zapier?
Both advertise thousands of integrations, and Zapier reports a larger app catalog. Catalog size does not confirm whether a needed trigger, lookup, field, or write action exists on the intended subscription.
What happens when I exceed my Make credits?
Make allows eligible paid plans to buy extra credits or activate auto-purchasing. Without added credits, scenarios may stop processing until the allowance is replenished; queue and retention limits still apply.
What happens when I exceed my Zapier tasks?
Depending on the paid account configuration, Zapier may bill excess tasks through pay-per-task billing or hold additional Zap runs until more task allowance is available.
Which tool is better for marketing automation?
Both handle lead capture, CRM updates, segmentation, and notifications. Make suits complex routing and transformations; Zapier suits straightforward app connections and built-in logic that can filter events without adding tasks. Compare the exact connector actions and monthly usage.

Sources

Written by

Shikha Goyal

Author

Toollers editorial contributor. Biography and credentials pending confirmation.

Reviewed by Aditya Verma