Make Credits

Make.com's recently-introduced credit-based pricing system allows more granular billing. However, for this very reason, it can significantly increase costs in scenarios with loops, long execution durations, or high processing loads. Under the new credit system:

  • Most modules cost 1 credit per operation
  • Some modules cost more if they have higher complexity or longer runtime
  • If you iterate over large datasets, each loop iteration is billed separately
  • Long-running operations (especially with AI or file processing) may consume credits dynamically based on execution time

For workflows involving Make.com, customJS offers a cost-effective alternative. By moving JavaScript logic to the native customJS module, you can reduce costs by up to 80% compared to running the same logic directly in Make.com.

Cost comparison

Scenario Make.com (credits) Native customJS module
50 iterations/day × 1 credit each 50 credits/day = 1500/month (~$15) Free if ≤ 20/day, else $10/month
100 iterations/day × 1 credit each 100 credits/day = 3000/month (~$30) $10/month
200 iterations/day × 1 credit each 200 credits/day = 6000/month (~$60) $10/month

Example: cost of processing 50 items

Aspect Make.com (credits) Native customJS module
Processing method 50 iterations × 1 credit each Single request for all 50 items
Time per item ~30 seconds per item (billed per iteration) Up to 60 seconds of JS execution per request
Billing basis Per iteration Per request
Daily cost (50 items) 50 credits ≈ $0.50 (example rate) Free if ≤ 20 requests/day; otherwise paid plan
Monthly cost (run daily) ≈ $15 Free (≤ 20 requests/day) or $10/month for higher usage