Action (Automation)
An action is a step an automation runs after its trigger fires, such as posting a message or creating a record. Each successful action counts as one task.
Updated October 1, 2026
An action is a step an automation runs after its trigger fires, such as "post a Slack message" or "create a contact." A Zap has one trigger and at least one action. Actions are the steps that change data in a connected app.
How actions run
When the trigger fires, the automation runs each action in order. Data from the trigger, like a customer name, an amount, or an email, becomes input for the actions. A multi-step Zap chains several actions, so one event can update a CRM, notify a channel, and add a spreadsheet row.
Built-in steps sit between actions. A formatter reshapes a value, and a filter stops the run unless a condition is met.
Actions and task billing
Each successful action step counts as one task.
Triggers, filters, and paths don't use tasks. A Zap that posts to Slack and then updates a sheet uses two tasks per run. On usage-based plans, your bill grows with actions per run times the number of runs.
Why it matters
A busy Stripe account can fire thousands of events a month, and every action on every run uses a task. Filter early and keep actions to the ones you need. ChargeBell sends Stripe events to Slack for a flat $24/mo, with no per-action charge as your payment volume grows.