Trigger

A trigger is the event that starts an automated workflow — the "when this happens" half of every automation, no-code or otherwise. Every workflow automation platform (Zapier, Make, n8n) and every visual programming environment structures automations around at least one trigger, which then fans out into one or more actions. Why it matters: choosing and configuring the right trigger correctly is the single most common source of automation bugs for no-code builders — a trigger that fires too often (e.g., on every field update instead of only on record creation) causes duplicate actions and wasted API calls; a trigger that's polling-based instead of webhook-based introduces delay that can break time-sensitive flows (e.g., a "send welcome email" automation that fires 15 minutes after signup instead of instantly). How it works: triggers fall into three broad categories. (1) Instant/webhook triggers: the source app pushes data the moment an event occurs (near-zero latency, most reliable, requires the source app to support webhooks). (2) Polling triggers: the automation platform checks the source app on an interval (every 1, 5, or 15 minutes depending on plan) for new or changed data — used when the source app has no webhook support, e.g., many "New Row in Google Sheets" triggers poll rather than push. (3) Scheduled triggers: the automation runs on a fixed cadence regardless of external events (e.g., "every day at 9am," "every Monday") — used for digest emails, weekly reports, or batch cleanup jobs, implemented via cron-style scheduling under the hood. Worked example — comparing trigger types for the same goal (notify sales when a big deal closes): a webhook trigger on "Deal Stage Changed to Closed Won" in a CRM's API fires within seconds of the change; a polling trigger checking the CRM every 15 minutes for closed deals could delay the Slack notification by up to 15 minutes; a scheduled trigger running "every morning at 8am, fetch all deals closed yesterday" batches the notification into a daily digest instead of a real-time alert — the same underlying event, three very different builder decisions depending on how urgent the response needs to be. Well-designed no-code platforms let you see which trigger type an integration uses before you build around it, since instant triggers are usually preferable whenever available. Some platforms also support manual triggers (a human clicks "run now" rather than any automated event firing) — useful for automations a person wants to kick off deliberately, like a one-off bulk data cleanup, rather than something that should run continuously in the background.