feat: add DigitalOcean integration with droplet trigger and action by aldoabellto235 · Pull Request #2983 · superplanehq/superplane

aldoabellto235 · 2026-02-09T15:48:13Z

Summary

Adds a new DigitalOcean integration to SuperPlane, connecting to the
DigitalOcean API via Personal Access Token authentication.

Trigger: On Droplet Event — polls the DigitalOcean Actions API every
60s for droplet lifecycle events (create, destroy, power_on, power_off,
shutdown, reboot, snapshot, rebuild, resize, rename)
Action: Create Droplet — provisions a new droplet with selectable
region, size, and image from the user's account; returns droplet ID, IP
address, and status
Includes hostname validation on the droplet name field to prevent invalid
characters before hitting the API
Frontend mappers for trigger/component rendering, DigitalOcean icon, and
display name registration

Changes

Backend (`pkg/integrations/digitalocean/`)

File	Purpose
`digitalocean.go`	Base integration: auth, Sync via `GET /v2/account`,
ListResources for region/size/image
`client.go`	HTTP client (Bearer token) with methods for account,
regions, sizes, images, droplets, actions
`on_droplet_event.go`	Polling trigger using `ScheduleActionCall` —
filters completed actions by type and time
`create_droplet.go`	Component: `POST /v2/droplets` with hostname
validation
`example.go` + JSON files	Embedded example payloads for trigger and
component
`*_test.go`	Unit tests for Sync, ListResources, Setup, Execute,
HandleAction

Frontend

File	Purpose
`mappers/digitalocean/`	index, trigger renderer, component mapper
`integrationIcons.tsx`	DigitalOcean logo registration
`integrationDisplayName.ts`	"DigitalOcean" display name
`mappers/index.ts`	Registration in app-wide registries

Modified

pkg/server/server.go — import for init() registration

Test plan

Closes #2398

Video:
https://drive.google.com/file/d/1frbOy9LM_DvesaIi_c0Zo4shlk2ebPhA/view?usp=sharing

docker-compose.dev.yml

pkg/integrations/digitalocean/on_droplet_event.go

web_src/src/pages/workflowv2/mappers/digitalocean/on_droplet_event.ts

pkg/integrations/digitalocean/on_droplet_event.go

AleksandarCole · 2026-02-09T16:37:47Z

Thanks @aldoabellto235 for the submission.

Please review these instructions: https://github.com/superplanehq/superplane/blob/main/docs/contributing/integration-prs.md

Can you attach the video of the working integration and components?

web_src/src/pages/workflowv2/mappers/digitalocean/create_droplet.ts

pkg/integrations/digitalocean/create_droplet.go

aldoabellto235 · 2026-02-10T01:32:35Z

Thanks @aldoabellto235 for the submission.

Please review these instructions: https://github.com/superplanehq/superplane/blob/main/docs/contributing/integration-prs.md

Can you attach the video of the working integration and components?

i have attached link to google drive vedeo

web_src/src/pages/workflowv2/mappers/digitalocean/on_droplet_event.ts

pkg/integrations/digitalocean/example_output_create_droplet.json

pkg/integrations/digitalocean/on_droplet_event.go

pkg/integrations/digitalocean/client.go

pkg/integrations/gitlab/gitlab.go

pkg/integrations/render/client.go

AleksandarCole · 2026-02-10T09:49:47Z

@aldoabellto235 amazing work! Tested it and it runs good with no issues.
Can we address these small changes before I push it to the code review:

Details tab (onEvent): can we move timestamps at the top, can we also include more info about the droplet (like what we have in other component) - currently only region is displayed, need info on size and os. Let's use Dropplet ID instead of ResourceID. Overall we want to have similar details for these two components.
Details tab (createDroplet) - Can we add timestamps at the top? Ip address appears empty. Status doesn't make sense to have here. Let's also include OS info
createDropplet configuration - when I enable tag and add some string - it will result in 500 when I try to save it

aldoabellto235 · 2026-02-10T14:35:16Z

@aldoabellto235 amazing work! Tested it and it runs good with no issues. Can we address these small changes before I push it to the code review:

Details tab (onEvent): can we move timestamps at the top, can we also include more info about the droplet (like what we have in other component) - currently only region is displayed, need info on size and os. Let's use Dropplet ID instead of ResourceID. Overall we want to have similar details for these two components.

Details tab (createDroplet) - Can we add timestamps at the top? Ip address appears empty. Status doesn't make sense to have here. Let's also include OS info

createDropplet configuration - when I enable tag and add some string - it will result in 500 when I try to save it

Done can you check again

AleksandarCole · 2026-02-10T19:11:51Z

@aldoabellto235 works well, thanks for prompt update! I will move it on to code review. Not sure about using 60s pooling for the trigger component - but I will let the engineering team check that.

In the meantime - I see that there is a conflict - please resolve that one while code review is in progress.

shiroyasha · 2026-02-10T19:36:14Z

Hey @aldoabellto235. Congrats on your first PR.

I see that you have quite a lot of unrelated changes, e.g. changes to GitLab, PagerDuty, etc. Please rebase with main if you haven't already, and remove changes from the Core system and from non-Digital Ocean components.

Returning to stage-2/3. The diff is quite big, and it will require a new functional review after the cleanup and rebase with main is done.

pkg/integrations/digitalocean/on_droplet_event.go

aldoabellto235 · 2026-02-11T04:45:10Z

Hey @aldoabellto235. Congrats on your first PR.

I see that you have quite a lot of unrelated changes, e.g. changes to GitLab, PagerDuty, etc. Please rebase with main if you haven't already, and remove changes from the Core system and from non-Digital Ocean components.

Returning to stage-2/3. The diff is quite big, and it will require a new functional review after the cleanup and rebase with main is done.

Done updated

shiroyasha · 2026-02-13T10:14:14Z

Hey @aldoabellto235. The code looks great! I'm doing the final round of tests and trying to set up this flow:

1/ Create a dropplet
2/ SSH into it, and run echo "hello world"

It seems that the IP address is not returned in the payload.
This would be a critical info to have in the downstream nodes.

Can we get it from DO's API?

pkg/integrations/digitalocean/create_droplet.go

aldoabellto235 · 2026-02-13T13:53:55Z

Hey @aldoabellto235. The code looks great! I'm doing the final round of tests and trying to set up this flow:

1/ Create a dropplet 2/ SSH into it, and run echo "hello world"
It seems that the IP address is not returned in the payload. This would be a critical info to have in the downstream nodes.
Can we get it from DO's API?

Okey let me add that

cursor

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

pkg/integrations/digitalocean/create_droplet.go

pkg/integrations/digitalocean/on_droplet_event.go

Add DigitalOcean integration with: - Create Droplet component (with SSH keys, tags, user data support) - On Droplet Event trigger (polls for lifecycle events) - Client with account, regions, sizes, images, actions, and droplet APIs - Frontend mappers with execution details and event rendering - Icon registration in sidebar and component header Signed-off-by: Aldo <aldo.abellto14@gmail.com>

The validateList function accessed field.TypeOptions.List without first checking if TypeOptions was nil, unlike every other validator (validateNumber, validateString, validateText, validateSelect, etc). This could cause a nil pointer dereference when validating a FieldTypeList field that has no TypeOptions configured. Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Avoid N+1 API calls when multiple actions reference the same droplet by caching GetDroplet results per ResourceID during each poll cycle. Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Closes superplanehq#2618 This PR introduces the **Cursor** integration to SuperPlane, allowing users to build workflows utilizing Cursor's AI-powered capabilities. It includes the base integration setup and two starter components: 1. **Launch Cloud Agent (Action):** Triggers a Cursor Cloud Agent on a specific repository/branch and tracks the execution state to completion. It links to the Cloud Agent and PR in the output. This agent has no limits(except credit limit). 2. **Get Daily Usage Data (Action):** Fetches daily team usage metrics from the Cursor Admin API for reporting and cost tracking. - **Authentication:** Connects via Cursor BasicAuth (Admin API and Cloud Agents API). - **Code Logic:** The `Launch Cloud Agent` implementation handles significant logic to track the agent's lifecycle (polling status, handling completion, etc.). The code is structured to robustly handle this weight to ensure reliable execution tracking. [Watch the Loom Video](https://www.loom.com/share/2f6f3f98ab6b47ce88444a15f93afe45) - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation (`make gen.components.docs`) - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] I have signed off my commits (`git commit -s`) --------- Signed-off-by: Harsh <harxhist@gmail.com> Signed-off-by: Igor Šarčević <igor@operately.com> Co-authored-by: Igor Šarčević <igisar@gmail.com> Co-authored-by: Igor Šarčević <igor@operately.com> Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Add networks/v4 data to the droplet enrichment payload so the trigger detail tab can display the droplet's public IP address. Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Add DigitalOcean integration with: - Create Droplet component (with SSH keys, tags, user data support) - On Droplet Event trigger (polls for lifecycle events) - Client with account, regions, sizes, images, actions, and droplet APIs - Frontend mappers with execution details and event rendering - Icon registration in sidebar and component header Signed-off-by: Aldo <aldo.abellto14@gmail.com>

The rebase conflict resolution accidentally kept older versions of Cursor integration files, missing ConversationMessage and GetAgentConversation that get_last_message.go depends on. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Aldo <aldo.abellto14@gmail.com>

Instead of emitting immediately after creation (when droplet status is "new" and has no IP), store the droplet ID in metadata and schedule a poll action every 10s. Once the droplet reaches "active" status with an assigned IP address, emit the full droplet data. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Aldo <aldo.abellto14@gmail.com>

- createDroplet: handle terminal droplet states (off, archive) instead of polling indefinitely. Only continue polling for "new" status. - onDropletEvent: log emit failures instead of returning error, so the trigger keeps polling and doesn't stop permanently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Aldo <aldo.abellto14@gmail.com>

aldoabellto235 · 2026-02-14T17:13:42Z

@shiroyasha i add ip address, you can try it

AleksandarCole · 2026-02-15T10:25:07Z

Thanks @aldoabellto235!

@shiroyasha I've tested this, it waits for droplet to spin up (Running state), and provides IP at the end.

If code looks good I would like to merge this.

cursor bot reviewed Feb 9, 2026

View reviewed changes

AleksandarCole added the pr:stage-1/3 Needs to pass basic review. label Feb 9, 2026

AleksandarCole added the wfh label Feb 9, 2026