NETLIFY n8n INTEGRATION: AUTOMATE NETLIFY WITH N8N

The Form Submitted trigger is your go-to solution for capturing lead data and user submissions in real-time. This trigger fires instantly whenever someone submits a form on your Netlify-hosted site, allowing you to route that data anywhere—CRM, email marketing platform, spreadsheet, or notification system.

Configuration parameters:

• Credential to connect with: This dropdown is required and lets you select your authenticated Netlify account. Ensure your credentials are properly set up before configuring this trigger.
• Site Name or ID: A required field where you specify which Netlify site to monitor. You can select from a dropdown of your available sites or enter the site ID directly.
• Event: Set to "Form Submitted" to activate this specific trigger. This is a required dropdown selection.
• Form Name or ID: An optional field that lets you narrow down monitoring to a specific form. Leave empty to capture submissions from all forms on the site.
• Simplify: An optional toggle that, when enabled, streamlines the output data for easier processing in subsequent workflow steps.

Typical use cases:

• Automatically add contact form submissions to HubSpot or Salesforce as new leads
• Send instant Slack notifications to your sales team when high-value forms are submitted
• Push form data to Google Sheets for easy tracking and reporting
• Trigger automated email sequences via Mailchimp or SendGrid

When to use it: This trigger is essential for any site that collects user information. If you're running a marketing site, portfolio with contact forms, or any application with user input, this trigger ensures no submission goes unnoticed.

The Deploy Created trigger activates whenever a new deployment is initiated on your Netlify site. This is the starting point for deployment-aware automations—perfect for tracking build activity, maintaining deployment logs, or kicking off related processes when new code ships.

Configuration parameters:

• Credential to connect with: A required dropdown to select your Netlify account credentials for authentication.
• Site Name or ID: A required field to specify which Netlify site should be monitored for new deployments. This accepts either the site name or its unique identifier.
• Event: Must be set to "Deploy Created" from the required dropdown. Supports both fixed values and dynamic expressions for advanced use cases.

Typical use cases:

• Log every deployment to a Notion database for historical tracking
• Send a Slack message to the team channel announcing "New deployment started for [project]"
• Create a timestamp entry in Google Sheets tracking all build initiations
• Trigger parallel testing workflows in other systems when deployment begins

When to use it: This trigger is valuable for teams that need to track deployment frequency, maintain audit logs, or initiate processes that should run alongside (not after) deployments. It's particularly valuable for teams managing multiple sites who need centralized visibility into build activity.

The Deploy Failed trigger is your safety net for catching build errors before they become bigger problems. This trigger fires immediately when a deployment fails, enabling instant notifications, automatic ticket creation, or any remediation workflow you need.

Configuration parameters:

• Credential to connect with: A required dropdown for selecting your authenticated Netlify account.
• Site Name or ID: A required text input (or dropdown when options load correctly) to specify the monitored Netlify site.
• Event: Set to "Deploy Failed" from the required dropdown. This configuration ensures the trigger only fires on failure events.

Typical use cases:

• Send urgent Slack or Teams notifications to developers when builds fail
• Automatically create GitHub issues with deployment error details
• Generate Jira tickets for the engineering team to investigate
• Trigger SMS alerts via Twilio for critical production sites
• Log failures to a centralized error tracking system like Sentry

When to use it: This trigger is non-negotiable for any production site. Failed deployments can mean broken features, missing content, or complete site downtime. Automate your incident response so your team knows about failures instantly, not hours later when customers start complaining.

The Deploy Building trigger fires when a deployment enters the build phase. This intermediate state trigger is useful for tracking build progress, managing concurrent operations, or simply keeping stakeholders informed about deployment status.

Configuration parameters:

• Credential to connect with: A required dropdown to select your Netlify credentials.
• Site Name or ID: A required field where you specify which site to monitor. Enter the site name or ID directly if the dropdown experiences loading issues.
• Event: Set to "Deploy Building" from the required dropdown, using either fixed selection or expression mode for dynamic configuration.

Typical use cases:

• Update a status dashboard to show "Build in progress" for the relevant project
• Send a brief Slack update: "Building deployment for [site]—ETA 2-3 minutes"
• Pause or queue other automations until the build completes
• Log build start times for performance tracking

When to use it: This trigger is valuable for teams that need granular visibility into deployment pipelines. If you're coordinating multiple systems around deployments or maintaining real-time dashboards, the Deploy Building trigger gives you that intermediate status update before the final success or failure.