Actions21
Overview
This node interacts with a service managing organizational data, specifically focusing on the "People" resource when the "Get All" operation is selected. It retrieves a list of people records from the system, optionally filtering to include only active individuals. This functionality is useful in scenarios such as syncing user directories, generating reports on current staff, or integrating people data into other workflows.
For example, you might use this node to fetch all active employees before sending them a notification email or to pull a complete list of contacts for CRM updates.
Properties
| Name | Meaning |
|---|---|
| Only Active | Boolean flag indicating whether to return only active people (true) or all people (false). |
| Options | A collection placeholder for additional optional parameters (currently empty). |
Output
The node outputs an array of JSON objects representing people records retrieved from the external system. Each object contains details about an individual person, such as their name, status, and other relevant attributes defined by the external API.
No binary data output is indicated in the source code.
Dependencies
- Requires connection to an external API service that manages people, clients, and projects data.
- Needs an API authentication token or key configured within n8n to authorize requests.
- The node depends on internal helper modules handling specific operations for people, clients, and projects.
Troubleshooting
- Unsupported resource error: If a resource other than "people", "clients", or "projects" is specified, the node throws an error stating the resource is unsupported. Ensure the resource parameter is correctly set.
- API errors: Network issues or invalid credentials may cause request failures. Verify API keys and network connectivity.
- Empty results: If no people are returned, check if the "Only Active" flag filters out all entries or if the external system has no matching records.
- When "Continue On Fail" is enabled, errors will be returned as JSON objects with an
errorfield instead of stopping execution.
Links and References
- Refer to the external API documentation of the service managing people data for detailed schema and filtering options.
- n8n documentation on configuring API credentials and error handling best practices.