Actions

OpsAgent uses a usage-based billing model built around the concept of actions. Every interaction your apps perform in HubSpot — from executing a workflow action to rendering a CRM card — is tracked as an action execution.

What is an Action?

An action is a single unit of work performed by an OpsAgent app. Each time a workflow action runs in HubSpot, a CRM card interaction occurs, or an API call executes a task, that counts as one action execution.

Actions are the core billing unit in OpsAgent. Every execution is logged with its status, cost, app information, and metadata, giving you complete visibility into your usage.

Action Inputs and Outputs

When you add a workflow action to your HubSpot workflow, you work with two key concepts:

Action Inputs — The data the action needs to do its work. When configuring a workflow action, you'll fill out input fields like text boxes, dropdowns, and checkboxes. These inputs tell the action what to do (for example, which email address to send to, what phone number to format, or which date to modify).

Action Outputs — The results produced by the action. After the action runs, it creates output values that you can use in later workflow steps. For example, an address geocoding action might output the latitude and longitude it calculated. You can use these outputs to:

• Copy values to record properties — Save the output to a HubSpot contact, company, or deal property
• Branch the workflow — Use the output in an if/then branch to make decisions (for example, "if the geocoded address is within 50 miles...")
• Pass data to subsequent actions — Use the output as an input for another workflow action

To learn how to use action outputs in your workflows, see Using workflow action outputs in the HubSpot Knowledge Base.

Action Statuses

Each action execution has one of three statuses:

• success — The action completed successfully. This is the only billable status.
• failed — The action encountered an error and did not complete. Failed actions are never billed.
• skipped — The action was skipped because no work was needed (for example, a conditional check determined the action wasn't necessary). Skipped actions are never billed.

You're only charged for successful actions. If something goes wrong or the action doesn't need to run, you don't pay for it.

Trigger Sources

Actions can be triggered from three different sources:

• workflow — Triggered by a HubSpot workflow step
• card — Triggered by a user interacting with a CRM card on a HubSpot record page
• api — Triggered by an API call made to OpsAgent

The trigger source is logged with each execution so you can track where your usage is coming from.

Action Pricing

Each action has a price per execution, defined in cents. Pricing is configured per app and feature, and can be customized at the organization level or use the platform's default rate.

Some key points about pricing:

• Pricing can vary by app and feature — more complex operations may cost more than simple ones
• Some actions are completely free ($0.00) — for example, helper actions that support a primary billable action
• The price is snapshotted at execution time — you're always charged the rate that was active when the action ran, even if pricing changes later
• Custom organization pricing overrides the platform default, letting you negotiate custom rates if needed

For example, the OTP Verification app charges $0.07 per OTP generation, but the helper actions (storing the OTP in a HubSpot property, sending an email) are free.

Tracking Usage

All action executions are visible on the Billing > Usage page. This page provides:

• Total execution count for the current billing period
• Success rate (percentage of successful vs. failed/skipped)
• Total cost so far in the current period
• Daily usage charts showing executions and costs over time
• A filterable log table with every individual action execution

You can filter the log by:

• App name
• Action status (success, failed, skipped)
• Trigger source (workflow, card, api)
• Specific action name
• Date range

This makes it easy to understand exactly where your costs are coming from and identify any unexpected spikes in usage.

Billing Connection

At the end of each billing period, all unbilled successful action executions are aggregated and invoiced. The invoice line items show:

• Which app performed the action
• How many executions occurred
• The rate per execution
• The total cost

Failed and skipped actions are logged for visibility but never included in invoices.

For more details on payment methods, invoices, and budget limits, see the Billing documentation.