Action (Automation)

An action is a step an automation performs after its trigger fires — "post a Slack message," "create a contact," "send an email." A Zap has one trigger and at least one action, and each action runs the work that actually changes data in a connected app.

How actions run

When the trigger fires, the automation executes each action in order, passing data from one step to the next. Fields from the trigger — a customer name, an amount, an email — flow into the action as inputs. A multi-step Zap chains several actions so one event can update a CRM, notify a channel, and log a row in sequence.

Actions are where transformation and routing usually sit alongside built-in steps like formatter (reshape a value) and filters (stop the flow unless a condition is met).

Actions and task billing

Billing is the key thing to understand about actions:

Triggers, filters, and paths are free, but every action that completes consumes a task. So a Zap that posts to Slack and updates a sheet uses two tasks per run. On usage-based plans, the number of actions per run multiplied by run volume is what drives your bill.

Why it matters

The more actions a workflow performs and the more often it runs, the more tasks it burns — which is why a high-traffic Stripe event can make an automation surprisingly expensive. Keeping actions lean, filtering early, and choosing flat-priced tools for high-volume paths all help. ChargeBell handles the common Stripe-to-Slack case for one flat $24/mo, with no per-action metering as your payment volume grows.