Xurrent GraphQL Connector

🔌 Xurrent GraphQL Connector

This connector is optimized for bulk data synchronization and efficient searching of people and software configuration items (CIs) across multiple identifier fields.

⚡ Actions

Retrieve Xurrent Records

• Facilitates paginated retrieval of records from any Xurrent GraphQL connection.
• Supports filtering, ordering, and view selection for large result sets.

Fetch People from Xurrent for CMDB

• Searches for people across multiple identifiers like email, employee ID, and authentication ID.
• Returns a deduplicated array of person records with an identifier-to-person mapping.

Fetch Software from Xurrent for CMDB

• Searches for software configuration items by primary and alternate names.
• Includes status filtering to ensure only relevant assets are synchronized.

📥 Input Parameters

• Connection (String, required for retrieval): The GraphQL connection name, such as "services" or "people".
• Identifiers (Array, required for people search): List of identifiers to search for, encrypted for GDPR compliance.
• Software Names (Array, required for software search): Array of names used to match software CIs.
• Page size (Integer, optional): Controls the number of records or identifiers processed per batch (default: 100).

📤 Output

• Records: Deduplicated array of hashes containing the requested node fields.
• Identifier map: Mapping of matched identifiers to corresponding person or software records.
• Rate limit / Cost limit: Detailed information on API consumption and remaining query costs.
• Has next page: Boolean indicating if more data batches remain to be fetched.

📌 Use Cases

• Bulk Data Sync: Exporting large sets of teams, services, or CIs into external systems.
• CMDB Population: Resolving batches of external identifiers into verified Xurrent person records.
• Asset Discovery: Mapping software names to their respective configuration items for asset management.

⚠️ Notes

• Authentication: Uses OAuth2 Client Credentials flow; bearer tokens are cached until expiry.
• GDPR: Identifier fields for person searches are encrypted.
• Error Handling: Automatically reschedules jobs on HTTP 429 (Rate Limit) or HTTP 503 (Service Unavailable) responses.
• Internal Optimization: Uses batch-based iteration and aliased queries to maximize GraphQL efficiency.

‍