NetSendo v1.7.8: Better Debugging & API Scheduling
Introduction
Have you ever spent valuable time trying to figure out why a specific email failed to send? A cryptic, truncated error message can turn a quick fix into a lengthy investigation. Similarly, automating campaign creation often involves multiple API calls, adding unnecessary complexity to your workflows. At NetSendo, we believe in giving you full control and clarity over your marketing automation.
That's why we're excited to release NetSendo v1.7.8. This update is all about improving your developer and operator experience with enhanced error diagnostics and more powerful campaign scheduling tools.
scheduled_at parameter to the create_campaign API tool, allowing you to schedule campaigns in a single step.
🚀 What's New in v1.7.8
This release focuses on quality-of-life improvements that streamline common tasks and remove friction from your daily operations. As a self-hosted platform, giving you the best tools to manage your system is our top priority.
Detailed Error Modal
No more truncated error messages. See the full SMTP log or API error in a clean, accessible modal.
One-Step API Scheduling
The create_campaign tool now accepts a scheduled_at parameter to create and schedule in one API call.
API Key Stability
We've fixed the "CSRF token mismatch" bug, ensuring reliable API key generation every time.
Enhanced Error Diagnostics
Previously, when a message failed to send, the error in the Message Statistics table was often cut short. This was especially problematic for verbose SMTP connection errors. In v1.7.8, the error column is now clickable, opening a modal that displays the full, non-truncated error message. It even includes a "Copy to Clipboard" button for easy sharing or logging.
ℹ️ Note: This feature is a game-changer for diagnosing deliverability issues, from incorrect credentials to firewall blocks on your SMTP port.
Streamlined Campaign Scheduling via API
We've made our MCP Campaign Tools even more powerful. You can now create and schedule a campaign in a single API request by including the optional scheduled_at parameter. This simplifies automation scripts and reduces the number of calls needed to get a campaign ready to go.
{
"tool": "create_campaign",
"inputs": {
"name": "Q1 Newsletter",
"channel": "email",
"type": "regular",
"list_ids": [1, 2],
"template_id": 15,
"from_email": "hello@yourbrand.com",
"from_name": "YourBrand",
"subject": "Our Latest Updates!",
"scheduled_at": "2026-03-15T09:00:00Z"
}
}🎁 Benefits & Use Cases
These new features unlock more efficient workflows for everyone, from SaaS companies to marketing agencies.
SaaS: Proactive Churn Prevention
Your automated "trial ending" email sequence suddenly has a high failure rate. Instead of guessing, you click the error message and see a detailed SMTP error: 535-5.7.8 Username and Password not accepted. You realize your email provider's password was recently changed, and you can fix it instantly, preventing customer churn.
E-commerce: Flash Sale Automation
You want to trigger a flash sale campaign based on inventory levels from your backend system. With the new scheduled_at parameter, your inventory management script can make a single API call to NetSendo to create and schedule the "Low Stock Alert!" campaign for the optimal time, all without manual intervention.
Agencies: Transparent Client Reporting
A client asks why some of their contacts aren't receiving the newsletter. You can now navigate to their Message Statistics, copy the exact, detailed error for a bounced recipient, and provide a clear, actionable explanation. This builds trust and positions you as a knowledgeable partner.
🛠️ Step-by-Step Guide: Diagnosing a Failed Message
Let's walk through how to use the new error modal to debug a sending failure.
-
Navigate to Statistics
In your NetSendo dashboard, go to a specific message and click on the "Statistics" tab.
-
Identify Failed Recipients
Scroll down to the "Recipients" list and filter or find a recipient with the status "Failed". You'll see a truncated error message in the "Status" column.
-
Open the Error Modal
Click directly on the truncated error message. A modal window will pop up.
[Image: A screenshot showing the Message Statistics table with an arrow pointing to the clickable error message, and the resulting modal open with a full error log.] -
Analyze and Copy
Read the full error message in the modal. Use the "Copy to Clipboard" button to save the error for your records or to share with your server administrator.
🎯 Expert Tips
Use the NetSendo API to periodically fetch message statistics. If you find failed messages, you can now pull the full error details and push them directly to a Slack channel or a logging service like Sentry for proactive alerting.
Combine the scheduled_at parameter with your own business logic. For example, create a script that schedules birthday emails for your users by pulling their birthdate from your CRM and setting the campaign to run at 8 AM in their local timezone.
Now that generating API keys is more reliable, remember to follow security best practices. Store your keys in environment variables or a dedicated secrets manager. Never commit them directly to your codebase.
Conclusion with CTA
NetSendo v1.7.8 is a testament to our commitment to developer experience and operational excellence. With clearer error diagnostics and more efficient API tools, you can spend less time debugging and more time building meaningful connections with your audience.
As a self-hosted platform, you have the power to update and benefit from these improvements immediately. Data ownership and unlimited sending are just the beginning; true power comes from a tool that's a joy to use and manage.
Ready to Improve Your Workflow?
Update your instance to NetSendo v1.7.8 today to take advantage of these new features.
