Netlify Trigger

Triggers on Netlify deploy events and form submissions

Overview

Receives webhook notifications from Netlify when deploy lifecycle events or form submissions occur. Supports deploy_created, deploy_building, deploy_failed, and submission_created events. The trigger registers a notification hook on the specified Netlify site via the Netlify API, which sends POST requests to the webhook URL when the selected event fires. For form submissions, you can optionally scope to a specific form or listen to all forms. The Simplify option for form submissions returns only the form field data instead of the full payload. Useful for CI/CD automation, deploy status notifications, deployment failure alerts, and capturing form submissions from Netlify-hosted sites.

Category: Development
Tool Name: netlify_trigger
Version: 1

Appearance: Icon: si-netlify | Color: #00c7b7

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Netlify credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Site	string	Yes	—	The Netlify Site ID to monitor for events. Find this in your Netlify site settings under General > Site details.
Event	options	Yes	—	The Netlify event type to listen for.
				Options: deployBuilding, deployCreated, deployFailed, submissionCreated (Form Submitted)
Form	string	Yes	*	The Netlify form ID to listen for submissions on. Use ”*” for all forms, or enter a specific form ID. (shown when Event is submissionCreated)
Simplify	boolean	No	true	Whether to return a simplified version of the response instead of the raw data. When enabled, only the form field data is returned. (shown when Event is submissionCreated)

Output Data

Each Netlify notification produces one output item:

• _trigger — always netlify_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the Netlify event name: deploy_building, deploy_created, deploy_failed or submission_created

The Netlify payload is merged in at the top level, so deploy notifications expose the deploy’s own fields (id, site, state, branch, URLs, timestamps) directly on the item. For form submissions with Simplify turned on, only the submission’s form-field data is merged in instead of the full payload. Reference the result downstream by expression, e.g. {{ $json.state }} for a deploy or {{ $json.email }} for a simplified form submission.

Usage Examples

• Start a workflow when a Netlify deploy is created
• Send a Slack notification when a Netlify deploy fails
• Trigger a follow-up action when a Netlify deploy starts building
• Capture form submissions from a Netlify-hosted site and save to a database

Example Configuration

Alert on failed deploys:

{
  "type": "netlify_trigger",
  "parameters": {
    "siteId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "event": "deployFailed"
  }
}

Track successful deploy creation:

{
  "type": "netlify_trigger",
  "parameters": {
    "siteId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "event": "deployCreated"
  }
}

Capture one form’s submissions as plain field data:

{
  "type": "netlify_trigger",
  "parameters": {
    "siteId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "event": "submissionCreated",
    "formId": "contact-form",
    "simple": true
  }
}

Capture every form on the site with the full webhook payload:

{
  "type": "netlify_trigger",
  "parameters": {
    "siteId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "event": "submissionCreated",
    "formId": "*",
    "simple": false
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when Netlify sends a webhook for a deploy lifecycle event or form submission. Select the Netlify site to monitor and the event type to listen for. For form submissions, optionally scope to a specific form or use “All Forms”. Enable Simplify for form submissions to receive only form field key-value pairs instead of the full payload.