3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node updates settings related to a data connector, allowing users to configure how data is offloaded and managed in external systems. This is useful for scenarios where data synchronization and storage need to be controlled, such as enabling or disabling BigQuery integration, selecting an offload destination (None, PostgreSQL, or BigQuery), setting whether to purge data after synchronization, configuring remote PostgreSQL connection details, and defining scheduling parameters.

Practical examples include:

  • Enabling BigQuery integration to offload data for analytics.
  • Configuring a remote PostgreSQL database as the offload destination.
  • Setting up automatic purging of synchronized data to manage storage.
  • Scheduling periodic sync operations with custom timing.

Properties

Name Meaning
Is Big Query Enabled Boolean flag to enable or disable BigQuery integration.
Offload Destination Selects where to offload data: None, PostgreSQL, or BigQuery.
Purge After Sync Boolean flag indicating whether to purge data after synchronization completes.
Remote Postgre Config JSON object containing configuration details for connecting to a remote PostgreSQL server, including certificates and password.
Schedule JSON object defining scheduling parameters for data synchronization tasks.

Output

The node outputs JSON data reflecting the updated data connector settings. The structure corresponds to the properties sent in the update request, confirming the applied configuration. There is no indication that the node outputs binary data.

Dependencies

  • Requires an API authentication token or key to connect to the backend service managing data connector settings.
  • No explicit external libraries are indicated beyond standard HTTP request handling.
  • The node expects the user to provide valid JSON for complex properties like RemotePostgreConfig and Schedule.

Troubleshooting

  • Invalid JSON input: If the JSON provided for RemotePostgreConfig or Schedule is malformed, the node will likely fail. Ensure JSON syntax is correct.
  • Authentication errors: Missing or invalid API credentials will prevent successful updates.
  • Unsupported offload destination: Selecting an unsupported option or misconfiguring the remote PostgreSQL settings may cause errors.
  • Network issues: Connectivity problems to the backend service can result in timeouts or failures.

Links and References

  • No direct links available from the source code.
  • For further information, consult the documentation of the backend service managing data connector settings or the n8n community forums for similar node usage examples.

Discussion