A practical field guide from Automation Ace.
Using the API Request Action in Zapier App Integrations
Many Zapier app integrations include an API Request action — sometimes labeled "API Request (Beta)" — that lets you call any endpoint in that app's REST API directly from a Zap step. Unlike using Webhooks by Zapier (which requires you to manage authentication headers manually) or a Code step (which requires writing fetch logic), the API Request action automatically uses the authentication from your existing connected account. It's the fastest way to call an API endpoint that the native Zapier integration doesn't expose as a built-in action.
What the API Request Action Does
When you select the API Request action in a Zapier app integration, you get a generic HTTP request builder pre-wired to the app's base URL and authenticated using your connected account. You specify:
- Method: GET, POST, PUT, PATCH, DELETE
- Endpoint: the path relative to the app's API base URL (e.g.,
/v1/contacts/12345) - Query String Parameters: key-value pairs appended to the URL
- Request Headers: additional headers beyond authentication (e.g., Content-Type)
- Request Body: JSON or form-encoded body for POST/PUT/PATCH requests
The authentication (OAuth token, API key, session token) is injected automatically from the connected account — you never handle credentials directly in the step.
Which Apps Include the API Request Action
Not every Zapier integration includes it, but many major platforms do. Look for "API Request" in the action list when selecting an action for apps like:
- HubSpot, Salesforce, Pipedrive
- Airtable, Notion, ClickUp
- Slack, Microsoft Teams
- Shopify, WooCommerce
- Google Workspace apps (Sheets, Drive, Gmail, Calendar)
- Stripe, QuickBooks
- ActiveCampaign, Mailchimp
If an app's integration includes it, it appears in the action dropdown like any other action. If it isn't listed, fall back to a Code step with fetch or Webhooks by Zapier.
When to Use It vs. Alternatives
- Use API Request when the app already has a connected Zapier account and the endpoint you need isn't a built-in action — e.g., deleting a record, calling a bulk endpoint, or using a beta API feature
- Use Webhooks by Zapier when you're calling a completely different app with no Zapier integration, or when you need precise control over all request headers including auth
- Use a Code step when you need conditional logic, response parsing, looping, or error handling around the API call — see HTTP POST in Zapier Code steps and HTTP GET in Zapier Code steps
Example: Delete an Airtable Record via API Request
Airtable's native Zapier integration doesn't include a "Delete Record" action. But the Airtable integration includes an API Request action that uses your existing Airtable connected account:
- Add an Airtable → API Request action
- Select your connected Airtable account
- Set Method to
DELETE - Set Endpoint to
/v0/{baseId}/{tableId}/{recordId}— maprecordIdfrom your trigger - No body needed for DELETE requests
The action sends a DELETE request to the Airtable API authenticated with your account's token. For deleting Airtable records via JavaScript in a Code step, see deleting Airtable records via API.
Example: Create a HubSpot Note via API Request
HubSpot's standard Zapier actions don't cover every endpoint. Using the API Request action:
- Add a HubSpot → API Request action
- Method:
POST - Endpoint:
/crm/v3/objects/notes - Headers:
Content-Type: application/json - Body (JSON):
{ "properties": { "hs_note_body": "{{note_text}}", "hs_timestamp": "{{timestamp}}" } }
Map {{note_text}} and {{timestamp}} from earlier Zap steps using the field mapper.
Parsing the API Response
The API Request action returns the response body as a set of output fields. For JSON responses, Zapier automatically parses the top-level keys as individual fields you can map in downstream steps. For nested objects, you may see dot-notation keys (e.g., data.id) or need to extract values in a Code step:
// If the API response is nested, parse it in a Code step
let response;
try {
response = JSON.parse(inputData.response_body);
} catch (e) {
throw new Error('Failed to parse API response: ' + e.message);
}
output = {
record_id: response.id || response.data?.id || '',
status: response.status || ''
};Error Handling
The API Request action fails the Zap step if the response status is 4xx or 5xx. If you need the Zap to continue despite errors — or to take different actions based on the response code — use a Code step instead, where you can check response.status and handle it explicitly.
The API Request action is the highest-leverage option when it's available: you get authenticated access to the full API with no credential management, using the same connected account already configured in the Zap. Check the action list for "API Request" before reaching for Webhooks or a Code step — if it's there, it saves significant setup time and removes authentication complexity from your Zap.
For making authenticated HTTP requests in a Code step when the API Request action isn't available, see HTTP POST in Zapier Code steps and HTTP GET in Zapier Code steps. For configuring Webhooks by Zapier as an alternative, see passing data through Webhooks in Zapier. For help calling a specific app's API from a Zap, talk to Automation Ace.
Disclaimer: This article may include links to apps, products, or services. Some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.