Can HumDay connect to Netlify's documentation?

Yes. HumDay reads Netlify's documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 120 operations are documented.

Do I need to write code to automate Netlify's documentation?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Netlify's documentation account.

What can HumDay do in Netlify's documentation?

66 of the 120 documented operations change something in Netlify's documentation, and 54 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Netlify's documentation account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Netlify's documentation is held behind that approval.

Automate Netlify's documentation

HumDay reads Netlify's documentation’s own published API description and derives 120 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Netlify's documentation is

Netlify is a hosting service for the programmable web. It understands your documents and provides an API to handle atomic deploys of websites, manage form submissions, inject JavaScript snippets, and much more. This is a REST-style API that uses JSON for serialization and OAuth 2 for authentication. This document is an OpenAPI reference for the Netlify API that you can explore. For more detailed i

API host: api.netlify.com

What HumDay can do in Netlify's documentation

66 documented operations change something in Netlify's documentation. The 58 most useful are listed here.

POSTNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./sites
POSTCreates new environment variables./accounts/{account_id}/env
PATCHNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./sites/{site_id}
POSTNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./{account_slug}/sites
PATCHUpdates or creates a new value for an existing environment variable./accounts/{account_id}/env/{key}
PUT[Beta] Unlinks the repo from the site./sites/{site_id}/unlink_repo
DELETEDeletes an environment variable./accounts/{account_id}/env/{key}
PUTUpdates an existing environment variable and all of its values./accounts/{account_id}/env/{key}
DELETEDeletes a specific environment variable value./accounts/{account_id}/env/{key}/value/{id}
PUTUpdate path/deploys/{deploy_id}/files/{path}
POSTUpdate hooks/hooks
POSTUpdate accounts/accounts
POSTUpdate dns zones/dns_zones
POSTUpdate deploy keys/deploy_keys
DELETEDelete hook id/hooks/{hook_id}
PUTUpdate hook id/hooks/{hook_id}
DELETEDelete site id/sites/{site_id}
DELETEDelete deploy id/deploys/{deploy_id}
DELETEDelete zone id/dns_zones/{zone_id}
DELETEDelete key id/deploy_keys/{key_id}
DELETEDelete account id/accounts/{account_id}
PUTUpdate account id/accounts/{account_id}
POSTUpdate members/{account_slug}/members
DELETEDelete form id/sites/{site_id}/forms/{form_id}
DELETEDelete submission id/submissions/{submission_id}
PUTUpdate dns/sites/{site_id}/dns
POSTUpdate ssl/sites/{site_id}/ssl
POSTUpdate log/builds/{build_id}/log
POSTUpdate enable/hooks/{hook_id}/enable
POSTUpdate assets/sites/{site_id}/assets
POSTUpdate builds/sites/{site_id}/builds
POSTUpdate start/builds/{build_id}/start
POSTUpdate deploys/sites/{site_id}/deploys
POSTUpdate lock/deploys/{deploy_id}/lock
PUTUpdate metadata/sites/{site_id}/metadata
PUTUpdate rollback/sites/{site_id}/rollback
POSTUpdate snippets/sites/{site_id}/snippets
POSTUpdate cancel/deploys/{deploy_id}/cancel
POSTUpdate unlock/deploys/{deploy_id}/unlock
POSTUpdate build hooks/sites/{site_id}/build_hooks
PUTUpdate transfer/dns_zones/{zone_id}/transfer
POSTUpdate traffic splits/sites/{site_id}/traffic_splits
POSTUpdate dns records/dns_zones/{zone_id}/dns_records
DELETEDelete member id/{account_slug}/members/{member_id}
PUTUpdate member id/{account_slug}/members/{member_id}
POSTThis is an internal-only endpoint./deploys/{deploy_id}/plugin_runs
DELETEDelete id/sites/{site_id}/build_hooks/{id}
PUTUpdate id/sites/{site_id}/build_hooks/{id}
DELETEDelete asset id/sites/{site_id}/assets/{asset_id}
PUTUpdate asset id/sites/{site_id}/assets/{asset_id}
DELETEDelete deploy id/sites/{site_id}/deploys/{deploy_id}
PUTUpdate deploy id/sites/{site_id}/deploys/{deploy_id}
PUTUpdate name/deploys/{deploy_id}/functions/{name}
DELETEDelete snippet id/sites/{site_id}/snippets/{snippet_id}
PUTUpdate snippet id/sites/{site_id}/snippets/{snippet_id}
PUTUpdate split test id/sites/{site_id}/traffic_splits/{split_test_id}
DELETEDelete dns record id/dns_zones/{zone_id}/dns_records/{dns_record_id}
POSTUpdate tickets/oauth/tickets

What HumDay can read from Netlify's documentation

These are the operations a schedule or a trigger can watch.

GETNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./sites
GETNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./sites/{site_id}
GETNote: Environment variable keys and values will soon be moved from buildsettings.env and repo.env to a new endpoint./{account_slug}/sites
GETReturns all environment variables for an account or site./accounts/{account_id}/env
GETReturns an individual environment variable./accounts/{account_id}/env/{key}
GETRead user/user
GETRead files/sites/{site_id}/files
GETRead file path/sites/{site_id}/files/{file_path}
GETRead hooks/hooks
GETRead accounts/accounts
GETRead dns zones/dns_zones
GETRead services/services/
GETRead deploy keys/deploy_keys
GETRead forms/sites/{site_id}/forms
GETRead types/hooks/types
GETRead types/accounts/types
GETRead hook id/hooks/{hook_id}
GETRead build id/builds/{build_id}
GETRead deploy id/deploys/{deploy_id}
GETRead zone id/dns_zones/{zone_id}
GETRead key id/deploy_keys/{key_id}
GETRead addonName/services/{addonName}
GETRead account id/accounts/{account_id}
GETRead members/{account_slug}/members
GETRead submission id/submissions/{submission_id}
GETRead dns/sites/{site_id}/dns
GETRead ssl/sites/{site_id}/ssl
GETRead assets/sites/{site_id}/assets
GETRead builds/sites/{site_id}/builds
GETRead deploys/sites/{site_id}/deploys
GETRead metadata/sites/{site_id}/metadata
GETRead snippets/sites/{site_id}/snippets
GETRead status/{account_id}/builds/status
GETRead submissions/forms/{form_id}/submissions
GETRead build hooks/sites/{site_id}/build_hooks
GETRead submissions/sites/{site_id}/submissions
GETRead manifest/services/{addonName}/manifest
GETRead traffic splits/sites/{site_id}/traffic_splits
GETRead dns records/dns_zones/{zone_id}/dns_records
GETRead deployed branches/sites/{site_id}/deployed-branches
GETRead service instances/sites/{site_id}/service-instances
GETRead member id/{account_slug}/members/{member_id}

How automating Netlify's documentation works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Netlify's documentation account.
Grant access, then go live. You approve the specific Netlify's documentation operations it may use — and only those.

Popular Netlify's documentation integrations

Connect Netlify's documentation to the tools people pair it with most.