Every blockd automation has two parts: a trigger (what kicks it off) and an action (what it does). This guide walks through every trigger blockd supports, with examples of when to use each.

Schedule triggers

Run an automation on a recurring schedule — every minute, hourly, daily, weekly, or custom cron. Example: "Every weekday at 8am, email me a summary of yesterday's closed pull requests." Great for digests, reports, and anything time-based.

Event triggers

Fire when something happens in one of your connected apps — a new email, a Slack mention, a Stripe charge, a GitHub PR, a Notion row. Example: "When someone mentions me in Slack, check if the message contains a question mark, and if so, draft a reply." Great for real-time reactions.

Webhook triggers

Give your automation a URL. Anything that POSTs to that URL fires it. Example: a Typeform submission, a custom app event, a GitHub webhook. Use this when blockd doesn't have a native integration yet — any HTTP-capable service works.

Every trigger can have filters (only fire if X), and every automation can chain multiple actions. You don't configure any of this — you just describe it. blockd's AI picks the right trigger, wires up the conditions, and generates the run plan.