Pulumi

Manage infrastructure as code with Pulumi Cloud stacks, deployments, and state.

Detail	Value
Category	DevOps
Base URL	https://api.pulumi.com/api
Authentication	Bearer Token
Endpoints	8
Connector key	pulumi

Using Pulumi in a workflow

1. Go to Connections and click New Connection.
2. Pick Pulumi from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /user	Get current user
GET /user/stacks	List stacks
GET /stacks/{organization}/{project}/{stack}	Get stack details
DELETE /stacks/{organization}/{project}/{stack}	Delete a stack
GET /stacks/{organization}/{project}/{stack}/updates	List update history
GET /stacks/{organization}/{project}/{stack}/export	Export stack state
POST /stacks/{organization}/{project}/{stack}/deployments	Create a deployment
GET /orgs/{organization}	Get organization details

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /user

Get current user

Detail	Value
Operation ID	devops.getCurrentUser
Method	GET
Path	/user

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.getCurrentUser.
4. 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 Pulumi API reference.

GET /user/stacks

List stacks

Detail	Value
Operation ID	devops.listStacks
Method	GET
Path	/user/stacks

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.listStacks.
4. 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 Pulumi API reference.

GET /stacks/{organization}/{project}/{stack}

Get stack details

Detail	Value
Operation ID	devops.getStack
Method	GET
Path	/stacks/{organization}/{project}/{stack}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.getStack.
4. 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 Pulumi API reference.

DELETE /stacks/{organization}/{project}/{stack}

Delete a stack

Detail	Value
Operation ID	devops.deleteStack
Method	DELETE
Path	/stacks/{organization}/{project}/{stack}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.deleteStack.
4. 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 Pulumi API reference.

GET /stacks/{organization}/{project}/{stack}/updates

List update history

Detail	Value
Operation ID	devops.listStackUpdates
Method	GET
Path	/stacks/{organization}/{project}/{stack}/updates

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.listStackUpdates.
4. 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 Pulumi API reference.

GET /stacks/{organization}/{project}/{stack}/export

Export stack state

Detail	Value
Operation ID	devops.exportStackState
Method	GET
Path	/stacks/{organization}/{project}/{stack}/export

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.exportStackState.
4. 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 Pulumi API reference.

POST /stacks/{organization}/{project}/{stack}/deployments

Create a deployment

Detail	Value
Operation ID	devops.createDeployment
Method	POST
Path	/stacks/{organization}/{project}/{stack}/deployments

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.createDeployment.
4. 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 Pulumi API reference.

GET /orgs/{organization}

Get organization details

Detail	Value
Operation ID	devops.getOrganization
Method	GET
Path	/orgs/{organization}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Pulumi connection from the Connection dropdown.
3. In the Operation dropdown, select devops.getOrganization.
4. 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 Pulumi API reference.