Workflow integrations

Measure the workload before the model runs.

Bring token, context-window, and model-cost preflight checks into automation pipelines. Each integration documents where calculation runs and which input types it supports.

02Available

Activepieces

Independent piece for local workflow-runtime counting, cost estimation, and multi-model comparisons.

03Planned

Zapier

Actions for counting, estimating cost, and comparing models in Zaps.

Documentation coming soon
04Planned

Make

Modules for preflighting LLM workloads before downstream model operations.

Documentation coming soon
Runtime boundary

Privacy follows the execution environment.

The browser calculator keeps content in the browser. Workflow integrations execute inside n8n, Activepieces, Zapier, or Make, so their deployment, logging, retention, and credential policies apply.

The integrations do not require a TokenCalculator.dev API key when they use the shared local core package.

Review the browser privacy architecture →