Instantly icon

Instantly

Interact with Instantly API

Actions24

Overview

This node integrates with the Instantly API to manage email accounts, campaigns, leads, and analytics. Specifically, for the Account resource and the Resume Account operation, it allows users to resume a paused or inactive email account within their Instantly system. This is useful in scenarios where an email account was previously paused (e.g., to temporarily stop sending emails) and now needs to be reactivated to continue operations such as sending campaigns or managing leads.

Practical examples include:

  • Resuming an email account after resolving issues that caused it to be paused.
  • Reactivating accounts that were manually paused during maintenance or troubleshooting.
  • Automating workflows that toggle account states based on external triggers.

Properties

Name Meaning
Email Account The target email account to operate on. You can select from a list of existing email accounts or specify an email address directly.
Continue on Error Whether to continue execution if the account is already in the target state (e.g., trying to resume an already active account). When enabled, the operation will succeed with a warning message instead of failing.

Output

The node outputs JSON data representing the result of the resume operation on the specified email account(s). The output typically includes details about the account's updated status or any relevant metadata returned by the Instantly API.

If multiple input items are processed, the output is an array of JSON objects corresponding to each item.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Instantly API.
  • The node depends on the Instantly API endpoints to perform actions on accounts.
  • Proper configuration of the Instantly API credentials in n8n is necessary.
  • Network connectivity to Instantly's API endpoints is required.

Troubleshooting

  • Common Issues:

    • Attempting to resume an account that is already active may cause an error unless "Continue on Error" is enabled.
    • Invalid or missing email account identifiers can lead to failures.
    • API authentication errors if the API key credential is not set up correctly.
    • Network or API downtime causing request failures.

  • Error Messages:

    • Errors related to "account already in target state" can be resolved by enabling the "Continue on Error" option.
    • Authentication errors require checking the API key credential setup.
    • If the node fails to find the specified email account, verify the email address or selection method.

Links and References

Discussion