OneLogin

Manage users, apps, roles, and authentication via the OneLogin API.

Detail	Value
Category	Security
Base URL	https://api.us.onelogin.com/api/2
Authentication	Bearer Token
Endpoints	6
Connector key	onelogin

Using OneLogin in a workflow

1. Go to Connections and click New Connection.
2. Pick OneLogin 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 /users	List users
POST /users	Create a user
GET /users/{userId}	Get a user
GET /roles	List roles
GET /apps	List applications
GET /events	List events

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

GET /users

List users

Detail	Value
Operation ID	security.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 OneLogin connection from the Connection dropdown.
3. In the Operation dropdown, select security.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 OneLogin API reference.

POST /users

Create a user

Detail	Value
Operation ID	security.createUser
Method	POST
Path	/users

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /users/{userId}

Get a user

Detail	Value
Operation ID	security.getUser
Method	GET
Path	/users/{userId}

Parameters

Name	Location	Type	Required
userId	path	integer	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your OneLogin connection from the Connection dropdown.
3. In the Operation dropdown, select security.getUser.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

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 OneLogin API reference.

GET /roles

List roles

Detail	Value
Operation ID	security.listRoles
Method	GET
Path	/roles

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /apps

List applications

Detail	Value
Operation ID	security.listApps
Method	GET
Path	/apps

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /events

List events

Detail	Value
Operation ID	security.listEvents
Method	GET
Path	/events

Parameters

No parameters.

Using this endpoint in a workflow

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