How do I connect Netlify to Lodol?

Authenticate Netlify once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

Netlify

Website BuildersCloud Computing

Host and deploy websites on Netlify. Manage sites and their build settings, trigger deploys with build hooks, check whether the latest deploy succeeded, set environment variables, inject snippets, and read form submissions.

Get Started Browse all integrations

20 actions

Actions

Steps your workflow can run in Netlify.

List sitesList the sites the connected Netlify account can see. Returns each site's name, ID, primary and deploy URLs, plan, team, build settings and its currently published deploy.

Get siteRead one site in full: its name and URLs, custom domain and domain aliases, team, build command and publish directory, SSL settings, and the deploy currently published on it.

Create siteCreate a Netlify site. The name becomes its netlify.app subdomain and must be unique across all of Netlify; leave it empty to let Netlify invent one.

Update siteChange a site's settings: rename it, set or clear its custom domain and domain aliases, put it behind a password, change where build notifications go, force HTTPS, or change the build command, publish directory and functions directory. Only the fields you fill in are sent; the rest are left alone.

Delete siteDelete a site permanently, along with every deploy, form submission and environment variable belonging to it. This cannot be undone, and the site's netlify.app subdomain becomes available for anyone to claim.

List site deploysList a site's deploys, newest first. Each one reports its state ('ready', 'building', 'error' and so on), the branch and commit it came from, its own preview URL, when it was created and published, and the error message if it failed.

List build hooksList a site's build hooks. Each one carries the URL that triggers a deploy of its branch when something POSTs to it, with no credentials needed.

Create build hookCreate a build hook and return its URL. POSTing to that URL rebuilds and redeploys the site with no credentials, which is how a workflow triggers a Netlify deploy: create the hook once, then call its URL whenever the content it publishes changes.

Update build hookRename a build hook or point it at a different branch. The hook's URL does not change, so anything already calling it keeps working and starts building the new branch.

Delete build hookDelete a build hook. Its URL stops working immediately, so anything still calling it will start failing.

List site snippetsList the HTML snippets Netlify injects into this site's pages after each deploy - analytics tags, chat widgets and the like - with the code each one injects and where it goes.

Create site snippetInject HTML into this site's pages without redeploying it - an analytics tag, a chat widget, a meta tag. 'Code' goes into every page; 'Thank-you page code' goes only into the page a form submission lands on.

Update site snippetChange an injected snippet - its code, where that code goes, or its name. Only the fields you fill in are sent.

Delete site snippetStop injecting a snippet and remove it. The code disappears from the site's pages on the next deploy.

List environment variablesList a team's environment variables, or one site's when you pick a site. Each one reports its value per deploy context, which parts of the pipeline can read it, and who changed it last.

Create environment variableCreate an environment variable for a team, or for one site when you pick a site. Set which deploy contexts the value applies to and which parts of the build can read it.

Set environment variable valueChange an existing variable's value for one deploy context, leaving its other contexts alone. The variable must already exist.

Delete environment variableDelete an environment variable and every deploy-context value it holds. Builds after this one will not see it, which will break anything that reads it.

List site formsList the forms Netlify detected in this site's deployed HTML, with each form's name, the paths it appears on, the fields it collects and how many submissions it has received. A form only appears here after a deploy that contains it.

List form submissionsList every submission across all of a site's forms, newest first. Each one carries the submitter's name, email and company where Netlify recognised those fields, and the whole submitted payload under 'data'.