Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Sequence → Update Variant

AI-generated

Overview

The node interacts with the Reachkit API to update a specific variant within a campaign sequence. This operation allows users to enable or disable a particular variant of a campaign sequence, which can be useful for managing different versions of marketing or communication sequences dynamically.

Common scenarios include:

  • Activating or deactivating a variant of an email or messaging sequence based on performance or testing results.
  • Managing campaign variants without needing to manually adjust settings in the Reachkit dashboard.
  • Automating campaign variant control as part of a larger workflow, such as enabling a new variant after certain conditions are met.

Example: A marketing team wants to disable an underperforming variant of a campaign sequence automatically when its engagement drops below a threshold. This node can be used in an n8n workflow to update the variant's enabled status accordingly.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign containing the variant to update.
Variant ID The unique identifier of the variant within the campaign sequence that should be updated.
Enabled Boolean flag indicating whether the variant should be enabled (true) or disabled (false).

Output

The node outputs JSON data representing the response from the Reachkit API after updating the variant. This typically includes details about the updated variant, such as its current enabled status and identifiers.

If the node supports binary data output (not indicated here), it would represent any files or attachments returned by the API, but this operation primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Reachkit API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://reachkit.ai/api/v1.

Troubleshooting

  • Invalid Campaign or Variant ID: If the provided IDs do not exist or are incorrect, the API will likely return an error. Verify the IDs before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
  • Network Issues: Connectivity problems may prevent the node from reaching the Reachkit API. Check network access and proxy settings if applicable.
  • Invalid Property Values: For example, setting Enabled to a non-boolean value might cause errors. Use correct data types as specified.

Links and References

Discussion