Actions111
- Item Actions
- Webhook Actions
- Collection Actions
- File Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Extension Actions
- Field Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This n8n node is designed to interact with a "Preset" resource, specifically to retrieve (get) the details of a preset by its unique identifier. It is useful in scenarios where you need to fetch configuration or template data stored as presets from an external system (such as Directus or a similar service). For example, you might use this node to dynamically load preset settings for further automation steps, or to display preset information in a workflow.
Properties
| Name | Meaning |
|---|---|
| ID | Primary key of the preset. This is a required string value used to specify which preset to retrieve. Example: 39 |
Output
The output will be a JSON object containing the details of the requested preset. The exact structure depends on the external service's response, but typically includes fields such as the preset's ID, name, and other relevant attributes.
Dependencies
- Requires access to the external service that manages presets (e.g., Directus).
- May require API credentials or environment variables configured in n8n to authenticate requests.
Troubleshooting
- Missing or Invalid ID: If the "ID" property is missing or incorrect, the node may return an error indicating that the preset could not be found.
- Authentication Errors: If API credentials are not set up correctly, you may encounter authentication or authorization errors.
- Network Issues: Connectivity problems between n8n and the external service can result in timeout or network errors.
Links and References
- n8n Documentation
- Directus API Reference (if applicable to your setup)