Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node interacts with a "Collection" resource and performs the "List" operation. It is designed to retrieve a list of items from a specified collection, likely from an external service or database (such as Directus). The node can optionally output each element of the returned array as a separate item in the workflow, which is useful for processing or iterating over individual records.
Common scenarios:
- Fetching all entries from a database collection for further processing.
- Integrating data from an external CMS or API into n8n workflows.
- Automating tasks that require handling multiple records individually, such as sending notifications or transforming data.
Practical example:
You might use this node to pull all user records from a "users" collection and then send each user a personalized email by splitting the results into individual items.
Properties
| Name | Type | Meaning |
|---|---|---|
| Split Into Items | Boolean | Whether to output each element of an array as its own item. If enabled, the node will emit one item per array element; otherwise, it outputs the entire array as a single item. |
Output
- json: The output contains the data retrieved from the collection. If "Split Into Items" is enabled, each item in the output represents a single element from the collection array. Otherwise, the output is a single item containing the full array under a property (commonly named after the collection or as a generic array).
- Binary: There is no indication that binary data is output by this node.
Dependencies
- This node depends on access to an external service (likely Directus) and may require appropriate API credentials or environment variables configured in n8n.
- Ensure that any required authentication (API keys, tokens, etc.) is set up in your n8n instance.
Troubleshooting
- Authentication errors: If credentials are missing or incorrect, you may receive errors related to authorization. Double-check your API keys or connection settings.
- Empty results: If the collection name is misspelled or does not exist, the node may return an empty array.
- Unexpected output structure: If "Split Into Items" is not set as intended, you may get a single item with an array instead of multiple items. Adjust the property accordingly.