Automation Triggers

Overview

Triggers are the backbone of automation in Taskade. They are predefined conditions that, when met, initiate a series of automated actions within. Essentially, they're the "if" part of an "if this, then that" equation, monitoring for specific events or changes.

TL;DR: A trigger is the event that pulls work into an automation, like a new task, a new email, a form submission, or a scheduled time. Taskade offers 82 triggers across 47 built-in and connected apps. When one fires, Taskade pipes the event through filters, branches, and loops, then runs actions across your connected apps.

The Four Categories of Triggers

Taskade triggers fall into four categories. Pick the one that matches where the event originates:

Every trigger in Taskade fits one of these four categories. Once the trigger fires, the Automation v2 engine pipes the event through filters, branches, and loops before dispatching to actions across 100+ integrations.

Test a Trigger to See Its Real Payload

Building filters against a made-up payload almost always misses an edge case. The fastest way to see the real shape is to fire the trigger once and let Taskade replay the latest event.

The trigger step's Inspector: configure the event, then click Test to replay the last real payload before you build filters against it:

┌───────────────────────┬───────────────────────────────────────┐
│  FLOW                 │  INSPECTOR · Trigger                  │
├───────────────────────┼───────────────────────────────────────┤
│  ▸ TRIGGER            │  Project    [ Sales Pipeline  ▾ ]     │
│    Task Added         │  Event      [ Task Added     ▾ ]      │
│       │               │                                       │
│    FILTER ◇           │  ▸ Last trigger payload      Copy     │
│    Status=Won         │    task: { title: Acme,               │
│       │               │           due: 2026-06-09 }           │
│    ACTION             │                                       │
│    Slack msg          │  Test Run                             │
│       │               │  Replay the last real event.          │
│    + Add step         │          [ Test ]                     │
└───────────────────────┴───────────────────────────────────────┘

• Open the automation in the flow editor.
• Click the trigger step. The side panel opens.
• Use the test action to replay the most recent event from the trigger.
• Copy any field from the replayed payload into a Branch or Filter step downstream.

If the trigger has never fired, save the automation and send one real event from the source app. The next test replay pulls that payload in.

Why this matters. Building filters against a real payload catches the surprises before they ship.

Taskade Triggers

💡 Note: Most triggers that aren't marked "Instant" check for new events every 15 minutes. The Schedule trigger is the exception: it runs on the interval you set, as often as every few minutes with the Every X Minutes option.

Calendly Triggers

Slack Triggers

Typeform Triggers

Gmail Triggers

Google Sheets Triggers

Google Forms Triggers

Google Drive Trigger

Webflow Triggers

HubSpot Triggers

YouTube Triggers

RSS Triggers

Discord Triggers

Google Calendar Triggers

GitHub Triggers

Asana Triggers

Notion Triggers

Zoom Triggers

Stripe Triggers

Shopify Triggers

Telegram Bot Triggers

Start automations when events happen in your Telegram chats. Connect your bot via the Bot API Token from @BotFather.

💡 Tip: All Telegram Bot triggers are instant — your automation starts the moment the event occurs. Pair with Telegram Bot actions to build full chatbot workflows.

More triggers

These apps can also start an automation. Open each one for details.

What operators watch for

The trigger is where a real business workflow begins. A few patterns from operators who run their whole business on Taskade:

• E-commerce: a Shopify New Order opens fulfillment, and New Abandoned Checkout starts a win-back email.
• Service business: a Form submission books a job, and Task Due nudges the crew the day before.
• Client portal: a Stripe New Payment unlocks access, and Canceled Subscription revokes it.
• Content team: a Schedule trigger posts the daily roster every morning at 7am with no AI credits.

Pair any trigger with Branch, Filter, and AI actions to decide what happens next.

Frequently Asked Questions

Related guides

• Automation Actions — What runs after a trigger fires
• Automations: Overview — Anatomy of a full automation
• Branch Action — Route based on trigger data
• Filter Data — Gate-keeping triggers
• Loop Action — Process batch events
• Integrations Directory — See which services have triggers