Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Netlify

Netlify is a platform for building and deploying websites and apps.

CategoryDeveloper Tools
AuthenticationOAuth 2.0
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Netlify with Flows360

Netlify is a platform for building and deploying websites and apps.

Use the Netlify connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 4 triggers.

Available actions

  • Start Deploy
  • Get Site
  • List Site Deploys
  • List Files

Available triggers

  • New Deploy Started
  • New Deploy Succeeded
  • New Deploy Failed
  • New Form Submission

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Netlify
  • Package: @activepieces/piece-netlify@0.1.6
  • Exact artifact digest: sha256:f579c658e3d2568426c6dd646066ac19205755f35cec154b8e931292111f2323
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Start Deploy (start_deploy), Triggers a new build for a site on Netlify. Supports clearing build cache. Classification: read.
  • Get Site (get_site), Get a specified site. Note: Environment variable keys and values have moved from build_settings.env and repo.env to a new endpoint. Please use getEnvVars to retrieve site environment variables. Classification: read.
  • List Site Deploys (list_site_deploys), Returns a list of all deploys for a specific site. Classification: read.
  • List Files (list_files), Returns a list of all the files in the current deploy. Classification: read.

Trigger contracts

  • New Deploy Started, webhook.
  • New Deploy Succeeded, webhook.
  • New Deploy Failed, webhook.
  • New Form Submission, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects8
Supported actions4
Triggers4

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Start Deploy Yes No Triggers a new build for a site on Netlify. Supports clearing build cache.
Get Site Yes No Get a specified site. Note: Environment variable keys and values have moved from build_settings.env and repo.env to a new endpoint. Please use getEnvVars to retrieve site environment variables.
List Site Deploys Yes No Returns a list of all deploys for a specific site.
List Files Yes No Returns a list of all the files in the current deploy.
New Deploy Started Yes No webhook trigger declared by the pinned package.
New Deploy Succeeded Yes No webhook trigger declared by the pinned package.
New Deploy Failed Yes No webhook trigger declared by the pinned package.
New Form Submission Yes No webhook trigger declared by the pinned package.

Supported actions

Start Deploy · Read

Triggers a new build for a site on Netlify. Supports clearing build cache.

start_deploy · Risk: low · Retry: safe

Inputs

  • siteId · string · Required, Select the site to deploy
  • clearCache · boolean · Optional, Whether to clear the build cache before building
Get Site · Read

Get a specified site. Note: Environment variable keys and values have moved from build_settings.env and repo.env to a new endpoint. Please use getEnvVars to retrieve site environment variables.

get_site · Risk: low · Retry: safe

Inputs

  • siteId · string · Required, Select the site to retrieve information for
List Site Deploys · Read

Returns a list of all deploys for a specific site.

list_site_deploys · Risk: low · Retry: safe

Inputs

  • siteId · string · Required, Select the site to list deploys for
  • page · number · Optional, Page number for pagination (starts from 1)
  • perPage · number · Optional, Number of items per page (max 100)
List Files · Read

Returns a list of all the files in the current deploy.

list_files · Risk: low · Retry: safe

Inputs

  • siteId · string · Required, Select the site to list files for

Triggers

New Deploy Started · Webhook

Fires immediately when a deploy job starts on your Netlify site.

Inputs

  • siteId · string
New Deploy Succeeded · Webhook

Fires when a new site version has successfully deployed.

Inputs

  • siteId · string
New Deploy Failed · Webhook

Fires when a site deploy fails.

Inputs

  • siteId · string
New Form Submission · Webhook

Fires when a Netlify form submission is received.

Inputs

  • siteId · string

Setup

Setup

  1. Add the Netlify connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-netlify@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Netlify connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-netlify@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com