Appearance
Argo CD
Manage GitOps applications, sync operations, and clusters with Argo CD.
| Detail | Value |
|---|---|
| Category | DevOps |
| Base URL | https://argocd.example.com/api/v1 |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | argocd |
Using Argo CD in a workflow
- Go to Connections and click New Connection.
- Pick Argo CD from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /applications | List applications |
POST /applications | Create an application |
GET /applications/{name} | Get application details |
DELETE /applications/{name} | Delete an application |
POST /applications/{name}/sync | Sync an application |
POST /applications/{name}/rollback | Rollback an application |
GET /clusters | List clusters |
GET /repositories | List repositories |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /applications
List applications
| Detail | Value |
|---|---|
| Operation ID | devops.listApplications |
| Method | GET |
| Path | /applications |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listApplications. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
POST /applications
Create an application
| Detail | Value |
|---|---|
| Operation ID | devops.createApplication |
| Method | POST |
| Path | /applications |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.createApplication. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
GET /applications/{name}
Get application details
| Detail | Value |
|---|---|
| Operation ID | devops.getApplication |
| Method | GET |
| Path | /applications/{name} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.getApplication. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
DELETE /applications/{name}
Delete an application
| Detail | Value |
|---|---|
| Operation ID | devops.deleteApplication |
| Method | DELETE |
| Path | /applications/{name} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.deleteApplication. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
POST /applications/{name}/sync
Sync an application
| Detail | Value |
|---|---|
| Operation ID | devops.syncApplication |
| Method | POST |
| Path | /applications/{name}/sync |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.syncApplication. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
POST /applications/{name}/rollback
Rollback an application
| Detail | Value |
|---|---|
| Operation ID | devops.rollbackApplication |
| Method | POST |
| Path | /applications/{name}/rollback |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.rollbackApplication. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
GET /clusters
List clusters
| Detail | Value |
|---|---|
| Operation ID | devops.listClusters |
| Method | GET |
| Path | /clusters |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listClusters. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.
GET /repositories
List repositories
| Detail | Value |
|---|---|
| Operation ID | devops.listRepositories |
| Method | GET |
| Path | /repositories |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Argo CD connection from the Connection dropdown.
- In the Operation dropdown, select
devops.listRepositories. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Argo CD API reference.