SmartLeadInstall

Overview

The node integrates with the SmartLead API to manage email marketing campaigns. Specifically, the Update Schedule operation under the 🎯 Campaign Management resource allows users to modify the scheduling settings of an existing campaign. This includes setting how often emails are sent (daily, weekly, or monthly), the exact time for sending, specific days of the week (for weekly schedules), the day of the month (for monthly schedules), and the timezone.

This operation is beneficial when you want to automate or adjust the timing of your email campaigns without recreating them. For example, you might want to change a campaign from sending emails every Monday, Wednesday, and Friday at 9 AM UTC to sending daily at 10 AM in the "America/New_York" timezone.

Properties

Output

The output JSON contains the response data from the SmartLead API after updating the campaign schedule. Typically, this will include confirmation details about the updated schedule such as the new schedule type, time, days or date, and timezone.

The node does not output binary data for this operation.

Dependencies

• Requires an active connection to the SmartLead API via an API key credential configured in n8n.
• The node makes authenticated HTTP requests to the SmartLead API endpoint https://server.smartlead.ai/api/v1/campaigns/{campaignId}/schedule.
• Proper permissions on the API key to update campaign schedules are necessary.

Troubleshooting

• Invalid Campaign ID: If the provided Campaign ID does not exist or is incorrect, the API will return an error. Verify the Campaign ID before running the node.
• Invalid Schedule Parameters: Providing inconsistent parameters, such as missing Schedule Days for a weekly schedule or Schedule Date for a monthly schedule, may cause errors. Ensure all required fields for the chosen schedule type are set.
• Time Format Errors: The Schedule Time must be in 24-hour HH:mm format. Incorrect formatting can lead to request failures.
• Timezone Issues: Use valid timezone strings recognized by the API (e.g., UTC, America/New_York). Invalid timezones may cause errors.
• API Authentication Failures: Ensure the API key credential is correctly configured and has sufficient permissions.
• Network or Server Errors: Temporary network issues or server downtime can cause request failures. Retry after some time or check SmartLead service status.

Links and References

• SmartLead API Documentation (Assumed URL based on base URL; verify actual docs)
• List of IANA Time Zone Database Names — for valid timezone values
• n8n HTTP Request Node Documentation — for understanding HTTP request handling in n8n

If you need further details on other operations or resources, feel free to ask!