Overview
This n8n node allows you to publish events to LogSnag, a service for event logging and notifications. Specifically, with the Log resource and the Publish operation, you can send custom log events to a specified project and channel in your LogSnag account. This is useful for tracking application events, user actions, or system changes, and optionally triggering push notifications.
Common scenarios:
- Logging user signups, purchases, or errors.
- Sending real-time notifications to your team when important events occur.
- Tracking workflow milestones or automation steps.
Example:
When a new order is placed in your e-commerce store, use this node to log the event to LogSnag and notify your team via push notification.
Properties
| Name | Type | Meaning |
|---|---|---|
| Project | String | The name of the LogSnag project where the event will be published. |
| Channel | String | The channel within the project to which the event will be sent. |
| Event | String | The name of the event being logged. |
| Additional Fields | Collection | Optional fields to further describe the event: |
| - Description | String | (Optional) A description of the event. |
| - Icon | String | (Optional) A single emoji to represent the event visually. |
| - Notify | Boolean | (Optional) Whether to send a push notification for this event. |
Output
The node returns the response from the LogSnag API as a JSON object. The structure typically includes confirmation of the event publication and may echo back submitted data. The exact output depends on the LogSnag API's response format.
Example output:
{
"success": true,
"message": "Event published successfully"
}
Note: The actual fields may vary based on LogSnag's API.
Dependencies
- External Service: Requires a LogSnag account.
- API Key: You must configure LogSnag API credentials in n8n under the name
logsnagApi. - n8n Configuration: No additional environment variables are required beyond the API key setup.
Troubleshooting
Common issues:
- Invalid API Key: If the API key is missing or incorrect, the node will fail with an authentication error. Ensure your credentials are set up correctly in n8n.
- Missing Required Fields: If any of the required properties (Project, Channel, Event) are empty, the node will throw a validation error. Double-check that all required fields are filled.
- Network Errors: If n8n cannot reach the LogSnag API (e.g., due to network issues), the node will return a connection error.
Error messages and resolutions:
"401 Unauthorized": Check your LogSnag API credentials."400 Bad Request": Ensure all required fields are provided and valid."404 Not Found": Verify the project and channel names exist in your LogSnag account.