Skip to content

feat: Add CircleCI integration#2916

Merged
shiroyasha merged 47 commits intosuperplanehq:mainfrom
vikramships:feat/circleci-integration
Feb 11, 2026
Merged

feat: Add CircleCI integration#2916
shiroyasha merged 47 commits intosuperplanehq:mainfrom
vikramships:feat/circleci-integration

Conversation

@vikramships
Copy link
Contributor

@vikramships vikramships commented Feb 6, 2026

What Changed

Added CircleCI integration with API token authentication. This includes two components: a trigger that listens for pipeline completions and an action that starts pipelines and tracks them to completion.

Why

This integration enables SuperPlane users to orchestrate CircleCI pipelines within their workflows. Users can trigger builds, monitor pipeline status, and react to completion events without leaving SuperPlane.

How

Base Integration:

  • Uses CircleCI Personal API Token for authentication
  • Implements webhook provisioning for real-time events
  • Follows the Semaphore integration pattern

On Pipeline Completed (Trigger):

  • Registers webhooks with CircleCI to receive workflow completion events
  • Verifies webhook signatures using HMAC SHA256
  • Emits events when workflows finish (success/failed/canceled)

Trigger Pipeline (Action):

  • Starts pipelines via CircleCI API with configurable parameters
  • Monitors completion using webhook + polling fallback (10s interval)
  • Routes to success/failed output channels based on final workflow status
  • Automatically injects SuperPlane execution context as pipeline parameters

Tests & Documentation:

  • Unit tests for all components
  • Integration tests for webhook handling
  • Full documentation in docs/components/CircleCI.mdx

Demo Video

https://www.youtube.com/watch?v=PvzHGetsujk

The video shows:

  1. Integration setup with API token
  2. On Pipeline Completed trigger detecting a pipeline completion
  3. Trigger Pipeline action starting a pipeline and tracking it to success

Related Issues

Closes #1957

Breaking Changes

None

cursor[bot]
cursor bot reviewed Feb 6, 2026
View reviewed changes
cursor[bot]
cursor bot reviewed Feb 6, 2026
View reviewed changes
cursor[bot]
cursor bot reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
shiroyasha
shiroyasha reviewed Feb 6, 2026
View reviewed changes
@shiroyasha
Copy link
Collaborator

shiroyasha commented Feb 6, 2026

@vikramships great start! 🎉

I left a few comments that need to be addressed before we can merge.

lucaspin
lucaspin reviewed Feb 7, 2026
View reviewed changes
@forestileao
Copy link
Collaborator

forestileao commented Feb 7, 2026 •
edited
Loading

@vikramships thank you for the PR.
Just a few requirements:

  • To make it mergable we need to follow some desings on the frontend side. As you can see the component UI is plain with default states and no metadata info. So I suggest checking docs/contributing/component-design.md
  • it is possible to use AI help to generate the metadata
  • everything that would need to be implemented in the frontend is under web_src/src/worflowv2/mappers
  • we have some pre-implemented examples to follow

@vikramships
Copy link
Contributor Author

vikramships commented Feb 7, 2026

@vikramships thank you for the PR. Just a few requirements:

  • To make it mergable we need to follow some desings on the frontend side. As you can see the component UI is plain with default states and no metadata info. So I suggest checking docs/contributing/component-design.md
  • it is possible to use AI help to generate the metadata
  • everything that would need to be implemented in the frontend is under web_src/src/worflowv2/mappers
  • we have some pre-implemented examples to follow

Hi @forestileao,

I'm working on these improvements based on the examples. Thanks.

cursor[bot]
cursor bot reviewed Feb 7, 2026
View reviewed changes
cursor[bot]
cursor bot reviewed Feb 7, 2026
View reviewed changes
@vikramships vikramships force-pushed the feat/circleci-integration branch 2 times, most recently from 70338f4 to 8a3dad1 Compare February 7, 2026 04:02
cursor[bot]
cursor bot reviewed Feb 7, 2026
View reviewed changes
cursor[bot]
cursor bot reviewed Feb 7, 2026
View reviewed changes
@AleksandarCole AleksandarCole added the bounty This issue has a bounty open label Feb 7, 2026
@vikramships
Copy link
Contributor Author

vikramships commented Feb 7, 2026

@forestileao @shiroyasha @lucaspin - All feedback addressed. Frontend mappers implemented. Ready for re-review when you get a chance. Thanks!

@shiroyasha
Copy link
Collaborator

shiroyasha commented Feb 7, 2026

@vikramships it seems that you have conflicts with the main branch, can you please address them 🙏

@vikramships vikramships force-pushed the feat/circleci-integration branch from e27d1e3 to fec1d18 Compare February 7, 2026 16:33
@vikramships
Copy link
Contributor Author

vikramships commented Feb 7, 2026 •
edited
Loading

@vikramships it seems that you have conflicts with the main branch, can you please address them 🙏

Thanks for mentioning this @shiroyasha, I pushed new changes.

@forestileao
Copy link
Collaborator

forestileao commented Feb 7, 2026 •
edited
Loading

@vikramships thanks for adding the mapper in the frontend. But please address the comments from @lucaspin and @shiroyasha and resolve them once done.

@shiroyasha
Add error message
40e0472 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Store url in the metadata
4454536 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Allow selecting pipeline definition id from a list
0b8f56e 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Show pipeline name on the node
da3fc64 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Fix metadata updating
2b193ae 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Preserve metadata
7c0adc5 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Check pipeline status
e722097 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Poll right after you get a webhook
f91d9fd 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Don't store workflow data in the metadata
bafd762 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Fix nil problem in trigger setup
bbce782 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Upsert the webhook
5e675f4 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
After hook, start agressive polling
5859e6c 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Allow requesting actions from a trigger webhook request
c27698e 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Fixup code for poll after hook
c4ad00c 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Cleanup action payload
d266d8c 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Handle errored state
8742d43 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Apply formatting
be17845 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha shiroyasha force-pushed the feat/circleci-integration branch from 8f120ca to be17845 Compare February 11, 2026 11:25
@shiroyasha
Rename the on pipeline done -> on workflow completed
e775d26 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha
Rely on workflow status
82a18d4 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha shiroyasha force-pushed the feat/circleci-integration branch 2 times, most recently from 006546f to 0a9ab93 Compare February 11, 2026 16:48
@shiroyasha
Simplify pipeline done condition
84f26ba 
Signed-off-by: Igor Šarčević <igor@operately.com>
@shiroyasha shiroyasha force-pushed the feat/circleci-integration branch from 8a17d99 to 84f26ba Compare February 11, 2026 17:03
@shiroyasha shiroyasha merged commit 278ec69 into superplanehq:main Feb 11, 2026
2 checks passed
@github-project-automation github-project-automation bot moved this from Backlog to Done in SuperPlane Board Feb 11, 2026
aldoabellto235 pushed a commit to aldoabellto235/superplane that referenced this pull request Feb 14, 2026
@vikramships @shiroyasha @aldo235
feat: Add CircleCI integration (superplanehq#2916)
b97b2b5 
## What Changed

Added CircleCI integration with API token authentication. This includes
two components: a trigger that listens for pipeline completions and an
action that starts pipelines and tracks them to completion.

## Why

This integration enables SuperPlane users to orchestrate CircleCI
pipelines within their workflows. Users can trigger builds, monitor
pipeline status, and react to completion events without leaving
SuperPlane.

## How

**Base Integration:**
- Uses CircleCI Personal API Token for authentication
- Implements webhook provisioning for real-time events
- Follows the Semaphore integration pattern

**On Pipeline Completed (Trigger):**
- Registers webhooks with CircleCI to receive workflow completion events
- Verifies webhook signatures using HMAC SHA256
- Emits events when workflows finish (success/failed/canceled)

**Trigger Pipeline (Action):**
- Starts pipelines via CircleCI API with configurable parameters
- Monitors completion using webhook + polling fallback (10s interval)
- Routes to success/failed output channels based on final workflow
status
- Automatically injects SuperPlane execution context as pipeline
parameters

**Tests & Documentation:**
- Unit tests for all components
- Integration tests for webhook handling
- Full documentation in `docs/components/CircleCI.mdx`

## Demo Video

https://www.youtube.com/watch?v=PvzHGetsujk

The video shows:
1. Integration setup with API token
2. On Pipeline Completed trigger detecting a pipeline completion
3. Trigger Pipeline action starting a pipeline and tracking it to
success

## Related Issues

Closes superplanehq#1957

## Breaking Changes

None

---------

Signed-off-by: vikramships <zenohkai@gmail.com>
Signed-off-by: Ramesh Kumar Voodi <voodirameshkumar@gmail.com>
Signed-off-by: Igor Šarčević <igor@operately.com>
Co-authored-by: Igor Šarčević <igor@operately.com>
Signed-off-by: Aldo <aldo.abellto14@gmail.com>
ishaksebsib pushed a commit to ishaksebsib/superplane that referenced this pull request Feb 17, 2026
@vikramships @shiroyasha
feat: Add CircleCI integration (superplanehq#2916)
9fe62f6 
## What Changed

Added CircleCI integration with API token authentication. This includes
two components: a trigger that listens for pipeline completions and an
action that starts pipelines and tracks them to completion.

## Why

This integration enables SuperPlane users to orchestrate CircleCI
pipelines within their workflows. Users can trigger builds, monitor
pipeline status, and react to completion events without leaving
SuperPlane.

## How

**Base Integration:**
- Uses CircleCI Personal API Token for authentication
- Implements webhook provisioning for real-time events
- Follows the Semaphore integration pattern

**On Pipeline Completed (Trigger):**
- Registers webhooks with CircleCI to receive workflow completion events
- Verifies webhook signatures using HMAC SHA256
- Emits events when workflows finish (success/failed/canceled)

**Trigger Pipeline (Action):**
- Starts pipelines via CircleCI API with configurable parameters
- Monitors completion using webhook + polling fallback (10s interval)
- Routes to success/failed output channels based on final workflow
status
- Automatically injects SuperPlane execution context as pipeline
parameters

**Tests & Documentation:**
- Unit tests for all components
- Integration tests for webhook handling
- Full documentation in `docs/components/CircleCI.mdx`

## Demo Video

https://www.youtube.com/watch?v=PvzHGetsujk

The video shows:
1. Integration setup with API token
2. On Pipeline Completed trigger detecting a pipeline completion
3. Trigger Pipeline action starting a pipeline and tracking it to
success

## Related Issues

Closes superplanehq#1957

## Breaking Changes

None

---------

Signed-off-by: vikramships <zenohkai@gmail.com>
Signed-off-by: Ramesh Kumar Voodi <voodirameshkumar@gmail.com>
Signed-off-by: Igor Šarčević <igor@operately.com>
Co-authored-by: Igor Šarčević <igor@operately.com>
mfuzailzubari pushed a commit to mfuzailzubari/superplane that referenced this pull request Feb 19, 2026
@vikramships @mfuzailzubari
feat: Add CircleCI integration (superplanehq#2916)
af76309 
## What Changed

Added CircleCI integration with API token authentication. This includes
two components: a trigger that listens for pipeline completions and an
action that starts pipelines and tracks them to completion.

## Why

This integration enables SuperPlane users to orchestrate CircleCI
pipelines within their workflows. Users can trigger builds, monitor
pipeline status, and react to completion events without leaving
SuperPlane.

## How

**Base Integration:**
- Uses CircleCI Personal API Token for authentication
- Implements webhook provisioning for real-time events
- Follows the Semaphore integration pattern

**On Pipeline Completed (Trigger):**
- Registers webhooks with CircleCI to receive workflow completion events
- Verifies webhook signatures using HMAC SHA256
- Emits events when workflows finish (success/failed/canceled)

**Trigger Pipeline (Action):**
- Starts pipelines via CircleCI API with configurable parameters
- Monitors completion using webhook + polling fallback (10s interval)
- Routes to success/failed output channels based on final workflow
status
- Automatically injects SuperPlane execution context as pipeline
parameters

**Tests & Documentation:**
- Unit tests for all components
- Integration tests for webhook handling
- Full documentation in `docs/components/CircleCI.mdx`

## Demo Video

https://www.youtube.com/watch?v=PvzHGetsujk

The video shows:
1. Integration setup with API token
2. On Pipeline Completed trigger detecting a pipeline completion
3. Trigger Pipeline action starting a pipeline and tracking it to
success

## Related Issues

Closes superplanehq#1957

## Breaking Changes

None

---------

Signed-off-by: vikramships <zenohkai@gmail.com>
Signed-off-by: Ramesh Kumar Voodi <voodirameshkumar@gmail.com>
Signed-off-by: Igor Šarčević <igor@operately.com>
Co-authored-by: Igor Šarčević <igor@operately.com>

Signed-off-by: Muhammad Fuzail Zubari <mfuzail.zubari@gmail.com>
mfuzailzubari pushed a commit to mfuzailzubari/superplane that referenced this pull request Feb 19, 2026
@vikramships @mfuzailzubari
feat: Add CircleCI integration (superplanehq#2916)
898d20f 
## What Changed

Added CircleCI integration with API token authentication. This includes
two components: a trigger that listens for pipeline completions and an
action that starts pipelines and tracks them to completion.

## Why

This integration enables SuperPlane users to orchestrate CircleCI
pipelines within their workflows. Users can trigger builds, monitor
pipeline status, and react to completion events without leaving
SuperPlane.

## How

**Base Integration:**
- Uses CircleCI Personal API Token for authentication
- Implements webhook provisioning for real-time events
- Follows the Semaphore integration pattern

**On Pipeline Completed (Trigger):**
- Registers webhooks with CircleCI to receive workflow completion events
- Verifies webhook signatures using HMAC SHA256
- Emits events when workflows finish (success/failed/canceled)

**Trigger Pipeline (Action):**
- Starts pipelines via CircleCI API with configurable parameters
- Monitors completion using webhook + polling fallback (10s interval)
- Routes to success/failed output channels based on final workflow
status
- Automatically injects SuperPlane execution context as pipeline
parameters

**Tests & Documentation:**
- Unit tests for all components
- Integration tests for webhook handling
- Full documentation in `docs/components/CircleCI.mdx`

## Demo Video

https://www.youtube.com/watch?v=PvzHGetsujk

The video shows:
1. Integration setup with API token
2. On Pipeline Completed trigger detecting a pipeline completion
3. Trigger Pipeline action starting a pipeline and tracking it to
success

## Related Issues

Closes superplanehq#1957

## Breaking Changes

None

---------

Signed-off-by: vikramships <zenohkai@gmail.com>
Signed-off-by: Ramesh Kumar Voodi <voodirameshkumar@gmail.com>
Signed-off-by: Igor Šarčević <igor@operately.com>
Co-authored-by: Igor Šarčević <igor@operately.com>

Signed-off-by: Muhammad Fuzail Zubari <mfuzail.zubari@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@shiroyasha shiroyasha shiroyasha left review comments

@cursor cursor[bot] cursor[bot] left review comments

@forestileao forestileao Awaiting requested review from forestileao

@lucaspin lucaspin Awaiting requested review from lucaspin

Assignees

@shiroyasha shiroyasha

Labels

bounty This issue has a bounty open pr:stage-3/3 Ready for full, in-depth, review

Projects

SuperPlane Board
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[CircleCI] Base

6 participants

@vikramships @shiroyasha @forestileao @AleksandarCole @omarsoufiane @lucaspin