LogSnag icon

LogSnag

Send events and insights to LogSnag
Join our community

Actions2

Overview

The LogSnag - Insight: Publish operation node allows you to send an "insight" (a key metric or value) to the LogSnag service. This is useful for tracking and visualizing important metrics, such as user signups, sales numbers, or any custom value over time, directly from your n8n workflows.

Common scenarios:

  • Automatically updating a dashboard with the latest business KPIs.
  • Sending real-time metrics from automated processes (e.g., number of processed orders).
  • Logging application health or usage statistics for monitoring purposes.

Practical example:
After processing a batch of new users in n8n, you can use this node to publish the total count as an insight to LogSnag, where it can be visualized and tracked over time.

Properties

Name Type Meaning
Project String The name of the LogSnag project where the insight will be published. Required.
Title String The title of the insight (e.g., "New Users Today"). Required.
Value String The value of the insight (e.g., "42", "99.5%"). Required.
Additional Fields Object Optional collection of extra fields. For this operation:
  Icon String A single emoji to represent the insight visually (optional).

Output

The node returns the response from the LogSnag API after publishing the insight. The structure typically includes:

{
  "success": true,
  "message": "Insight published successfully"
}
  • The actual output may include additional fields depending on the LogSnag API's response.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the LogSnag API.
  • API Key: You must configure valid LogSnag API credentials in n8n under the credential type logsnagApi.
  • n8n Configuration: Ensure that the node has network access to https://api.logsnag.com/v1.

Troubleshooting

Common issues:

  • Missing or invalid API key:
    Error message: 401 Unauthorized or similar.
    Resolution: Check that your LogSnag API credentials are correctly set up in n8n.

  • Required property missing:
    Error message: 400 Bad Request with details about missing fields.
    Resolution: Ensure all required properties ("Project", "Title", "Value") are provided.

  • Invalid value for Icon:
    If the icon is not a single emoji, the API may reject the request.
    Resolution: Use only a single emoji character for the Icon field.

  • Network errors:
    Error message: ENOTFOUND, ECONNREFUSED, etc.
    Resolution: Verify network connectivity from your n8n instance to LogSnag.

Links and References

Discussion