MOCO

Consume MOCO API

Actions20

Project Actions
Company Actions
Activity Actions
User Actions

Overview

This node interacts with the MOCO API to manage User resources, specifically supporting the 'List' operation. It allows users to retrieve a list of users from MOCO with options to return all users or limit the number of results. Additional filtering options include filtering by user IDs, fetching users updated after a specific timestamp, including archived (deactivated) users, and sorting the results by a specified field. This node is useful for scenarios where you need to synchronize user data, generate reports, or automate workflows involving user information from MOCO.

Use Case Examples

Retrieve all users in the MOCO system to synchronize with another database.
Fetch a limited number of users updated after a certain date for incremental updates.
List users including archived ones for audit or compliance purposes.

Properties

Name	Meaning
Return All	Whether to return all user results or only up to a given limit.
Limit	Maximum number of user results to return when 'Return All' is false.
IDs	Filter users by specific IDs, allowing fetching multiple users by providing comma-separated IDs.
Updated After	Filter users to include only those created or updated after the specified timestamp.
Additional Fields	Additional optional parameters for the user list operation, including whether to include archived users and the field to sort the results by.

Output

JSON

id - Unique identifier of the user.
firstname - First name of the user.
lastname - Last name of the user.
email - Email address of the user.
active - Indicates if the user is active.
external - Indicates if the user is external.
unit_id - Identifier of the unit the user belongs to.
archived - Indicates if the user is archived (deactivated).
created_at - Timestamp when the user was created.
updated_at - Timestamp when the user was last updated.

Dependencies

MOCO API

Troubleshooting

Ensure the MOCO API credentials are correctly configured and have the necessary permissions to list users.
If the node returns no results, verify the filter parameters such as IDs and Updated After timestamp are correct and match existing users.
When using the 'Return All' option, be aware of potential performance impacts if the user base is very large.
Common error messages may include authentication errors (check API key validity) and rate limit errors (consider adding delays or reducing request frequency).