Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 36 ยท Zaps, Triggers and Actions

Choosing Triggers and Apps for a Zap

Pick the right trigger event and the right app version: new versus updated records, instant versus polling, built-in apps, email parsing and schedules, plus a runnable trigger chooser.

The trigger is the foundation of a Zap. If it fires too often, too rarely or on the wrong thing, nothing after it can be right. This lesson shows how to choose the app, the event, and the settings of a trigger so it matches your intent.

Zapier cannot run on this site. Menus and event names are described in words and vary by app. The Python block is a labelled stand-in that models a decision guide.

Start from the question

Ask: "What exactly should start this automation?" Then write it as a precise sentence.

  • "When a new row is added to this sheet" is not the same as "when any row changes".
  • "When an email arrives with the label Invoices" is narrower than "when any email arrives".
  • "When a deal is moved to Won" depends on a field value change.

Apps offer different trigger events. Typical names:

Pattern Typical event names Use for
New item New Row, New Contact, New Email, New Order Reacting to creation.
Updated item Updated Row, Deal Updated, Contact Updated Reacting to changes (can fire often).
Specific change Deal Stage Changed, Status Changed A precise transition.
Matching a search New Email Matching Search, New Row in View Pre-filtered events.
Schedule Every Day, Every Week Reports and cleanups.
Webhook Catch Hook Anything that can send an HTTP request (chapter 5).

New versus updated

New triggers fire once per item. Updated triggers can fire every time any field changes, which may be many times per record. If you only care about one transition, prefer a specific trigger (such as stage changed) or add a filter that checks the field you care about.

Narrow at the source when possible

Some triggers let you limit the source: choose one folder, one label, one form, one view, one board. Narrowing at the trigger is cheaper and clearer than letting everything through and filtering later. Triggers like "New Row in View" (where supported) let the spreadsheet or database apply the criteria.

Built-in apps and utilities

Zapier ships its own utility apps, which are useful as triggers or helpers:

  • Schedule: run at fixed times.
  • Webhooks: catch incoming calls or send outgoing ones.
  • Email Parser (where available) and mailbox-style triggers: read structured data from email bodies.
  • RSS: new items in a feed.
  • Formatter, Filter, Paths, Delay and Looping: control and transform data, covered in chapter 4.

Instant or polling?

Where an app offers both, the description tells you. Choose instant for customer-facing speed, polling when no instant version exists. Details are in polling vs instant triggers.

App versions and connectors

An app can have several versions of its connector, and older ones may be deprecated. If you see a notice that a trigger or action is deprecated, plan to migrate. Prefer the maintained version, and check which fields it exposes: a newer version may rename or restructure them, which can break mappings downstream.

Premium and custom apps

Some apps are labeled premium and need an eligible plan. If an app is not in the directory, you can still connect it through its API using webhooks or an API request step (chapter 5), or through a private integration built with Zapier's developer platform.

Triggers that produce many items

Some triggers return one item at a time; others may return a batch inside one run (for example "new emails" bundling several). If a trigger supplies a list, you either handle the first only, or use looping to process each. Know which behaviour you have by testing with more than one record.

A trigger chooser: a stand-in

The code below encodes a few rules of thumb. Give it a description and it suggests a trigger style. It is a toy, but writing rules down is how you learn to choose.

Python Stand-in: trigger chooser

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Preventing double fires

Even a correct trigger can fire twice when:

  • A record is created and then immediately edited by another automation.
  • Two Zaps listen to the same source and each performs an action.
  • A form app sends both a "submitted" and an "updated" event.

You can detect doubles by storing a unique ID somewhere (for example in a Zapier Table or in the target app) and checking it first. The stand-in below shows the check.

Python Stand-in: ignore a record already processed

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Test your trigger properly

  1. Test with a real, recent record in the source app.
  2. Create another record and check the Zap sees it.
  3. Edit an existing record and see whether the trigger fires (and whether you wanted it to).
  4. Check what happens with empty fields and unusual characters.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. You only care when a deal moves to Won. Best choice?

    Pick a trigger that matches the transition, or filter on the exact field.
  2. 2. Why narrow a trigger at the source (a label, a folder, a view)?

    Narrow sources avoid starting runs you will immediately filter out.
  3. 3. An 'Updated' trigger may fire:

    Updates can fire repeatedly; use a filter or a more specific trigger.
  4. 4. An app has no connector. What can you do?

    Webhooks and API request steps connect services that have no ready connector.

Summary

  • Write the trigger as a precise sentence, then pick the matching event.
  • Prefer specific or narrowed triggers; use filters for fine control.
  • New triggers fire once per item; updated triggers can fire repeatedly.
  • Watch app versions, premium apps and batch behavior.
  • Guard against double fires with unique IDs, and test with several real records.

Next: Actions: Create, Update, Search and Find-or-Create