Skip to main content

➕ Create New Connector

Connectors in SyncNow share common settings, but each may have specific configurations, behaviors, and limitations. For detailed information about a particular connector, refer to the System Connector section.

⚙️ System Connector Settings​

Edit System
  • Name: The display name for your connector.
  • Type: The system type (e.g., Jira, Azure DevOps, ServiceNow, etc.).
  • Allow Self-Signed Certificate:
    Enable this option to allow connectivity if the target system uses a self-signed certificate.
    warning

    It is not recommended to use self-signed certificates in a production environment. Enable this only for testing purposes.

  • URL: The base URL of the external system.
  • Username and Password: Credentials for authenticating with the target system.
  • Username and Token: Use this option if the system supports token-based authentication (recommended for enhanced security).
  • API Version: Specify the API version if required. Refer to the System Connector documentation for version compatibility and recommendations.

🔒 Webhook Security​

Webhooks enable continuous, real-time synchronization and are automatically registered when you activate a sync process.
You can configure webhook security using the following options:

  1. Anonymous Notifications
    Enable this if the source system (e.g., Azure DevOps, Jira, ServiceNow) only supports anonymous notifications to SyncNow.

    warning

    If you enable anonymous notifications, we strongly recommend adding IP restrictions for security.

  2. Allowed IP Addresses
    Specify trusted IP addresses or IP ranges (in network/mask format, separated by commas) from which SyncNow will accept webhook notifications.

info

For security reasons, always use IP restrictions if anonymous notifications are enabled.

Tip:
Review the documentation for your specific connector type for additional configuration options, best practices, and limitations.