Capture and centralize log messages from your n8n flows in Better Stack Logs. Teams can track errors, warnings, and info in one place for faster fixes and clear visibility. Ideal for IT and operations that want simple, reliable logging across many workflows.

Under the hood, an Execute Workflow Trigger accepts two inputs called level and message. Any other workflow can call it with an Execute Workflow node and pass those two fields. The HTTP Request node then sends a POST request with a JSON body to your Better Stack Logs endpoint using header based auth. A Manual Trigger with a built in test sender is included so you can verify everything before connecting other flows.

Set your Better Stack endpoint URL and add your bearer token in the HTTP header credential. Expect quicker triage because events appear in seconds where your team already works. Use it to log failed API calls, retries, long running jobs, or key milestones so you know what happened and when.

• Reusable Execute Workflow Trigger that receives level and message from any calling flow.
• HTTP Request node sends a JSON payload with POST to your Better Stack Logs endpoint.
• Header based authentication using a bearer token stored in n8n credentials.
• Manual Trigger plus a test sender to generate sample logs and confirm setup.
• Simple two field schema that keeps logging consistent across teams.
• Lightweight design with minimal nodes for easy maintenance.

• Reduce manual log gathering from 20 minutes to 2 minutes per incident
• Automate up to 90 percent of repetitive logging across n8n flows
• Improve error visibility by centralizing messages in one view
• Cut context switching by sending logs from every workflow
• Connect n8n and Better Stack Logs without custom code

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Better Stack Logs. See the Tools Required section above for links to create accounts with these services.
3. In Better Stack Logs, get your logs endpoint URL and your token from the API or dashboard settings.
4. In n8n, open the HTTP Request node named Send Log to BetterStack. In the Credential to connect with field, click Create new credential and choose HTTP Header Auth. Name it clearly, for example Header Auth BetterStack.
5. Add a header key Authorization with the value Bearer YOUR_TOKEN. Save the credential.
6. In the same HTTP Request node, set the URL to your Better Stack Logs endpoint. Confirm Method is POST and Body is JSON with fields message and level.
7. Run the Manual Trigger. The included Send test log message node will call the logging workflow and push a sample error message.
8. Check your Better Stack Logs dashboard to confirm the test event appears. If nothing shows, verify the URL, token, and Authorization header format.
9. To use from another workflow, add an Execute Workflow node, select this logging workflow, and pass level and message in the inputs. Start with values like info or error and a short text message.
10. Troubleshoot common issues: 401 or 403 errors mean the token or header is wrong. 404 suggests the endpoint URL is incorrect. Empty logs usually mean level or message were not provided.