Overview
This node interacts with the Memos API to retrieve user or memo data. It supports listing all users or memos, as well as fetching a specific user or memo by its identifier. This node is useful in scenarios where you want to integrate Memos data into your workflows, such as syncing user information, displaying memo content, or automating data retrieval for further processing.
For example:
- Fetching a list of all users to update an internal directory.
- Retrieving a specific user's details by their ID.
- Getting a particular memo's content for analysis or notification purposes.
Properties
| Name | Meaning |
|---|---|
| Resource | Choose between "User" or "Memo" resource types. |
| Operation | Depending on the selected resource: - For User: "List Users", "Get User" - For Memo: "List Memos", "Get Memo" |
| Name | The identifier path for a specific user or memo, e.g., "users/1" or "memos/1". Required when using "Get User" or "Get Memo" operations. |
Output
The node outputs JSON data representing the requested users or memos:
- For list operations (
listUsers,listMemos), the output is an array of user or memo objects. - For get operations (
getUser,getMemo), the output is a single user or memo object matching the specified identifier.
The output is structured as an array of JSON objects under the json field, suitable for further workflow processing.
No binary data output is produced by this node.
Dependencies
- Requires access to the Memos API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node uses an internal helper function to make HTTP GET requests to the Memos API endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect "Name" property format (e.g., missing resource prefix like "users/" or "memos/") will result in failed requests.
- Requesting a non-existent user or memo ID will likely return an error or empty response.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify and update credentials.
- 404 Not Found errors suggest the specified user or memo does not exist; check the "Name" input value.
- Network or timeout errors may require checking connectivity or API availability.
Links and References
- Memos API Documentation (example placeholder link)
- n8n documentation on creating custom nodes