[EXAMPLES] Zapier Tasks VS Make.com Operations (formerly Integromat)

[examples] Zapier Tasks VS Make.com Operations (formerly Integromat)

Purpose

Help explain the difference between Zapier Tasks in Zaps and Make.com Operations in Scenarios.

Make.com was formerly Integromat.

Zapier Tasks

Help article to learn about Zapier Tasks: https://help.zapier.com/hc/en-us/articles/8496196837261

Overview

Whenever your Zap successfully completes an action, it counts as a task.
Trigger steps do not count as tasks, but successful action steps do.
You can see all the tasks your Zaps have attempted in Zap History.

How Tasks are Counted

The following count as tasks when your Zap runs:

Any successful action step.
- These actions steps do NOT count as Tasks.
  - Any formatter step that passes.
  - Any filter step that passes.
  - Any time a path’s rules pass.
For Sub-Zaps, the Call a Sub-Zap action and the Return From a Sub-Zap action each use 1 task.

Note

If Should This Step Be Considered a "success" When Nothing Is Found? is selected in a search step, the search action will count as a task.

Make Operations

Help article from Make.com: https://www.make.com/en/help/scenarios/counting-the-number-of-operations#make-s-operations-vs--zapier-s-tasks

Make

The trigger and search modules always perform 1 operation (even if more than 1 bundle is received).
Each action module usually performs 1 or more operations, although there are exceptions.
If you want to calculate the total number of operations needed for the scenario, you can count approximately 1 operation for 1 step (module) in the scenario.

Zapier

Zapier triggers do not perform any chargeable task.
Zapier actions perform the task(s) that you are charged for.

EXAMPLE 1

Steps: 2 (trigger + action)

Trigger (instant via webhook)
1. Zap Tasks: 0
2. Make Operations: 1
Action
1. Zap Tasks: 1
2. Make Operations: 1

Runs: 100 records processed

Total:

Zap Tasks: 100
Make Operations: 200

EXAMPLE 2

Steps: 2 (trigger + action)

Trigger (scheduled via polling an API endpoint every X minutes)
1. Zap Tasks: 0
2. Make Operations: 1
Action
1. Zap Tasks: 1
2. Make Operations: 1

Runs: 100 records processed in 24 hours

Total:

Interval: 15 minutes
- Zap Tasks: 100
- Make Operations: 196
  - 96 trigger checks over 24 hours
  - 100 action steps
Interval: 10 minutes
- Zap Tasks: 100
- Make Operations: 244
  - 144 trigger checks over 24 hours
  - 100 action steps
Interval: 5 minutes
- Zap Tasks: 288
- Make Operations: 388
  - 288 trigger checks over 24 hours
  - 100 action steps
Interval: 1 minute
- Zap Tasks: 100
- Make Operations:1,540
  - 1,440 trigger checks over 24 hours
  - 100 action steps

Plans & Pricing

Make sure to review the plans, pricing, and features.

Make.com: https://www.make.com/en/pricing

Zapier: https://zapier.com/app/billing/plans

Page 1 / 1

Thanks for the information, Troy! This one is particularly eye-opening:

@nicksimard

Arguably the biggest competitive comparison I see against Zapier is related to pricing (without true context).

But there tends to be a genuine lack of understanding about how the pricing is really broken down and related to different features.

Both apps can be cheaper depending on the use cases and configurations. (Same for other competitor apps.)

Could be useful marketing material.