Developer ToolsReal-timeUpdated May 2026

Netlify

Frontend deploys and form submissions from Netlify

Netlify is the frontend-deploy platform built around the Jamstack philosophy, static sites and serverless functions with continuous deployment from Git. Five triggers cover the deploy lifecycle: Deploy Created (a new deploy started), Deploy Building (build is in progress), Deploy Succeeded (live and serving traffic), Deploy Failed (broken, usually the trigger workflows care about most), Form Submission (Netlify Forms received a submission from a site form). Four actions cover deploy management: Trigger Build (kick off a manual deploy), Get Site, List Sites, List Deploys. The integration uses a Netlify personal access token from your user settings. Common patterns: a Deploy Failed pings the on-call channel in Slack with the build log URL and creates a Linear bug for triage; or a Form Submission on the contact form fans into HubSpot, sends a confirmation via SendGrid, and logs to a Notion intake database, bypassing Netlify's default form-notification email entirely.

Connect Netlify See 5 triggers

5triggers

4actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Netlify does.

5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When netlify deploy building

Fires when a deploy enters the building state. For "deploy started → update status page, notify team" workflows.

See what it returns →

Trigger live

When netlify deploy created

Fires when a new deploy is created (queued or building). For comprehensive deploy-history tracking workflows.

See what it returns →

Trigger live

When netlify deploy failed

Fires when a deploy fails. For "post failure log + commit info to engineering Slack" or "alert if main branch deploy fails" critical-failure workflows.

See what it returns →

Trigger live

When netlify deploy succeeded

Fires when a deploy goes live. For "post the deploy URL to Slack", "trigger downstream cache purge", "update status page back to operational" workflows.

See what it returns →

Trigger live

When netlify form submission

Fires when a Netlify Form is submitted. For "static-site form → push to CRM" workflows where you don't want to run a backend just to handle form submissions.

See what it returns →

Actions

Do anything Netlify can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Netlify Site	Returns site metadata — name, URL, build settings, plan, recent activity. Useful for "audit site configuration" workflows.	1 fields	View →
List Netlify Deploys	Paginated deploy history for a specific site with status filter. For deploy-history reporting and for "find last green deploy for rollback" workflows.	1 fields	View →
List Netlify Sites	Returns all sites in the account. Useful for cross-site reporting and for resolving site IDs at workflow setup.	1 fields	View →
Trigger Netlify Build	Manually triggers a build/deploy for a site. For "content changed in CMS → rebuild static site" or "scheduled daily rebuild for fresh data" patterns.	1 fields	View →

Recipes

Pre-built Netlify workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Netlify → Slack alerts

AI-triage every Netlify event, ping the right channel only when it matters.

Netlify → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Netlify → Notion database

Turn Netlify into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Netlify once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Netlify field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Netlify integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Netlify to Tiny Command?

Open the Tiny Command workflow builder, drop in a Netlify node, and click Connect. Authorize Netlify once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Netlify triggers does Tiny Command support?

Tiny Command supports 5 real-time Netlify triggers, including "Netlify Deploy Building", "Netlify Deploy Created", "Netlify Deploy Failed". Each trigger fires within seconds of the event happening in Netlify.

What Netlify actions can I run from a workflow?

4 Netlify actions are available out of the box, covering developer tools operations like "Get Netlify Site". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Netlify integration real-time?

Yes. Netlify Deploy Building and every other Netlify trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Netlify rather than on a polling schedule.

Do I need to write code to use Netlify with Tiny Command?

No. Every Netlify trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Netlify API endpoint directly.

How much does the Netlify integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Netlify integration itself has no per-app surcharge.