> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zapier.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started

> How To Run An Action

Use **Action Runs** to expand your existing workflow builder or automation product with Zapier’s library of 8,000+ app integrations.

Action Runs let your product trigger individual Zapier actions—such as sending an email, updating a CRM record, or posting to Slack—directly through the **Workflow API**. This allows you to offer your users powerful cross-app automations without needing to build and maintain thousands of individual connectors yourself.

Your product continues to own the workflow experience and execution layer, while Zapier handles the authentication, action execution, and integration maintenance behind the scenes.

***

## What is an Action Run?

An **action run** represents a single execution of an action step in a Zapier workflow. When you call the Action Run API, Zapier executes the action logic and returns a `run_id` that you can use to check the run's status and result.

<Warning>
  Running actions via the Workflow API is currently in limited beta. If you
  would like access to run actions, please use contact [ryan.powell@zapier.com](mailto:ryan.powell@zapier.com) to
  request access.
</Warning>

***

### Understanding Action Runs vs. Zaps

**Action Runs** differ from **Zaps** in how they’re created and executed:

* A **Zap** is a saved, user-owned workflow (trigger → actions) stored and managed by Zapier.
* An **Action Run** is a one-off action your app triggers through the **Workflow API**. Zapier executes the action but doesn’t store the workflow definition.
* Action Runs are stateless: data is retained briefly (7 days) for processing and troubleshooting, then automatically deleted. You should store any request or response data needed for visibility or support.

**Support expectations:** You’re responsible for surfacing run results or errors to your users. Zapier provides the execution infrastructure and may assist with escalations if needed.

**Contract end:** If your contract with Zapier ends, API access is disabled and any Action Run data in Zapier’s systems expires automatically within the retention window.

***

## Example / Demo

<Frame caption="See a walkthrough of how to run one-off actions using the WorkflowAPI.">
  <video controls className="w-full aspect-video" src="https://cdn.zappy.app/79ec346f9f76eeb2296461a864d034c7.mp4" />
</Frame>

***

## Prerequisites

Before you begin, make sure:

* You have access to a **public Zapier integration**.
* You’ve [registered your app and authenticated](/powered-by-zapier/authentication/methods/user-access-token) to use the API.
* You have at least one **action** configured in your integration, with required fields and sample data tested in the Zapier UI or via the API.
* You've had your integration added to the Action Runs allowlist

***

## View our guides for more information

* Step 1: [Trigger an Action Run](/powered-by-zapier/running-actions/create-action-run)
* Step 2: [Retrieve the Action Run Result](/powered-by-zapier/running-actions/retrieve-action-run)