×

Custom Actions in Zapier

/ Zapier / By

Custom Actions in Zapier: Step-by-Step Guide

When built-in app events are not enough, you can use Zapier custom actions to call any app’s public API and extend what your workflows can do inside Zapier.

This guide explains how to create, configure, test, and manage custom actions using the AI-powered visual builder, plus the limitations and best practices you need to know.

What is a Custom Action in Zapier?

A custom action is a step in a Zap that sends data to an app’s public API using HTTP requests. With a custom action you can:

  • Access features that are not yet available in Zapier’s standard app integrations.
  • Send data to any app that exposes a public REST API.
  • Configure HTTP methods, URLs, headers, and body content.
  • Use the AI visual builder to generate requests from plain language.

Custom actions are available on paid Zapier plans only.

Requirements and Limitations in Zapier

Before building, review what custom actions in Zapier can and cannot do.

Plan and access requirements in Zapier

  • Available only on paid Zapier plans; not supported on free plans.
  • You must use an existing Zap with supported trigger types.
  • You can add multiple custom actions in one Zap if needed.

Feature limitations of Zapier custom actions

  • Only request actions are supported (no triggers or searches).
  • No file support: you cannot send or receive files.
  • No pagination: a single request cannot automatically fetch multiple pages of results.
  • No cursors or streaming responses.
  • Cannot be used with Email by Zapier.
  • Cannot be used for private apps that require installation via invite.
  • Does not support XML request or response formats.
  • Does not support Form-Data request bodies.

Prerequisites for using APIs with Zapier

To build a reliable custom action in Zapier, you should have:

  • Access to the app’s public API documentation.
  • Details about authentication (for example, API key, OAuth token, or Bearer token).
  • Endpoint URLs, required query parameters, and required headers.
  • Sample request and response payloads in JSON format.

How to Create a Custom Action in Zapier

Custom actions are designed to be created directly from a Zap. You cannot create them from the My Apps page, but only from the Zap editor.

Step 1: Open or create a Zap in Zapier

  1. Sign in to your Zapier account.
  2. Create a new Zap or open an existing one.
  3. Ensure you have at least one trigger step before adding a custom action.

Step 2: Add a Zapier custom action step

  1. In the Zap editor, click the plus (+) icon to add a new step.
  2. Select the app you want to send data to. If the app has a native integration but is missing a specific action, you can still add a custom action step for that app.
  3. In the list of events, choose the option labeled Custom Action (Beta) or similar, depending on the app.
  4. Connect your account if prompted, following the app’s authentication instructions.

Step 3: Use the AI visual builder in Zapier

After selecting the custom action event, you will see the visual builder where you define your API request.

  1. In the AI prompt box, describe the action in plain language. For example: “Create a new contact with first name, last name, and email.”
  2. Include the endpoint path, HTTP method, and any query parameters if you know them.
  3. Click the button to let Zapier AI generate a draft request.

The visual builder will populate fields such as:

  • HTTP method (GET, POST, PUT, PATCH, DELETE).
  • Endpoint URL.
  • Headers, including authorization.
  • Request body structure in JSON.

Step 4: Configure request details manually in Zapier

Review and refine the request created by the AI builder.

  1. Confirm the HTTP method matches the API documentation.
  2. Update the URL path and query parameters as needed.
  3. Add or adjust headers, such as Content-Type: application/json and authorization fields.
  4. Edit the JSON body to match the API’s expected fields.
  5. Insert dynamic data from previous Zap steps using the field selector.

If the API requires complex nested JSON objects, make sure the structure follows the examples from the documentation.

Step 5: Test your custom action in Zapier

  1. Click Test step in the Zap editor.
  2. Zapier sends the configured request to the API.
  3. Check the response data returned from the app.

If the test is successful, you will see fields you can map in later Zap steps. If the test fails, follow the troubleshooting guidance below.

How to Use Custom Actions in Your Zapier Workflow

Once the custom action is tested, you can integrate it into the rest of your workflow.

  • Map response fields from the custom action into subsequent Zap steps.
  • Use filters or paths to control when the custom action runs.
  • Combine multiple custom actions with standard Zapier app actions.

You can add more than one custom action in a single Zap if the process requires multiple API calls.

Troubleshooting Zapier Custom Actions

Common issues with custom actions in Zapier usually come from incorrect API configuration or authentication problems.

Check authentication and headers

  • Confirm that your connected account is authorized to call the API.
  • Verify that the authorization header (for example, Authorization: Bearer <token>) is correct.
  • Ensure any required custom headers from the API documentation are included.

Verify URL, method, and body configuration

  • Compare the endpoint URL and HTTP method with the API docs.
  • Check that the request body is valid JSON and uses the correct field names.
  • Remove any trailing commas or invalid characters from the JSON.

Review API documentation for errors

  • Look up the HTTP status code returned in the test (for example, 400, 401, 403, 404, 500).
  • Use the error message from the API response to identify missing or invalid parameters.
  • Confirm rate limits or quotas are not exceeded.

Limitations to keep in mind inside Zapier

  • Responses that rely on pagination will only return the first page.
  • Responses in XML, binary, or file formats are not supported.
  • Form-Data or multipart requests must be converted to JSON if the API allows it; otherwise they are not supported.

Managing and Editing Custom Actions in Zapier

You manage each custom action from within its Zap.

  • Open the Zap containing the custom action step.
  • Click on the step to edit the configuration.
  • Update the AI prompt, URL, headers, or body as the API changes.
  • Retest the step after every significant change.

Currently, there is no separate library of reusable custom actions; each one belongs to the specific Zap where it is created.

Best Practices for Safe Zapier Custom Actions

  • Use test or sandbox API keys wherever possible during setup.
  • Limit the data sent to only what the endpoint requires.
  • Store sensitive values (like API keys) in account connections, not in plain text fields.
  • Document the purpose of the custom action in the step description for future maintenance.

Learn More About Custom Actions in Zapier

For official reference material on custom actions, including current limitations and UI details, see the original help article on the Zapier website: Custom Actions in Zapier.

If you need strategic help planning complex automations, integration architecture, or SEO-focused automation workflows, you can explore consulting resources at Consultevo.

By understanding how custom actions work and how to configure them correctly, you can use Zapier to integrate with almost any public API and extend your automations far beyond standard app events.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.


Get Zapier Help

Verified by MonsterInsights