Instantly icon

Instantly

Interact with Instantly API

Actions24

Overview

This node integrates with the Instantly API to create and manage email marketing campaigns. Specifically, the Campaign Create operation allows users to set up a new email campaign with detailed scheduling, targeting, and behavioral options.

Typical use cases include automating outreach sequences for sales, marketing, or customer engagement by defining when and how emails are sent to leads. For example, a user can create a campaign that sends personalized emails on weekdays between 9 AM and 5 PM in a specific timezone, with tracking enabled and automatic stopping conditions based on replies.

Properties

Name Meaning
Campaign Name The name of the campaign to be created.
Schedule Name The name assigned to the campaign's sending schedule.
Start Time The daily start time (24-hour format) when emails should begin sending.
End Time The daily end time (24-hour format) after which emails should stop sending.
Days of Week The days of the week on which emails will be sent. Options: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday.
Timezone The timezone used for scheduling the campaign's send times. A comprehensive list of global timezones is available.
Additional Fields A collection of optional settings including:
• Start Date and End Date for the campaign duration
• Lead Value (numeric value per positive lead)
• Evergreen flag (whether campaign runs indefinitely)
• Email Gap (minutes between emails)
• Random Wait Max (max random delay in minutes)
• Text Only (send text-only emails)
• Daily Limit (max emails per day)
• Daily Max Leads (max new leads contacted daily)
• Link Tracking (enable/disable)
• Open Tracking (enable/disable)
• Stop on Reply / Auto Reply / For Company (stop campaign conditions)
• Prioritize New Leads
• Match Lead ESP (match by email service provider)
• Insert Unsubscribe Header
• Allow Risky Contacts
• Disable Bounce Protect
• Email List (multiple sender emails)
• Email Tag List (tags for sender emails)
• CC List (emails to carbon copy)
• BCC List (emails to blind carbon copy)
• Email Sequence Steps: stepwise email sequence with subject, body, and delays
• Auto Variant Select Trigger (none, click rate, open rate, reply rate)

Output

The node outputs an array of JSON objects representing the result of the campaign creation request. Each output item corresponds to one input item processed and contains the response data from the Instantly API about the newly created campaign.

  • The json field includes details such as campaign ID, name, schedule, and configuration as returned by the API.
  • No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Instantly API.
  • The node uses internal helper functions to make HTTP requests to Instantly endpoints.
  • Proper timezone handling depends on valid timezone strings from the provided list.
  • The node expects the Instantly API to be reachable and responsive.

Troubleshooting

  • Common Issues:

    • Invalid or missing required fields like Campaign Name or Schedule parameters may cause API errors.
    • Incorrect time formats (not HH:MM 24-hour) could lead to scheduling failures.
    • Using unsupported timezone values might cause unexpected behavior.
    • Network or authentication issues with the Instantly API will prevent campaign creation.

  • Error Messages:

    • Errors from the Instantly API will be surfaced in the node output under an error property if "Continue On Fail" is enabled.
    • Typical error messages include validation errors for missing or invalid parameters.
    • Authentication failures indicate problems with the API key credential setup.

  • Resolutions:

    • Double-check all required properties are set correctly.
    • Use the exact time format and select timezones from the provided list.
    • Verify API credentials and network connectivity.
    • Enable "Continue On Fail" to capture errors per item without stopping the workflow.

Links and References

Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion