This connector serves as the foundation for integration code that powers a custom Xurrent App.

Secrets Changed Runbook (A)

Each iPaaS solution linked to a Xurrent App requires a single Secrets Changed runbook, triggered by the Secrets Changed event. When enabled, this runbook securely configures the provider's Xurrent account to send secrets to the iPaaS solution.

Automation Webhook Runbook (B)

For handling integration logic, create a runbook using the Automation Webhook trigger. This runbook executes whenever the webhook is invoked by the automation rules tied to the App offering.

Installation Changed Runbook (C)

To implement business logic during a customer's App installation, use the Installation Changed trigger. This trigger can be configured to respond to:

• New installations
• Updates
• App removals

Available Actions

Runbooks starting with the Installation Changed or Automation Webhook triggers can leverage the following actions to access App-related configuration data:

Client Credentials Token (1)

Outputs the client ID and secret for API access to the customer's Xurrent account.

Runbooks starting with the Installation Changed or Automation Webhook triggers can use this action without any further configuration to retrieve the correct credentials.

When using this action in another context the following 2 fields must be provided:

• customer_account_id: The account ID of the customer’s Xurrent account.
• app_reference: The reference of the app offering.

Retrieve App Config (2)

Outputs secrets and configuration values provided by the customer in Xurrent. The fields depend on the UI extension for the App offering.

All fields that need to be retrieved must be added to the Configuration schema. Secret values in the UI extension should be defined using the secret_string-type.

Runbooks starting with the Installation Changed or Automation Webhook triggers can use this action without any further configuration to retrieve the configuration details.

When using this action in another context the following 2 fields must be provided:

• customer_account_id: The account ID of the customer’s Xurrent account.
• app_reference: The reference of the app offering.

Authorization Code Token (3)

Outputs the client ID and secret for GUI access to the customer's Xurrent account.

Runbooks starting with the Installation Changed or Automation Webhook triggers can use this action without any further configuration to retrieve the correct credentials.

When using this action in another context the following 2 fields must be provided:

• customer_account_id: The account ID of the customer’s Xurrent account.
• app_reference: The reference of the app offering.

Update App Config (4)

Update the configuration values visible to the customer in Xurrent. The available fields depend on the UI extension related to the App offering.

Next to the custom fields it is also possible to update the disabled status of the App instance or to suspend the integration with a specific comment.

Runbooks starting with the Installation Changed or Automation Webhook triggers can use this action without any further configuration to update the configuration details.

When using this action in another context the following 2 fields must be provided:

• customer_account_id: The account ID of the customer’s Xurrent account.
• app_reference: The reference of the app offering.

Async URLs

Poll multiple URLs and return data when available. This action will check each URL and return the first one that has data available. Subsequent iterations will poll remaining URLs until all URLs have been processed.

External Application

To respond to changes in the external application additional runbooks can be created. When the trigger output schema includes the following 2 fields the available actions above can be used to retrieve the App configuration details.

• customer_account_id: The account ID of the customer’s Xurrent account.
• app_reference: The reference of the app offering.