Overview
This node allows you to send event envelopes to Sentry.io, a popular error tracking and monitoring platform. It is useful for logging messages with various severity levels from your workflows directly into Sentry, enabling centralized error reporting and monitoring.
Common scenarios include:
- Sending custom log messages or errors from an automation workflow to Sentry for tracking.
- Tagging events with workflow-specific metadata such as workflow ID and name.
- Adding extra contextual information like execution ID, URL, and trigger name to enrich the logged events.
For example, you can use this node to report a critical failure in a data processing workflow, including tags that identify the workflow and extras that link back to the specific execution instance.
Properties
| Name | Meaning |
|---|---|
| Message | The message text to send to Sentry. |
| Level | The severity level of the record. Options: Debug, Error, Fatal, Info, Log, Warning. |
| Environment | The environment name where the event occurred, e.g., "production" or "staging". |
| Tags | Additional key-value pairs to tag the event. By default, workflow ID and name are included. |
| Extra | Additional key-value pairs to add extra context to the event. By default, execution ID, URL, and trigger name are included. |
Output
The node outputs an array of JSON objects representing the response from the Sentry API for each input item processed. Each output item corresponds to one input item and contains the result of sending the envelope to Sentry.
If an error occurs and the node is set to continue on fail, the output for that item will contain an error field describing the issue.
No binary data is produced by this node.
Dependencies
- Requires an API authentication token credential for Sentry.io (referred generically as "an API key credential").
- The node uses the Sentry HTTP API endpoint
/api/{projectId}/envelope/to send event envelopes. - The node expects the base URL of the n8n instance to construct URLs and hostnames for tagging and extra context.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect project ID in the credentials may lead to 404 or permission errors.
- Network connectivity issues can prevent sending data to Sentry.
- Malformed input properties (e.g., missing required message) will cause errors.
Error messages:
- Errors returned from the Sentry API will be included in the output if "continue on fail" is enabled.
- Typical errors include authentication failures, invalid payloads, or rate limiting.
Resolution tips:
- Verify the API key credential is correctly configured and has access to the target Sentry project.
- Ensure all required fields (Message, Level, Environment) are properly set.
- Check network connectivity and firewall settings.
- Review Sentry project settings and permissions.