Actions24
- Account Actions
- Analytics Actions
- Campaign Actions
- Lead Actions
Overview
This node integrates with the Instantly API to update an existing email campaign's settings and schedule. It is useful for marketing automation workflows where you need to programmatically modify campaign parameters such as sending limits, tracking options, scheduling, and other campaign-specific configurations.
Typical use cases include:
- Adjusting campaign parameters dynamically based on external triggers or data.
- Automating campaign management tasks like changing daily email limits or toggling tracking features.
- Scheduling campaigns to run only during specific times or days without manual intervention.
For example, you could use this node to update a campaign’s daily email limit and enable link tracking before launching it, or to pause a campaign by adjusting its schedule.
Properties
| Name | Meaning |
|---|---|
| Campaign | The target campaign to update. You can select from a list of existing campaigns or specify the campaign ID directly. |
| Campaign Name | New name for the campaign. Leave empty to keep the current name. |
| Additional Fields | Various optional fields to customize the campaign: - Positive Lead Value (number): Value assigned to each positive lead. - Is Evergreen (boolean): Whether the campaign runs continuously. - Email Gap (Minutes) (number): Time gap between emails. - Random Wait Max (Minutes) (number): Maximum random wait time. - Text Only (boolean): If true, campaign sends text-only emails. - Daily Limit (number): Max emails sent per day. - Daily Max Leads (number): Max new leads contacted daily. - Email Accounts (multi-select): List of email accounts used for sending. - Email Tag List (string): Comma-separated tag UUIDs for emails. - CC List (string): Comma-separated email addresses to CC. - BCC List (string): Comma-separated email addresses to BCC. - Link Tracking (boolean): Enable/disable link tracking. - Open Tracking (boolean): Enable/disable open tracking. - Stop on Reply (boolean): Stop campaign if a reply is received. - Stop on Auto Reply (boolean): Stop campaign on auto-reply. - Stop for Company (boolean): Stop campaign for entire company domain on reply. - Prioritize New Leads (boolean): Prioritize contacting new leads. - Match Lead ESP (boolean): Match leads by their email service provider. - Insert Unsubscribe Header (boolean): Add unsubscribe header in emails. - Allow Risky Contacts (boolean): Allow sending to risky contacts. - Disable Bounce Protect (boolean): Disable bounce protection. - Auto Variant Select Trigger (options): Trigger for automatic variant selection; options are None, Click Rate, Open Rate, Reply Rate. |
| Campaign Schedule | Settings related to campaign timing: - Start Date (datetime): When the campaign should start. - End Date (datetime): When the campaign should end. - Schedules (multiple): One or more schedules specifying: - Schedule Name (string) - From Time (string, HH:MM 24-hour) - To Time (string, HH:MM 24-hour) - Timezone (select from many global timezones) - Days of Week (multi-select): Days when emails are sent (Sunday to Saturday). |
Output
The node outputs JSON data representing the updated campaign object returned by the Instantly API after the update operation. This typically includes all campaign properties reflecting the new state post-update.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- The node depends on the Instantly API endpoints for campaigns and accounts.
- Proper configuration of the API credential in n8n is necessary.
- The node uses internal helper methods to fetch lists of campaigns and email accounts for dropdown selections.
Troubleshooting
Common issues:
- Invalid campaign ID or selecting a non-existent campaign will cause errors.
- Providing invalid date/time formats in the schedule may result in API rejections.
- Omitting required fields like the campaign identifier will prevent execution.
- Network or authentication failures with the Instantly API will cause request errors.
Error messages:
- Errors fetching campaigns or email accounts for dropdowns will log to console but do not block execution.
- API errors during update will be thrown and can be caught if "Continue On Fail" is enabled.
- Validation errors from the API (e.g., invalid field values) will appear in the error message.
Resolutions:
- Verify campaign IDs and ensure they exist.
- Use the provided dropdowns to avoid typos in IDs.
- Check API credentials and network connectivity.
- Validate date/time inputs conform to expected formats.
Links and References
- Instantly API Documentation (general reference for campaign operations)
- n8n Documentation (for configuring credentials and using nodes)
- Timezone list references: IANA Time Zone Database
This summary is based solely on static analysis of the provided source code and property definitions.