Zapier Built-In Tools and Native Apps: What They Do and When to Use Them

A practical field guide from Automation Ace.

Zapier Built-In Tools and Native Apps: What They Do and When to Use Them

Zapier's native tools — the apps built and maintained by Zapier itself — are the most underutilized part of the platform. Most users focus on the third-party connectors (HubSpot, Slack, Google Sheets) and overlook the Zapier-native capabilities that make those connectors far more powerful: data transformation, conditional logic, delays, loops, custom code, and webhook handling. Mastering these built-in tools is what separates a collection of simple two-step Zaps from a well-designed automation system. All Zapier native tools are browsable at zapier.com/apps/categories/zapier-tools.

Formatter by Zapier

Formatter is the most-used Zapier native tool. It transforms text, numbers, and dates without requiring any code. Common uses include: splitting a full name into first and last name fields, formatting a phone number to a standard format, converting a date from one format to another (ISO 8601 to MM/DD/YYYY), extracting a domain from an email address, truncating long text to a character limit, and capitalizing or lowercasing strings for consistent data entry. Formatter runs as a free action step — it does not consume Zapier tasks — making it one of the most cost-efficient ways to clean data in a workflow. See which Zapier steps are free and don't count as tasks for the full list.

Filter by Zapier

Filter stops a Zap from continuing if a condition is not met. It is essential for any Zap that handles data from a shared trigger — where not every record or event should proceed through all the action steps. A Filter step should be the second step in most Zaps that process CRM events, form submissions, or spreadsheet row updates. Without a filter, a Zap that fires on "any CRM contact updated" will run for every update, including minor field changes that are not relevant to the workflow. Filter by Zapier is also a free step. For more on designing Zaps that fire reliably on the right records, see multi-step Zapier workflow design.

Paths by Zapier

Paths adds conditional branching to a Zap — different action sequences execute depending on the value of a field. A single Zap with Paths can replace two or three separate Zaps that handle different cases of the same trigger. Common uses: routing leads to different sales reps based on territory, sending different email sequences based on a form answer, updating different records based on a status value, and handling different currencies or regions with different logic. Paths requires a Zapier Professional plan or higher.

Delay by Zapier

Delay pauses a Zap for a specified time before continuing — from minutes to days. Use cases: sending a follow-up email 24 hours after a form submission, waiting for a payment to clear before triggering fulfillment, staggering a series of onboarding tasks across multiple days, and building a simple drip sequence without a dedicated email platform. Delay Until is a variant that pauses until a specific date and time — useful for scheduled reminders tied to a record's date field.

Webhooks by Zapier

Webhooks by Zapier has two modes: as a trigger (Catch Hook) to receive incoming webhook payloads from any system, and as an action (GET, POST, PUT) to make outbound HTTP requests to any API. This makes Zapier extensible to any system with a REST API, regardless of whether it has a native Zapier connector. For a deep dive on how webhooks work and when to use them, see what is a webhook and the comparison of APIs vs webhooks for automation. For help connecting apps that do not have Zapier connectors, see Zapier missing trigger or action workarounds.

For authenticated, repeatable calls and polling APIs that have no webhooks, Zapier also offers API by Zapier. See API by Zapier vs Webhooks by Zapier.

Code by Zapier

Code by Zapier runs JavaScript or Python inside a Zap step. It has access to the output from previous steps as input variables and can return any data structure for use in subsequent steps. Use Code when Formatter cannot handle a transformation, when you need to make a complex calculation, when you need to parse a non-standard data format, or when you need to call an API with authentication that Webhooks cannot handle cleanly. Code steps require a Zapier Professional plan or higher. For a broader discussion of where code fits in automation workflows, see Python and JavaScript automation scripts.

Sub-Zap by Zapier (Zapier Sub-Zap)

Sub-Zap lets one Zap call another Zap as a reusable module. The called Zap receives inputs from the calling Zap and returns outputs. This is Zapier's answer to shared logic — instead of duplicating the same 5-step sequence in six different Zaps, you build it once as a Sub-Zap and call it from each of the six. Sub-Zap reduces maintenance burden significantly: when the shared logic changes, you update one Zap instead of six. It requires a Zapier Team plan or higher.

Looping by Zapier

Looping processes an array of values — a list of line items, a set of records, a comma-separated list of email addresses — by running one or more action steps for each item in the list. Before Looping existed, handling arrays in Zapier required workarounds with Code steps or multiple Zaps chained together. Looping is an add-on that can be purchased separately or comes included with higher-tier plans.

Schedule by Zapier

Schedule triggers a Zap at a fixed interval — every hour, every day, every week, on a specific day of the month. It is the starting point for any time-based automation: daily report exports, weekly digest emails, monthly cleanup tasks, or any workflow that should run on a calendar basis rather than in response to an event. Schedule by Zapier is a free trigger.

Email by Zapier and Email Parser by Zapier

Email by Zapier provides a Zapier-hosted email address that can send outbound emails (as an action) or receive inbound emails and trigger a Zap (as a trigger). Email Parser by Zapier is a companion service that extracts structured data from incoming emails using rules you define — useful for systems that send data via email rather than API. Both tools are free at basic usage levels.

The built-in Zapier tools are what turn a Zapier account from a collection of point-to-point connections into a programmable workflow engine. Formatter cleans your data. Filter keeps junk records out. Paths routes to the right action. Code handles the edge cases. Webhooks connects anything with an API. Together, they cover 90% of the logic you would otherwise need custom code to handle.

For mailboxes that are not on Gmail or Outlook, IMAP by Zapier triggers Zaps from new messages in any IMAP folder and SMTP by Zapier sends through your own mail server. See SMTP vs IMAP vs Email by Zapier vs Email Parser vs Gmail/Outlook to choose the right email tool.

SFTP by Zapier

SFTP by Zapier connects an SFTP server to your Zaps: trigger on new or updated files, and upload or download files as steps. It is the built-in way to automate file exchanges with banks, payroll providers, suppliers, and legacy systems. See SFTP by Zapier explained and SFTP vs FTP vs FTPS.

Files by Zapier

Files by Zapier works with file contents: Convert File to Text (PDF, DOCX, PPTX, XLSX, CSV, JSON, XML), Create CSV File, Extract Rows, and Send CSV File Row Data to Webhooks. See Files by Zapier explained and converting files to text for AI.

Web Parser by Zapier

Web Parser by Zapier parses a web page into its title and content as HTML, Markdown, or plain text, which makes any public page usable by AI and later steps. See 10 web parsing use cases and automating website monitoring and summaries.

URL Shortener by Zapier

URL Shortener by Zapier turns long links into short zpr.io links with one Shorten URL action, which is handy for SMS, social posts, and notifications. See URL shorteners explained.

RSS by Zapier and Storage by Zapier

RSS by Zapier triggers a Zap when a new item appears in any RSS or Atom feed — useful for monitoring competitor sites, content publishers, job boards, or any source that exposes an RSS feed. Storage by Zapier (via the StoreClient utility) provides simple key-value storage that persists between Zap executions — useful for maintaining state, tracking counts, or storing configuration values that need to be accessible across multiple Zaps without an external database.

Deciding between Storage by Zapier and Zapier Tables? See Storage by Zapier vs Zapier Tables and how to share data between Zaps.

For structured data you want to see and edit as a table, Zapier Tables stores records that Zaps can create, find, update, and trigger from. A common use is a shared lookup table for routing and value mapping.

AI Guardrails by Zapier

AI Guardrails by Zapier adds safety checks around AI steps: Check for Personally Identifiable Information (PII), Detect Prompt Injection, Detect Toxicity, and Detect Sentiment. Each returns a structured result you can stop on or route with Paths. See AI Guardrails by Zapier explained and how to detect PII before sending it to AI models.

Human in the Loop by Zapier

Human in the Loop by Zapier pauses a Zap so a person can review it. The Request Approval action asks someone to approve or change data before the Zap continues, the Collect Data action asks for missing information mid-run, and the New Approval Requested trigger starts other Zaps when a review is requested. See Zapier Human in the Loop explained and 10 practical use cases.

For teams building their first serious automation system, the recommendation is to learn Formatter, Filter, and Webhooks first — these three cover the majority of real-world workflow requirements and work on every Zapier plan. Paths and Code unlock the next tier of complexity when you are ready. For help designing a Zapier workflow that uses these tools correctly from the start, talk to Automation Ace.