N-Central Connector

🔌 N-Central Connector

This connector facilitates a seamless alert-to-ticket workflow, allowing monitoring alerts from N-Central to automatically generate and update tickets.

⚡ Triggers

PSA - Generate Ticket

• Listens for Custom PSA Integration webhooks from N-Central to initiate ticket creation.

• Validates inbound credentials and extracts essential ticket data from the webhook payload.

• Automatically discards test tickets identified by IDs starting with TEST_NC_TICKET_ID.

⚡ Actions

Register PSA User

• Generates a secure password for an N-Central customer to facilitate multi-customer integration setups.

• Provides the necessary base endpoint URL and ticketing endpoint path for customer configuration.

Unregister PSA User

• Removes the generated password for a specific customer, effectively revoking their access to the PSA integration.

📥 Input Parameters

• ticket_url_template (String, Required): A template for linking tickets that must contain the {n_central_ticket_id} placeholder.

• user_name (String, Required): A unique identifier for the customer being registered or unregistered.

• psa_generate_ticket_runbook (Runbook, Optional): The specific runbook utilizing the "PSA - Generate Ticket" trigger.

📤 Output

• ncentralTicketId: The unique identifier of the ticket from N-Central.

• ticketUrl: The URL of the generated ticket returned to N-Central.

• password: The secret string password generated for a registered user.

• action: Indicates whether the triggered action was a "CREATE" or "UPDATE".

📌 Use Cases

• Automated ticket creation in Xurrent directly from N-Central monitoring alerts.

• Managing multi-customer PSA integrations in a multi-tenant environment.

• Customer deprovisioning by removing access credentials when no longer required.

⚠️ Notes

• Multi-customer Setup: For multi-tenant configurations, inbound credentials in the connection should be left empty while using Register/Unregister actions.

• Authentication: Uses inbound Basic Authentication for validating PSA trigger webhooks.

• Endpoint Configuration: Requires setting the Base Endpoint URL to the iPaaS platform host and the Ticketing Endpoint to the trigger path within N-Central.

‍