Zaptiva Usage Parameters

Zaptiva Usage Parameters

Usage Metering in Zaptiva

This article defines how usage is metered in Zaptiva.

Summary

  • Flow Runs — how many times a Flow executes per month.
  • Operations — countable steps executed inside a Flow (loop iterations included).
  • AI Credits — metering for AI features; 1 Credit = $0.01 (customer-facing equivalence).
  • Concurrent Flow Runs — how many Flows can run at the same time.
  • Test Mode — run Flows without consuming Flow Runs; limited and watermarked.

Flow Runs

A Flow Run is a single execution of a Flow from trigger to completion. Every trigger (manual, schedule, webhook, or event) counts as one Flow Run.

  • Example: If a Flow is triggered 500 times in a month, that equals 500 Flow Runs.
  • Effect: Plan limits specify how many Flow Runs you can consume each month.

Operations

An Operation is a counted step executed within a Flow.

  • Each Action, Search, or Data Transformation counts as one Operation.
  • Routers, Aggregators, Filters, and If/Else do not consume Operations.
  • Loops consume multiple Operations. Each iterated item counts as one Operation.

Example: A Flow that loops 100 items and performs one action per item consumes 100 Operations in that single Flow Run.

AI Credits

AI Credits are consumed when using AI-powered steps (generation, summarization, classification, enrichment, etc.).

  • 1 AI Credit = $0.01 for customer-facing equivalence.
  • Internally, Zaptiva meters tokens to control cost, but customers only see the credit model.
  • Credits may be purchased in packages with volume discounts.

Concurrent Flow Runs

Concurrent Flow Runs define how many Flows can execute simultaneously in your account.

  • If the concurrency limit is reached, new Flow Runs queue until a slot is free.
  • Higher plans include more concurrency; add-ons can increase this limit.
  • Example: With a concurrency of 2, if two Flows are running, a third will wait.

Test Mode

Implementation note: Test Mode is not yet available. Until released, it is subject to the Fair Use Policy below.

Test Mode lets you run a Flow without consuming Flow Runs.

  • All Flows can be executed in Test Mode once implemented.
  • Runs are limited in the number of records processed, to prevent production-scale usage.
  • Output is watermarked or otherwise marked as non-production to discourage live use.
  • Intended for validation, troubleshooting, and step-by-step iteration.

Service Conditions & Limitations 
(QWC-Based Integration for QuickBooks Desktop Only)

  • Dedicated Integration User (QuickBooks License Required)
    Zaptiva connects to QuickBooks Desktop through the QuickBooks Web Connector (QWC) using a designated integration user. This user is treated by QuickBooks as a standard user and consumes one QuickBooks Desktop user license for the duration of the integration.
  • Multi-User Mode Requirement
    The QuickBooks company file must remain in Multi-User Mode at all times. If the file is switched to Single-User Mode, scheduled or on-demand synchronizations will fail until Multi-User Mode is restored.
  • Dedicated Windows Profile for Synchronization
    The QuickBooks company file and QWC must run under a dedicated Windows user profile intended solely for Zaptiva synchronization.
    • This profile should not be used for day-to-day QuickBooks access by staff.
    • Human interaction within the same Windows profile (opening QuickBooks, switching company files, closing sessions, modal prompts, or interruptions) can disrupt or block Zaptiva sync operations.
    • While technically possible to share the profile, doing so is strongly discouraged and may introduce instability, failed syncs, or data timing issues.

These conditions are required to ensure a stable, predictable, and supportable integration between Zaptiva and QuickBooks Desktop. Failure to meet them may limit functionality, reliability, or Zaptiva’s ability to provide full operational support.

Fair Use Policy

Until all usage limits are technically enforced in the platform, Zaptiva applies a Fair Use Policy.

  • We monitor usage across Flow Runs, Operations, AI Credits, and Concurrent Flow Runs.
  • Excessive or disproportionate consumption may trigger a review and plan adjustment.
  • Zaptiva reserves the right to revise pricing or apply surcharges when usage exceeds fair thresholds.
  • After metering/enforcement is live, the plan limits you purchase will apply automatically.
© Zaptiva — Subject to change. This document reflects current design intent and policies.

    • Related Articles

    • Zaptiva Apps Categories

      Apps Categories Zaptiva provides apps that allow users to connect external systems, databases, and file formats within automation workflows. These apps are organized into three categories: Core Apps. Standard Apps. Premium Apps. Core Apps Core Apps ...

    • Getting Started with Zaptiva.

      Signup The first steps to get started is to sign up for a Zaptiva account, and select a plan. Navigate to the URL: https://app.zaptiva.com/ Login page will display Click on “Don’t have an account?” link and you will be redirected to the sign up page ...

    • Zaptiva Release Notes

      v2.13.1 Beta Release Date: Feb 19, 2026 MAJOR FEATURE: Introduced a new module named "User Log" for Super Admin to view user activity logs. Introduced two new operations, "Get Balance Sheet" and "Profit & Loss", under QuickBooks Desktop. Enhanced the ...

    • Notifications in Zaptiva: Overview and User Guide

      1. Notifications in Zaptiva Notifications in Zaptiva help users stay informed about important activities, updates, and system events in real-time. These alerts ensure that users never miss critical actions such as Renewal Subscription status, ...

    • How to manage Subscription and Payment Method in Zaptiva.

      Managing Billing & Payment Methods in Zaptiva Follow the steps below to manage Billing & Payment Methods in Zaptiva: 1. Navigate to the URL: https://app.zaptiva.com/ 2. Log in to your Zaptiva account. Billing & Subscription Update Payment Method ...