OA
OpsAgent

Billing

Last updated 3 weeks ago

OpsAgent uses usage-based billing — you pay based on the number of workflow action executions your apps perform. There are no fixed monthly subscription fees.

How Billing Works

OpsAgent charges based on action executions — each time a workflow runs, a CRM card interaction occurs, or an API call executes, that's one action. Only successful actions are billable; failed or skipped actions are never charged.

For a detailed explanation of actions, statuses, trigger sources, and pricing, see Actions.

Your current usage is always visible on the Billing page, which shows:

  • The current billing period (start and end dates)
  • Total action executions so far
  • Current cost

Detailed execution logs and filtering options are available on the Usage page.

Payment Methods

OpsAgent uses Stripe for payment processing. You can add and manage credit or debit cards from the Payment Methods tab on the Billing page.

To add a payment method:

  1. Go to Billing and click the Payment Methods tab
  2. Click Add Payment Method
  3. Enter your card details
  4. Click Save

If you have multiple payment methods, you can set any card as the default. The default card will be used for all charges.

Billing Information

You can configure your billing details (company name, address, VAT ID) from the Billing Info tab on the Billing page. This information appears on your invoices.

Fields include:

  • Company name
  • Billing address (street, city, state, postal code, country)
  • VAT ID (for EU businesses)

Invoices

Past invoices are available in the Invoices tab on the Billing page. Each invoice shows:

  • Invoice number and date
  • Total amount
  • Payment status

Click on any invoice to view or download it via Stripe's hosted invoice page.

Monthly Budget Limits

To prevent unexpected charges, you can set a monthly budget limit for your organization. When your usage reaches the budget threshold, workflow action executions will be paused until the next billing period.

This is useful for controlling costs during testing or when you want to cap spending at a predictable amount.

Previous
Overview