Xurrent App Connector

🔌 Xurrent App Connector

This connector serves as the base for integration code that powers custom Xurrent Apps, managing App Offering lifecycles, webhooks, and OAuth credentials via the Xurrent GraphQL API.

⚡ Triggers

Secrets Changed

• Receives and stores customer secrets (OAuth tokens, webhook policies) during provisioning or updates.

Installation Changed

• Fires when an App is installed, updated, or removed by a customer.

Automation Webhook

• Receives webhook payloads from App Offering automation rules with automatic JWT validation.

⚡ Actions

Client Credentials / Authorization Code Token

• Retrieves stored OAuth credentials for automated API (machine-to-machine) or user-facing GUI access to customer accounts.

Retrieve / Update App Config

• Reads or updates customer-specific configurations, secrets, App Instance custom fields, and suspension states.

Async URLs

• Sequential polling of multiple URLs, returning data as it becomes available with automatic backoff.

📥 Input Parameters

• app_reference (String, required): The target App Offering reference.
• customer_account_id (String, optional): Resolved automatically from trigger output or provided manually.
• config_schema (Schema Field, required for Retrieval): Defines fields to retrieve from the connection store or Xurrent API.
• custom_fields (Nested, optional for Update): Array of field objects to modify in the customer's account.

📤 Output

• customer_account_id: The unique account ID of the customer's Xurrent account.
• client_id / client_secret: Extracted OAuth credentials for the specified customer.
• config: Values matching the defined schema, including secret and non-secret fields.
• job.uuid: Unique execution ID for triggered runbooks.

📌 Use Cases

• Custom Integrations: Building tailored apps for external systems.
• Automated Deployment: Using blueprints to sync UI extensions and automation rules.
• Lifecycle Management: Handling onboarding and offboarding flows for marketplace Apps.

⚠️ Notes

• JWT Security: All inbound webhooks require automatic JWT validation using the ES256 algorithm.
• Constraint: Each iPaaS solution linked to a Xurrent App must have exactly one "Secrets Changed" runbook.
• Caching: OAuth credentials are stored in the outbound connection store for quick retrieval.

‍