Xurrent Connector

🔌 Xurrent Connector

This connector is the primary tool for interacting with the Xurrent platform. It uses GraphQL introspection to automatically generate input and output schemas, ensuring that fields always reflect the current Xurrent data model.

⚡ Triggers

Xurrent Webhook

• Receives and processes inbound webhook events from Xurrent in real time.
• Supports optional JWT signature verification for enhanced security.
• Use Case: Reacting to record changes, such as a request being completed or a task updated.

⚡ Actions

Xurrent Query

• Dynamically queries Xurrent records (e.g., people, requests, configuration items).
• Automatically handles pagination for connection-type queries.

Xurrent Mutation

• Executes GraphQL mutations to create, update, or delete records.
• Input schemas are generated dynamically from the Xurrent data model.

Upload Attachment

• Uploads files to Xurrent storage and returns a storage key.
• The storage key is then used in mutations (like noteCreate) to attach the file to a record.

📥 Input Parameters

• Query object (String, Required for Query): The GraphQL query field name, such as people or requests.
• Mutation (String, Required for Mutation): The GraphQL mutation name, such as requestCreate.
• File content (Binary, Required for Upload): The raw binary content of the file.
• Refresh schema (Boolean, Optional): Clears the cached GraphQL schema to fetch the latest model from Xurrent.

📤 Output

• nodes: An array of matching records generated from the GraphQL type.
• storage_key: The unique key for an uploaded file, used in AttachmentInput.
• ratelimit/costlimit: Information regarding API request limits and query costs.

📌 Use Cases

• Synchronizing Data: Detecting changes via webhooks and pushing updates to external systems.
• Record Creation: Creating Xurrent requests or notes based on external events.
• File Management: Attaching documentation or logs to Xurrent records.

⚠️ Notes

• Nested Execution: The Query action is a nested action that iterates over all matching records.
• Caching: GraphQL schemas are cached after the first introspection; use "Refresh schema" if the Xurrent data model changes.
• Rate Limiting: Includes automatic backoff handling for 429 (Rate Limit) and 503 (Service Unavailable) responses.

‍