Snipe-IT

IT asset management for hardware, licenses, users, and locations.

Detail	Value
Category	DevOps
Base URL	https://snipeit.example.com/api/v1
Authentication	Bearer Token
Endpoints	8
Connector key	snipe-it

Using Snipe-IT in a workflow

1. Go to Connections and click New Connection.
2. Pick Snipe-IT 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 /hardware	List hardware assets
POST /hardware	Create a hardware asset
GET /hardware/{id}	Get hardware details
PUT /hardware/{id}	Update hardware asset
POST /hardware/{id}/checkout	Check out hardware
POST /hardware/{id}/checkin	Check in hardware
GET /licenses	List licenses
GET /users	List users

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

GET /hardware

List hardware assets

Detail	Value
Operation ID	devops.listHardware
Method	GET
Path	/hardware

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /hardware

Create a hardware asset

Detail	Value
Operation ID	devops.createHardware
Method	POST
Path	/hardware

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /hardware/{id}

Get hardware details

Detail	Value
Operation ID	devops.getHardware
Method	GET
Path	/hardware/{id}

Parameters

No parameters.

Using this endpoint in a workflow

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

PUT /hardware/{id}

Update hardware asset

Detail	Value
Operation ID	devops.updateHardware
Method	PUT
Path	/hardware/{id}

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /hardware/{id}/checkout

Check out hardware

Detail	Value
Operation ID	devops.checkoutHardware
Method	POST
Path	/hardware/{id}/checkout

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /hardware/{id}/checkin

Check in hardware

Detail	Value
Operation ID	devops.checkinHardware
Method	POST
Path	/hardware/{id}/checkin

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /licenses

List licenses

Detail	Value
Operation ID	devops.listLicenses
Method	GET
Path	/licenses

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /users

List users

Detail	Value
Operation ID	devops.listUsers
Method	GET
Path	/users

Parameters

No parameters.

Using this endpoint in a workflow

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