Add Rules to a Firewall in DigitalOcean

What this operation does

Add Rules to a Firewall

• POSTChanges data · Firewallsapi.digitalocean.com/v2/firewalls/{firewall_id}/rules

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which DigitalOcean operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other DigitalOcean operations

• Create a New Domain RecordPOST · changes data
• Create a New AppPOST · changes data
• Create a New TagPOST · changes data
• Create a New VPCPOST · changes data
• Create a New DomainPOST · changes data
• Create a New Block Storage VolumePOST · changes data
• Create a New DropletPOST · changes data
• Create a New Database ClusterPOST · changes data

All 288 DigitalOcean operations

Questions

Can HumDay add rules to a firewall in DigitalOcean?

Yes. This operation is published in DigitalOcean's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my DigitalOcean data?

Yes — this is a POST operation, so it changes something in DigitalOcean. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your DigitalOcean account.

Where this came from

Read from a published API description for DigitalOcean at raw.githubusercontent.com/digitalocean/openapi/main/specification/DigitalOcean-public.v2.y. The description above is the provider’s own wording, not ours. Last published 2023-03-06.