Developer · CONNECTIONManage ShipStatic static-site deployments, labels and custom domains.
Explore 15 workflow actions for ShipStatic, including account permissions and operation limits.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Create a domain, or point it at another deployment, or change its labels.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete a deployment and its files; it is served until cleanup finishes.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Publish workflow files as a new deployment (each file at the site root under its own name); NodeHub computes each file's MD5 from the bytes it sends.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The current account.
A deployment's URL, status, file count, size, labels and password protection.
A domain's linked deployment, status, verification and labels.
Which DNS provider manages the domain.
The DNS records the domain needs at its DNS provider.
The plan's limits: largest file, file count and total size.
The account's audit log.
The account's deployments with their URLs, status and labels.
The account's domains with their linked deployment and verification.
Labels in use across the account.
Every plan on sale with its price and caps.
Replace a deployment's labels (the only thing that can change on a deployment).
A repeated request may repeat the external action. Review the previous result before retrying a write.
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
Inspect step outputs and confirm the result in ShipStatic. A saved workflow is not a completed provider action.
