Getting Started with Xurrent iPaaS

What is Xurrent iPaaS?

Xurrent iPaaS is an enterprise-grade platform that automates workflows between cloud and on-premises apps. It combines a powerful orchestration engine with a visual interface, allowing users to build complex integrations without deep coding knowledge.

🛡️ Enterprise-Grade Foundation

Built for reliability, security, and high performance. Xurrent handles mission-critical data across diverse environments at scale.

👥 Empowering All Integrators

Our "Single-Interface" philosophy removes technical barriers, providing a unified environment for all users:

• Non-Technical (Business Users): Build robust automations using a visual Trigger-Action mechanism and drag-and-drop Datapills.
• Technical (Developers/IT): Implement advanced logic like try-catch blocks, concurrency limits, and GitHub version control.

‍

Key Concepts

Before building your first automation, it is important to understand the core components of the Xurrent ecosystem.

Solutions

A Solution is a high-level organizational container that groups related integrations together. It acts as the "Command Center" for a specific business process. Inside a Solution, you manage Runbooks, Connections, and Environment Variables.

Runbooks

A Runbook is the individual automated workflow. It contains the logic and steps required to complete a specific task. Runbooks are modular; you might have one Solution for "Human Resources" containing multiple Runbooks like "New Hire Sync" and "Termination Access Revoke."

Connections

A Connection authorizes a Runbook to interact with apps like Salesforce, Jira, or N-Central.

• Authentication: Connections handle the secure handshake (OAuth, API Keys, or Tokens) between Xurrent and your third-party tools.
• Reusability: Connections are defined at the Solution level. Once a connection is established, it can be reused across multiple Runbooks within that same Solution.

Triggers

A Trigger specifies the event that initiates the steps in a Runbook.

• Event-based: Starts immediately when data is pushed to an endpoint (e.g., a Webhook Receiver).
• Scheduled: Starts on a predefined timeframe (e.g., the "Dynamic Scheduler").

Datatree and Datapills

Every step in a Runbook, starting with the Trigger, produces output data. This data is organized and made accessible through the Datatree.

• The Datatree: A structured hierarchy of all data fields generated by previous steps.
• Datapills: Individual data variables within the Datatree (e.g., User Name, Ticket ID). You use these pills to pass data dynamically between steps.

Input Fields and Mapping

Triggers and Actions include Input Fields that define how the workflow should execute. Inserting variables (Datapills) or Constants into these fields is called Mapping.

• Variable Mapping: Mapping a Datapill ensures that the value changes based on the trigger event (e.g., mapping a Salesforce Account Name to a Zendesk Org Name).
• Constant Mapping: Mapping a static value ensures the same data is sent every time (e.g., always adding the note "Synced via Xurrent" to every new record).

Jobs

A Job represents the flow of a single trigger event through the Runbook. Each time a trigger event occurs (e.g., one new ticket is created), the Runbook executes its actions, creating one unique Job.

• Success: A Job is successful when every step in the Runbook executes without error.
• Failure: If an error occurs, subsequent steps do not run unless specific error handling (like a try-catch block) is configured.

The Factory (Job Reports)

The Factory provides a high-level summary of all Jobs processed by a Runbook.

• Job Report: A list showing the date, time, status, and unique Job UUID for every execution.
• Job Details: Clicking a specific Job allows you to see the exact input and output data for every step in that run. This is the primary tool for troubleshooting and verifying your integration logic.