See llms.txt for all machine-readable content.

Back to Templates

Estimate WhatsApp Business API monthly costs from a CSV rate card

Created by

Created by: Tobachat || tobachat
Tobachat

Last update

Last update 9 hours ago

Categories

Quick overview

This workflow runs manually to estimate monthly WhatsApp Business Platform template messaging costs per country and category by combining your planned send volumes with an external EUR open-rate pricing CSV, producing per-line costs, a total, and the rates’ effective date.

How it works

  1. Runs when you manually execute the workflow.
  2. Loads your planned template send volumes by country ISO code and message category (marketing, utility, authentication).
  3. Downloads the WhatsApp Business API EUR rate card CSV via HTTP.
  4. Parses the CSV, matches each planned country to a single-country rate or regional rate (falling back to “Other” when needed), and calculates EUR cost per line using the selected per-message rate.
  5. Outputs a cost line per country and category, each with the effective date of its rate, plus a TOTAL row with the monthly message count and the total EUR cost.

Setup

  1. Update the planned send list with your country ISO codes, categories (marketing, utility, authentication), and monthly message counts.
  2. Verify the rate CSV URL is accessible (and replace it if you use a different or newer pricing source).
  3. Execute the workflow and review the output, especially the effective_date, before using the estimate for budgeting.

Requirements

  • No credentials. The workflow only needs internet access to download the public rate CSV.

Customization

  • Read the planned sends from Google Sheets instead of the Code node, add a Schedule Trigger to rerun the estimate every month, or add a Slack, Gmail or Google Sheets node after Estimate cost to deliver the result.

Additional info

The rates are Meta list prices in EUR per delivered template message from the Tobachat open dataset (https://tobachat.nl/en/whatsapp-business-api-costs/). The estimate does not model free service windows or volume tiers, so treat it as a ceiling and check Meta pricing before you commit to a budget.