Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Campaign → Update

AI-generated

Overview

The node interacts with the Reachkit API to update a campaign's status. Specifically, it allows users to change the status of an existing campaign by providing its unique identifier and the desired new status. This is useful in marketing automation or customer engagement workflows where campaigns need to be activated or paused dynamically based on external triggers or conditions.

Practical examples include:

  • Automatically pausing a campaign when certain performance thresholds are met.
  • Activating a campaign at a scheduled time or after completing prerequisite steps in a workflow.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign to update.
Status The new status to set for the campaign. Options: "Active" (to enable the campaign) or "Paused" (to temporarily disable the campaign).

Output

The node outputs JSON data representing the updated campaign object as returned by the Reachkit API. This typically includes the campaign's current properties such as its ID, name, status, and other metadata reflecting the update operation.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Reachkit API.
  • The node sends requests to the Reachkit API endpoint at https://reachkit.ai/api/v1.
  • Proper configuration of the API credential within n8n is necessary for successful communication.

Troubleshooting

  • Invalid Campaign ID: If the provided campaign ID does not exist or is malformed, the API will likely return an error indicating the campaign was not found. Verify the campaign ID before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly configured and has sufficient permissions.
  • Status Value Issues: Only "active" or "paused" are accepted values for the status property. Providing any other value may result in validation errors.
  • Network or API Downtime: Temporary network issues or Reachkit API downtime can cause request failures. Retrying after some time or checking API status is recommended.

Links and References

Discussion