Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation deletes a scheduler entry identified by its unique ID. It is useful in scenarios where scheduled tasks or jobs need to be programmatically removed from a system, such as canceling automated reports, stopping recurring notifications, or managing timed workflows.

For example, if you have a scheduler that triggers data backups every night, and you want to stop this schedule, you would use this operation to delete the corresponding scheduler by its ID.

Properties

Name Meaning
X USER ID User Id (string) - identifies the user making the request; sent as a header named X-USER-ID. This is required.
Id Scheduler ID (number) - the unique identifier of the scheduler to delete. This is required.

Output

The output JSON typically contains the response from the API confirming the deletion of the scheduler. This may include status information or confirmation messages indicating whether the deletion was successful.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the Connect Secure API.
  • The node depends on the external Connect Secure API service to perform the deletion.
  • Proper configuration of the API credentials within n8n is necessary.
  • The X-USER-ID header must be provided to identify the user context for the operation.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid or non-existent scheduler ID: Attempting to delete a scheduler that does not exist will likely result in an error. Verify the scheduler ID before deletion.
  • Authentication errors: If the API key credential is missing or invalid, the request will fail. Confirm that the API credentials are properly configured.
  • Network or API downtime: Connectivity issues or API service outages can cause failures. Check network connectivity and API status.

Links and References

  • Refer to the Connect Secure API documentation for detailed information about the scheduler deletion endpoint and required headers.
  • n8n documentation on how to configure API credentials and use HTTP headers in nodes.

Discussion