Actions2
Overview
This node allows you to retrieve data from a Wawi (merchandise management) system via its API. Specifically, it supports fetching either articles ("Artikel Abrufen") or industries ("Branchen Abrufen"). This is useful in scenarios where you want to integrate your merchandise data or industry classifications into an n8n workflow for further processing, reporting, or synchronization with other systems.
For example, you could use this node to automatically pull the latest article information from your Wawi system and update a product catalog or trigger notifications when new articles are added.
Properties
| Name | Meaning |
|---|---|
| API Key | Your API key used for authenticating requests to the Wawi API. |
| Operation | The type of data to retrieve. Options: "Artikel Abrufen" (Fetch Articles), "Branchen Abrufen" (Fetch Industries). |
Output
The node outputs a single JSON object containing the response from the Wawi API endpoint corresponding to the selected operation:
- For "Artikel Abrufen", the output JSON contains the list or details of articles retrieved.
- For "Branchen Abrufen", the output JSON contains the list or details of industries retrieved.
The output structure directly reflects the API's JSON response without additional transformation.
No binary data output is produced by this node.
Dependencies
- Requires access to the Wawi API endpoints:
http://wawi24.test/api/artikelfor articleshttp://wawi24.test/api/branchenfor industries
- Requires a valid API key for authentication, passed in the
Authorizationheader. - No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing API key will likely result in authentication errors from the API.
- Network connectivity problems or incorrect base URL may cause request failures.
- Selecting an unsupported operation value would not trigger a valid API call.
Error messages:
- Authentication errors typically indicate invalid API key; verify and provide a correct key.
- Request timeouts or connection errors suggest network issues or incorrect API endpoint URLs.
- Unexpected API responses might require checking the API documentation or server status.
Links and References
- Refer to your Wawi system API documentation for detailed information on the
/artikeland/branchenendpoints and their response formats. - General n8n HTTP Request node documentation can help understand how API calls are made within workflows.