Menu

Mattering Automations DigitalOcean integration

Connect DigitalOcean to Mattering Automations: droplets, block storage volumes, DNS, App Platform deployments, managed database housekeeping, Spaces access keys, snapshots, and tags as workflow steps, authenticated with a single personal access token.

The Mattering Automations DigitalOcean integration adds the DigitalOcean v2 REST API to your automation canvas: manage the droplet lifecycle from create through reboot, power, resize, snapshot, and destroy, attach and detach block storage volumes, keep DNS zones and records current, trigger App Platform deployments and read their logs, manage databases and users inside existing managed clusters, issue Spaces access keys, read load balancers, firewalls, and monitoring alert policies, and organize everything with projects and tags.

The credential is one personal access token, sent as a bearer token on every request. Tokens are generated in the DigitalOcean control panel, carry the dop_v1_ prefix, are shown exactly once, and can be scoped from full access down to per-resource read and write grants. Setup takes a few minutes once you have the token, and this guide walks through each step and ends with the full node reference.

The safety modeling is stated on the nodes rather than buried. Of the 55 nodes, 28 read and 27 act, and four of those carry a destructive flag: DigitalOcean: Delete Droplet, DigitalOcean: Delete Volume, DigitalOcean: Delete Domain, and DigitalOcean: Delete Snapshot, all permanent with no trash and no restore. Database cluster create and destroy are deliberately not nodes at all, and firewall and load balancer writes did not ship either. Nodes that start billing, like DigitalOcean: Create Droplet and DigitalOcean: Create Volume, say so in plain words, and powering a droplet off does not stop its billing.

Before you start

  • A DigitalOcean account you can sign in to at cloud.digitalocean.com, with access to the API section of the control panel to generate a personal access token.
  • A Mattering workspace with access to the Automations app.
  • Nothing to spend for setup and verification: every query node in this integration is a free read against resources you already have. The write nodes create real resources that DigitalOcean bills for, so treat them as production actions from the first test.
  • For the App Platform nodes, at least one existing app; for the database nodes, at least one existing managed cluster. The integration manages databases and users inside a cluster but deliberately does not create or destroy clusters themselves.

Create a DigitalOcean personal access token

Mattering authenticates to DigitalOcean with a bearer token: every request carries your personal access token in the Authorization header. Tokens are created in the control panel's API section, are shown exactly once, and carry scopes chosen at creation, from full access down to per-resource grants like droplet:read. The credential in Mattering is the single token value, nothing else.

Sign in at cloud.digitalocean.com and open API in the left navigation, then the Tokens tab (cloud.digitalocean.com/account/api/tokens).
Click Generate New Token, give the token a name your team will recognize, and choose an expiration.
Choose the token's access. Full Access covers all 55 nodes; Custom Scopes narrows the token to exactly what a workflow does, for example droplet and snapshot read scopes for a reporting sweep that should never be able to write.
Click Generate Token and copy the value straight away. It starts with dop_v1_ and DigitalOcean shows it once.
The token value is displayed exactly once, at creation. If it is lost, there is nothing to reveal later: generate a new token and update the credential. Treat the value like a password; a full-access token can destroy droplets, volumes, domains, and snapshots.
Scopes are fixed when the token is created. A read-only token passes the connection test and runs all 28 query nodes, but returns 403 on every write node. Widening access means creating a new token, not editing the old one.
If you set an expiration, every node starts returning 401 on that date with no warning inside Mattering. Note the date somewhere the team will see it, and rotate the credential before it lapses.

Connect DigitalOcean to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose DigitalOcean from the list.
Click Create new credential and paste the personal access token. It is a single token field: no username, no email.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls DigitalOcean's account endpoint and confirms the token authenticates. A 200 proves the connection; a 401 means the token is wrong, revoked, or expired.
Click Connect. All 55 DigitalOcean nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a DigitalOcean section should list the query and action nodes. Drop DigitalOcean: Get Account onto the canvas and run a test step. It takes no parameters and is the connector's auth probe: a successful response returns the account's email, team, droplet limit, and status, and proves the token is right. Follow it with DigitalOcean: Get Balance to see month-to-date usage in USD, which is also the number a spend-guard step checks before anything that creates billable infrastructure.

Next, run DigitalOcean: List Regions and DigitalOcean: List Sizes. They are the lookup tables the create and resize nodes depend on: region slugs like nyc3 and size slugs with their vCPUs, memory, and authoritative hourly and monthly prices. Then DigitalOcean: List Droplets confirms resource-level access on a real account. Everything in this verify path is read-only and free: it cannot reach the four destructive nodes and it cannot start any billing, so it is safe to re-run whenever you rotate the token.

Node reference

55 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 28

DigitalOcean: Get Account

digitalocean_get_account

Return the authenticated DigitalOcean account: email, name, team, droplet limit, and status. Zero-parameter Safe Read, so it doubles as the credential health check: 401 means the token is wrong or revoked, 200 proves the connection.

DigitalOcean: Get Action

digitalocean_get_action

Fetch one action (an async operation such as a reboot, snapshot, or resize) by ID and read its status: in-progress, completed, or errored. Droplet and volume action nodes return an action ID; poll this node to know when the operation actually finished.

DigitalOcean: Get App

digitalocean_get_app

Fetch one App Platform app by ID: full spec (services, envs, region), live URL, and the active or in-progress deployment with its phase.

DigitalOcean: Get App Logs

digitalocean_get_app_logs

Retrieve the aggregate logs of an app's active deployment. The response contains URLs, not raw log text: live_url streams current logs and historic_urls point at archived logs - fetch them with an HTTP Request node. type BUILD returns build logs of the currently served deployment.

DigitalOcean: Get Balance

digitalocean_get_balance

Return the account's current billing balance: month-to-date usage, month-to-date balance, and outstanding account balance in USD. Useful as a spend guard before nodes that create billable infrastructure.

DigitalOcean: Get Database Cluster

digitalocean_get_database_cluster

Fetch one managed database cluster by UUID: engine, version, node count, region, status, database names, and connection details (host, port, user, SSL).

DigitalOcean: Get Droplet

digitalocean_get_droplet

Fetch one droplet by ID: status (new, active, off, archive), public and private IPs, size, image, region, attached volumes, and tags.

DigitalOcean: Get Firewall

digitalocean_get_firewall

Fetch one cloud firewall by UUID: full inbound and outbound rule sets, status, and the droplets and tags it protects.

DigitalOcean: Get Load Balancer

digitalocean_get_load_balancer

Fetch one load balancer by UUID: IP, status, algorithm, forwarding rules, health check, sticky sessions, and the droplets behind it.

DigitalOcean: List Apps

digitalocean_list_apps

List App Platform apps with their spec, live URL, active deployment, region, and tier.

DigitalOcean: List DNS Records

digitalocean_list_dns_records

List the DNS records of a managed domain, with each record's ID (needed by the update and delete nodes). Filter by fully qualified name and/or record type.

DigitalOcean: List Database Clusters

digitalocean_list_database_clusters

List managed database clusters (PostgreSQL, MySQL, Caching/Valkey, MongoDB, Kafka, OpenSearch) with engine, version, size, status, and connection details. Cluster create and destroy are deliberately not offered as nodes; manage cluster lifecycle in the control panel.

DigitalOcean: List Database Users

digitalocean_list_database_users

List the users of a database cluster with role and connection password. Note the response includes each user's password - treat this node's output as sensitive. Not supported on Caching/Valkey clusters.

DigitalOcean: List Databases In Cluster

digitalocean_list_databases

List the logical databases inside a cluster. Not supported on Caching/Valkey clusters (the API returns an error there).

DigitalOcean: List Domains

digitalocean_list_domains

List the domains managed in DigitalOcean DNS, each with its TTL and full zone file.

DigitalOcean: List Droplets

digitalocean_list_droplets

List all droplets (virtual machines) on the account with status, IPs, size, region, image, and tags. Filter by exact name or by tag. By default only non-GPU droplets are returned; set type to gpus for GPU droplets.

DigitalOcean: List Firewalls

digitalocean_list_firewalls

List cloud firewalls with inbound/outbound rules and the droplets and tags each applies to.

DigitalOcean: List Images

digitalocean_list_images

List OS images usable for creating or rebuilding droplets: distribution images (Ubuntu, Debian, Fedora...), Marketplace application images, and the account's own snapshots and custom images (set private to true for those).

DigitalOcean: List Load Balancers

digitalocean_list_load_balancers

List load balancers with IP, status, forwarding rules, health check settings, and attached droplets.

DigitalOcean: List Monitoring Alerts

digitalocean_list_monitoring_alerts

List the account's monitoring alert policies: metric type (CPU, memory, disk, bandwidth), threshold, window, the droplets or tags covered, and where alerts are sent (email/Slack). Requires the metrics agent (monitoring true) on the covered droplets.

DigitalOcean: List Projects

digitalocean_list_projects

List the account's projects (the organizational folders resources live in), including which is the default.

DigitalOcean: List Regions

digitalocean_list_regions

List all DigitalOcean datacenter regions with their slugs (nyc3, sfo3, ams3...), availability, supported features, and which droplet sizes each offers. Use the slug in create nodes.

DigitalOcean: List SSH Keys

digitalocean_list_ssh_keys

List the SSH public keys stored on the account, with the ID and fingerprint used when embedding a key into a new droplet.

DigitalOcean: List Sizes

digitalocean_list_sizes

List all droplet size slugs with vCPUs, memory, disk, transfer allowance, hourly and monthly price, and the regions where each is available. The authoritative price check before creating or resizing a droplet.

DigitalOcean: List Snapshots

digitalocean_list_snapshots

List all snapshots on the account (droplet and volume), with size, source resource, and regions. Snapshots bill monthly per GiB until deleted.

DigitalOcean: List Spaces Keys

digitalocean_list_spaces_keys

List Spaces (S3-compatible object storage) access keys with their per-bucket permission grants. Secret keys are never included - they are only shown once at creation.

DigitalOcean: List Tags

digitalocean_list_tags

List the account's tags with a count of resources carrying each. Tags drive fleet operations: droplet list filtering, firewall targeting, and alert policy scoping.

DigitalOcean: List Volumes

digitalocean_list_volumes

List block storage volumes with size, region, filesystem, and which droplet (if any) each is attached to. Filter by exact name and/or region.

Action nodes 27

DigitalOcean: Assign Resources To Project

digitalocean_assign_project_resources

Move resources into a project using their URNs (uniform resource names). Purely organizational - nothing is modified or restarted. Reversible by assigning the resources to another project.

DigitalOcean: Attach Volume

digitalocean_attach_volume

Attach a block storage volume to a droplet in the same region. A volume attaches to one droplet at a time (up to 15 volumes per droplet); pre-formatted volumes auto-mount on supported images. Reversed by DigitalOcean: Detach Volume. Poll DigitalOcean: Get Action for completion.

DigitalOcean: Create App Deployment

digitalocean_create_app_deployment

Trigger a new deployment of an App Platform app, pulling the latest changes from its source repository - the redeploy button as a node. Poll the returned deployment via DigitalOcean: Get App until phase is ACTIVE; App Platform keeps serving the previous deployment if the new one fails, and a rollback path exists in the vendor UI.

DigitalOcean: Create DNS Record

digitalocean_create_dns_record

Create a DNS record on a managed domain. Changes go live on DigitalOcean's nameservers within seconds, propagating per TTL. Reversed by DigitalOcean: Delete DNS Record.

DigitalOcean: Create Database In Cluster

digitalocean_create_database

Create a new empty logical database inside an existing cluster (no extra cost - it shares the cluster's resources). Not supported on Caching/Valkey clusters. Reversible by dropping the database.

DigitalOcean: Create Database User

digitalocean_create_database_user

Create a database user in a cluster. The response includes the user's randomly generated password - capture it downstream and treat the output as sensitive. Engine options (for example PostgreSQL pg_allow_replication or MongoDB roles) go in the settings object. Not supported on Caching/Valkey clusters. Reversible by deleting the user.

DigitalOcean: Create Domain

digitalocean_create_domain

Add a domain to DigitalOcean DNS management. This creates the DNS zone only - it does not register the domain, and the registrar must point the domain at DigitalOcean's nameservers (ns1/ns2/ns3.digitalocean.com) for records to resolve. Reversed by DigitalOcean: Delete Domain.

DigitalOcean: Create Droplet

digitalocean_create_droplet

Create a new droplet (virtual machine). BILLING STARTS IMMEDIATELY, per second with a 60-second minimum, capped at the chosen size's monthly price, and continues until the droplet is destroyed - powering off does NOT stop billing. The 202 response means the create was accepted; poll DigitalOcean: Get Droplet until status is active. Reversed by DigitalOcean: Delete Droplet.

DigitalOcean: Create SSH Key

digitalocean_create_ssh_key

Store a new SSH public key on the account so it can be embedded into droplets at create time. Reversed by DigitalOcean: Delete SSH Key.

DigitalOcean: Create Spaces Key

digitalocean_create_spaces_key

Create a Spaces access key, optionally scoped to specific buckets. The response contains the secret_key EXACTLY ONCE - it can never be retrieved again, so store it immediately and treat this node's output as highly sensitive. A fullaccess grant overrides any scoped grants in the same key. Reversible by deleting the key in the control panel or API.

DigitalOcean: Create Tag

digitalocean_create_tag

Create a new tag (it starts attached to nothing). Tag names take letters, numbers, colons, dashes, and underscores. Reversible by deleting the tag.

DigitalOcean: Create Volume

digitalocean_create_volume

Create a block storage volume. BILLING STARTS IMMEDIATELY at the per-GiB monthly rate and continues until the volume is deleted. Volumes can only be resized upwards later (max 16 TiB). Reversed by DigitalOcean: Delete Volume.

DigitalOcean: Delete DNS Record

digitalocean_delete_dns_record

Delete one DNS record from a managed domain. Whatever the record pointed at stops resolving once caches expire. Reversible by recreating the record with the same values (capture them from DigitalOcean: List DNS Records first).

DigitalOcean: Delete Domain

digitalocean_delete_domain

PERMANENTLY DELETE a domain from DigitalOcean DNS, DESTROYING ALL OF ITS DNS RECORDS at once. If the domain's nameservers point at DigitalOcean, everything under it stops resolving immediately. Export the zone (DigitalOcean: List Domains includes zone_file) before deleting.

DigitalOcean: Delete Droplet

digitalocean_delete_droplet

PERMANENTLY DESTROY a droplet. The virtual machine and all data on its local disk are deleted with no trash and no restore - only separately taken snapshots or backups survive. Billing for the droplet stops. A 204 response means the destroy was accepted.

DigitalOcean: Delete SSH Key

digitalocean_delete_ssh_key

Remove an SSH key from the account. Existing droplets keep the key in their authorized_keys; only future droplet creates are affected. Reversible by re-adding the same public key.

DigitalOcean: Delete Snapshot

digitalocean_delete_snapshot

PERMANENTLY DELETE a snapshot. The saved disk image is gone for good - it cannot be restored and can no longer seed new droplets or volumes. The source droplet/volume itself is not touched. Billing for the snapshot stops.

DigitalOcean: Delete Volume

digitalocean_delete_volume

PERMANENTLY DELETE a block storage volume and all data on it. There is no trash and no restore - only separately taken volume snapshots survive. Detach the volume from any droplet first. Billing for the volume stops.

DigitalOcean: Detach Volume

digitalocean_detach_volume

Detach a block storage volume from a droplet. Unmount the filesystem inside the droplet first to avoid data loss on in-flight writes. The volume and its data persist (and keep billing) after detach. Reversed by DigitalOcean: Attach Volume.

DigitalOcean: Power Off Droplet

digitalocean_power_off_droplet

HARD power off a droplet. Per the vendor docs this is similar to cutting the power on a physical server and could lead to complications (unflushed writes may be lost); prefer a graceful shutdown from inside the machine when possible. Note a powered-off droplet still bills. Reversed by DigitalOcean: Power On Droplet.

DigitalOcean: Power On Droplet

digitalocean_power_on_droplet

Power on a droplet that is currently off. Returns an action object; poll DigitalOcean: Get Action until status is completed.

DigitalOcean: Reboot Droplet

digitalocean_reboot_droplet

Gracefully reboot a droplet, like running the reboot command from its console. Returns an action object; poll DigitalOcean: Get Action until status is completed.

DigitalOcean: Rename SSH Key

digitalocean_update_ssh_key

Rename a stored SSH key. Only the display name can change; the key material itself is immutable.

DigitalOcean: Resize Droplet

digitalocean_resize_droplet

Resize a droplet to a different size slug, which CHANGES ITS PRICE. The droplet must be powered off first. With disk false (the default) only CPU and RAM change and the resize is reversible; with disk true the disk grows too and the resize is PERMANENT - a disk can never be shrunk back. Poll DigitalOcean: Get Action until completed, then power on.

DigitalOcean: Snapshot Droplet

digitalocean_snapshot_droplet

Take a full-disk snapshot of a droplet. Snapshots are stored at a low monthly per-GiB rate until deleted, and can be used as the image for new droplets. The snapshot can take several minutes; poll DigitalOcean: Get Action. Reversed by DigitalOcean: Delete Snapshot.

DigitalOcean: Tag Resources

digitalocean_tag_resources

Attach an existing tag to one or more resources. Tagging changes nothing about the resources themselves, but note that tag-scoped firewalls and alert policies start applying to newly tagged droplets immediately. Reversible by untagging (the API's untag endpoint, via an HTTP Request node if needed).

DigitalOcean: Update DNS Record

digitalocean_update_dns_record

Update an existing DNS record. Only the fields filled in are changed; the classic dynamic-DNS move is updating an A record's data to a new IP. Reversible by setting the previous values back.

Using the integration

On the automation canvas

DigitalOcean nodes chain with every other node on the platform: a nightly sweep can run DigitalOcean: Snapshot Droplet across a tagged fleet and open a Mattering Productivity task if an action fails, a morning report can combine DigitalOcean: Get Balance with DigitalOcean: List Droplets and DigitalOcean: List Volumes into a spend summary in a Mattering database, and DigitalOcean: List Monitoring Alerts documents what the alerting actually covers. DigitalOcean: List Tags and DigitalOcean: Tag Resources keep the fleet organized so every later sweep can filter by tag.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can use them. An assistant can answer what is running and what it costs from DigitalOcean: List Droplets and DigitalOcean: Get Balance, point a record somewhere new with DigitalOcean: Update DNS Record, or trigger a redeploy with DigitalOcean: Create App Deployment. DigitalOcean also ships an official MCP server aimed at chat-driven account management; this integration differs by running the same operations as scheduled workflow steps with results landing in Mattering apps. The read nodes are the safest surface to hand an agent; keep the four destructive nodes behind a human step.

The droplet lifecycle, with billing stated plainly

DigitalOcean: Create Droplet starts billing immediately, per second with a 60-second minimum, capped at the size's monthly price, and its 202 response means accepted, not running: poll DigitalOcean: Get Droplet until the status is active. DigitalOcean: Reboot Droplet is the graceful restart, DigitalOcean: Power Off Droplet is a hard stop the vendor compares to cutting the power, and a powered-off droplet still bills; DigitalOcean: Power On Droplet brings it back. DigitalOcean: Resize Droplet changes the price, requires the droplet off first, and is reversible only while disk stays false: growing the disk is permanent. DigitalOcean: Delete Droplet is the flagged, permanent end of the line, and the only thing that stops the billing.

DNS without the control panel

DigitalOcean: List Domains shows every managed zone with its full zone file, and DigitalOcean: Create Domain adds one, creating the DNS zone only: the registrar must point the domain at ns1, ns2, and ns3.digitalocean.com before records resolve. DigitalOcean: List DNS Records finds a record and the ID the write nodes need, DigitalOcean: Create DNS Record and DigitalOcean: Update DNS Record go live on DigitalOcean's nameservers within seconds, and DigitalOcean: Delete DNS Record is recoverable if you captured the record's values first. DigitalOcean: Delete Domain is a different class entirely: it destroys every record in the zone at once, which is why it is flagged destructive and why exporting the zone file first is the rule.

App Platform redeploys and logs

DigitalOcean: List Apps and DigitalOcean: Get App read each app's spec, live URL, and deployment phase. DigitalOcean: Create App Deployment is the redeploy button as a node: it pulls the latest source and builds, and App Platform keeps serving the previous deployment if the new one fails. Poll DigitalOcean: Get App until the phase is ACTIVE. DigitalOcean: Get App Logs returns URLs rather than raw text: live_url streams current logs and historic_urls point at archives, so fetch them with an HTTP Request node when a workflow needs the contents.

What is deliberately read-only or absent

Load balancers and firewalls ship as reads only: DigitalOcean: List Load Balancers, DigitalOcean: Get Load Balancer, DigitalOcean: List Firewalls, and DigitalOcean: Get Firewall audit the configuration, but a wrong firewall write can lock out SSH fleet-wide, so writes stayed off the canvas. Database cluster create and destroy are not nodes: DigitalOcean: List Database Clusters and DigitalOcean: Get Database Cluster read them, and DigitalOcean: Create Database In Cluster, DigitalOcean: Create Database User, DigitalOcean: List Databases In Cluster, and DigitalOcean: List Database Users work inside them, with the vendor's own limitation that database and user management is unsupported on Caching and Valkey clusters. DigitalOcean: Create Spaces Key returns its secret exactly once, and key deletion stays in the control panel. Kubernetes, container registry, certificates, VPCs, and reserved IPs are out of scope for this version.

Troubleshooting

Test Connection fails with a 401
The token is wrong, revoked, or expired. DigitalOcean shows a token's value exactly once at creation, so a token pasted from an old note may be one that was later regenerated or deleted; there is no way to re-reveal it. Generate a new personal access token under API in the control panel, update the credential, and re-run Test Connection. Expired tokens fail the same way: if the token was created with an expiration, every request 401s from that date.
Query nodes work but write nodes return 403
The token is scoped read-only, or is missing the write scopes for that resource. DigitalOcean token scopes mirror create, read, update, and delete per resource and are fixed at creation, so the connection test and all 28 query nodes can pass while DigitalOcean: Create Droplet or DigitalOcean: Update DNS Record is refused. Create a new token with Full Access, or with the write scopes the workflow actually uses, and update the credential.
DigitalOcean: Create Droplet fails with a 422
The request references a size, image, or region combination DigitalOcean cannot satisfy: a size slug not offered in the chosen region, a mistyped image slug, or a region that is not currently available. Build the request from live lookups instead of memory: DigitalOcean: List Regions shows which sizes each region offers, DigitalOcean: List Sizes shows availability per size, and DigitalOcean: List Images returns valid distribution, Marketplace, and custom image slugs.
A droplet or action node returned success but the work is not done
The API is asynchronous for anything that takes real time. DigitalOcean: Create Droplet returns 202 when the create is accepted, so poll DigitalOcean: Get Droplet until the status is active before connecting to it. Reboot, power, snapshot, resize, attach, and detach return an action object instead: poll DigitalOcean: Get Action with the returned ID until its status is completed, and treat errored as a real failure rather than retrying blind.
Database nodes fail on a Caching or Valkey cluster
That is a DigitalOcean limitation, not a credential problem. Database and user management is unsupported on Caching and Valkey clusters, so DigitalOcean: List Databases In Cluster, DigitalOcean: Create Database In Cluster, DigitalOcean: List Database Users, and DigitalOcean: Create Database User return errors there. Use those nodes with PostgreSQL, MySQL, MongoDB, Kafka, and OpenSearch clusters, and manage Caching and Valkey clusters in the control panel.
DigitalOcean: Delete Volume fails while the volume is in use
A volume cannot be deleted while attached to a droplet. Run DigitalOcean: Detach Volume first, and before that, unmount the filesystem inside the droplet so in-flight writes are not lost. Once detached, the delete succeeds; remember it is flagged destructive because the volume's data has no trash and no restore, and only separately taken snapshots survive.
A domain was added but nothing resolves
DigitalOcean: Create Domain creates the DNS zone inside DigitalOcean only; it does not register the domain and it does not change where the domain points. At the registrar, set the domain's nameservers to ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com. Until that change propagates, records created with DigitalOcean: Create DNS Record exist in the zone but no resolver asks DigitalOcean for them.
Nodes intermittently return status_code 429
DigitalOcean enforces 5,000 requests per hour and 250 requests per minute per token, and returns 429 when either window is exceeded, with ratelimit-limit, ratelimit-remaining, and ratelimit-reset headers on every response. Spread scheduled sweeps out rather than firing them together, and reduce the call count: list endpoints accept per_page up to 200, so one wide page replaces ten narrow ones. The reset header is a Unix timestamp a wait step can use before retrying.
A powered-off droplet is still accruing charges
That is DigitalOcean's billing model: a powered-off droplet keeps its disk, IP, and reserved capacity, and continues to bill. DigitalOcean: Power Off Droplet stops the machine, not the meter. If the goal is to stop paying, snapshot the droplet with DigitalOcean: Snapshot Droplet, then destroy it with DigitalOcean: Delete Droplet; the snapshot bills by stored GiB, which is far less than the droplet, and can seed an identical replacement later.
The secret for a Spaces key is nowhere to be found
Spaces secret keys are returned exactly once, in the response of DigitalOcean: Create Spaces Key, and never again: DigitalOcean: List Spaces Keys deliberately returns grants and access key IDs without secrets. If the secret was not captured from the create response, the key is unrecoverable; create a new key, store the secret immediately in a secrets manager, and revoke the old key in the control panel.

DigitalOcean is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products