Connector for integrating with Xurrent using the GraphQL API with dynamic schema introspection.

Outbound Connection

An outbound connection is required for the query, mutation, and upload attachment actions.
It supports two authentication methods: OAuth2 Client Credentials and Personal Access Token.

Xurrent Webhook Trigger

The Xurrent Webhook trigger receives and processes webhook events from Xurrent.
JWT verification can be configured either on the inbound connection (shared across all
runbooks) or per trigger. Additional payload fields can be defined to automatically parse
webhook data into the correct types.

Xurrent Query Action (1)

Dynamically queries Xurrent records. Select a query object (e.g. people, requests,
configurationItems) and the input arguments and output fields are automatically generated
from the Xurrent GraphQL schema via introspection.

How it works

1. Select a query object (e.g. people, requests, configurationItems).
   The available objects are loaded from the Xurrent GraphQL schema once the outbound connection is configured.
2. The input fields (filters, views) and output fields are automatically generated based on the
   selected query object via schema introspection.
3. Use Include nested fields to select which related objects to include in the query result
   (e.g. include team fields when querying people).
4. Optionally set a Limit to cap the number of records retrieved.

This action is nested: it iterates over all matching records and executes the successor action
once per record. Connect subsequent actions to the output schema to process each record individually.

Clearing the schema cache

The GraphQL schema is cached in the connection store after the first introspection.
Check the Clear cache option to force a refresh (e.g. after Xurrent schema changes).

Xurrent Mutation Action (2)

Executes a Xurrent GraphQL mutation. Select a mutation (e.g. requestCreate, personUpdate,
noteCreate) and the input and output schemas are automatically generated.

How it works

1. Select a mutation (e.g. requestCreate, personUpdate, noteCreate).
   The available mutations are loaded from the Xurrent GraphQL schema once the outbound connection is configured.
2. The input fields and output fields are automatically generated based on the selected mutation.
3. Provide the mutation input either by mapping individual fields or as a JSON object.

Attaching files

To attach files to a record (e.g. a note), first use the Upload Attachment action to upload
the file. Then use the returned storage_key as the key value in the mutation's attachment input.

Clearing the schema cache

The GraphQL schema is cached in the connection store after the first introspection.
Check the Clear cache option to force a refresh (e.g. after Xurrent schema changes).

Upload Attachment Action (3)

Uploads a file to Xurrent via the attachmentStorage GraphQL query.
Returns a storage key that can be used as AttachmentInput in subsequent mutations
(e.g. adding a note with an attachment via noteCreate).

How it works

4. The action queries the Xurrent attachmentStorage endpoint to obtain upload credentials
   and a pre-signed upload URI.
5. The file is uploaded directly to the storage provider (e.g. Amazon S3) using a multipart POST.
6. The returned storage key identifies the uploaded file in Xurrent's storage.

Using the storage key

Use the storage_key output as the key value in any mutation that accepts AttachmentInput.
For example, when creating a note with an attachment via noteCreate, map the storage_key
to the attachment's key field.

Content type detection

If no content type is specified, it is automatically detected from the file name extension.