documentation

Choose surviving values using minimum-value logic.

Overview The Minimum Value strategy is the precise inverse of the Maximum Value rule. It is a deterministic survivorship logic designed to identify and preserve the smallest data point found among duplicate records. This strategy is particularly valuable when "less" signifies "better," "earlier," or "higher priority." By filtering out higher values, UnifyApps ensures that your Golden Record reflects the most conservative estimate, the earliest historical event, or the highest rank (lowest integer) available in your data ecosystem. The Logic: Lowest Wins When configured, the system evaluates the target field across all conflicting records within a match group. Selection Criteria: As defined in the configuration panel, the system will "Select the lowest value among duplicates". Behavior by Data Type: Numeric Data: It selects the smallest number (e.g., comparison between $150 and $120 results in $120 ). Date/Time Data: It selects the earliest chronological timestamp (e.g., determining the "First Created Date"). Configuration Options Similar to other quantitative strategies, Minimum Value is most effective when applied granularly: Primary Strategy You can assign this as the main rule for specific fields via the Custom Strategy configuration. This is ideal for fields where the lowest value represents the "truth" or the desired business state (like a queue position). Fallback Strategy It serves as an effective tie-breaker in Fallback Strategies. If a primary rule (like "Source System") fails because a high-priority source is missing data, the Minimum Value rule can ensure that a valid, conservative value is picked from the remaining sources rather than leaving the field empty.

Salesforce

Salesforce is a cloud-based software suite for customer relationship management

Using Salesforce streamlines managing customer relationships and sales processes. It helps track customer interactions, manage sales deals, and analyze data for better decisions.Salesforce ensures your customer data is protected with strong security. It's a tool for boosting sales efficiency and keeping customer information organized and safe. Integrating your application with Salesforce allows you to leverage Salesforce's extensive CRM capabilities. Authentication Before you begin, make sure you have the following information: Connection Name : Assign a descriptive name for this connection. This name is essential as it helps identify this specific Salesforce connection within UnifyWorkflow. Domain : This information directs your application to connect to the correct Salesforce instance. If your Salesforce instance URL is https://mycompany.my.salesforce.com , then your domain is mycompany.my.salesforce.com . Authentication Type : There are two options for authenticating the connection to your salesforce account - OAuth & JWT Token . OAuth After entering the Domain of your company, click Authorise . It will redirect you to the login page of Salesforce, from where you can login to your Salesforce account to directly authorize and connect your salesforce account in UnifyApps. Salesforce JWT Token Step 1: Create a Private Key and Digital Cert Authorizing an org with the org login jwt command requires a digital certificate and the private key used to sign the certificate. You can use your own private key and certificate issued by a certification authority. Alternatively, you can use OpenSSL to create a key and a self-signed digital certificate. Using a private key and certificate is optional when you authorize an org by logging into a browser. This process produces two files: server.key —The private key. You specify this file when you authorize an org with the org login jwt command. server.crt —The digital certificate. You upload this file when you create the required connected app. Open a terminal (macOS and Linux) or command prompt (Windows). If necessary, install OpenSSL on your computer. To check whether OpenSSL is installed on your computer, run the which command on macOS or Linux or the where command on Windows. Create a directory for storing the generated files, and change to the directory. Generate a private key, and store it in a file called server.key You can delete the server.pass.key file because you no longer need it. Generate a certificate signing request using the server.key file. Store the certificate signing request in a file called server.csr . Enter information about your company when prompted. Generate a self-signed digital certificate from the server.key and server.csr files. Store the certificate in a file called server.crt . Step 2 : Create a External Client App Salesforce CLI requires a external client app in the org that you're authorizing. A external client app is a framework that enables an external application, in this case Salesforce CLI, to integrate with Salesforce using APIs and standard protocols, such as OAuth. We provide a default external client app when you authorize an org with the org login web command . For extra security, you can create your own external client app in your org using Setup and configure it with the settings of your choice. You're required to create a connected app when authorizing the org with the org login jwt command. Log in to your org. From Setup , enter App Manager in the Quick Find box, then select App Manager . In the top-right corner, click New External Client App . Update the basic information as needed, such as the connected app name and your email address. Select Enable OAuth Settings . For the callback URL, enter http://localhost:1717/OauthRedirect . fIf port 1717 (the default) is already in use on your local machine, specify an available one instead. Then update your sfdx-project.json file by setting the oauthLocalPort property to the new port. For example, if yo

Zoho Invoice

Integrating your application with Zoho Invoice enables seamless invoicing, payment tracking, and customer management. It allows businesses to automate billing workflows, generate professional invoices, monitor payment statuses, and streamline financial operations efficiently. Authentication: Connecting your application with Zoho Invoice enables smooth invoice creation, real-time tracking, and automated financial workflows. Before you begin, ensure you have the following information : Connection Name: Choose a meaningful name for your connection. This helps you identify it within your application or integration settings (e.g., "MyAppZohoInvoiceIntegration"). Domain : Select your Zoho domain. Organization ID : Your Zoho Invoice organization ID. OAuth-Based Authentication: Zoho Invoice uses OAuth 2.0 for secure authentication. Go to the Zoho Developer Console. Create a new client. Choose Server-based Applications. Provide required details (Client Name, Redirect URI, etc.). After creation, note the following: Client ID Client Secret Generate a Grant Token using the authorization URL. Exchange the grant token for: Access Token Refresh Token Use the access token in API requests for authentication. Actions Action Name Descriptions Add task Add a task in Zoho Invoice Create contact Creates a contact in Zoho Invoice Create expense Create a expense in Zoho Invoice Create invoice Creates an invoice in Zoho Invoice Create project Creates a project in Zoho Invoice Delete contact Delete a contact in Zoho invoice Delete invoice Delete an invoice in Zoho invoice Delete project Delete a project in Zoho invoice Delete task Delete a task in Zoho invoice Get contact details Get the contact details in Zoho Invoice Get expense Get expenses in Zoho Invoice Get expenses in Zoho Invoice Get an invoice details in Zoho Invoice Get project details Get the project details in Zoho Invoice Get task details Get the task details in Zoho Invoice List expenses List expenses from Zoho Invoice List Invoices List invoices in Zoho Invoice Update contact Updates a contact in Zoho Invoice Update expense Update expense in Zoho Invoice Update invoice Updates an invoice in Zoho Invoice Update project Updates a project in Zoho Invoice Update task Updates a task in Zoho Invoice

Using repeatable

Displays dynamic lists/grids by repeating a component template for each data item. Takes an array of objects as input and creates multiple instances of the design. Essential for product catalogs, user lists, feeds. Configure data source, layout (list/grid)

The Repeatable component is a powerful tool for displaying dynamic lists or grids of data within your application. It works by taking a component or a group of components you design (a template) and repeating it for each item in a given data source. This is essential for building common UI patterns like product catalogs, user lists, task lists, comment threads, news feeds, and any other interface that needs to display a variable number of similar items. Key Properties / Configuration (Content Tab) The Content tab is where you connect your data and configure the core behavior of the Repeatable component. Data Source: This is the most important property. It requires an array of objects to function. Each object in the array will represent one instance of the repeated content on the screen. You can either bind this to a data source that returns data in the correct format (e.g., from an API call or a Unify Data Object). Or, you can manually enter a static array for prototyping, for example: {{ [{"id":"1","name":"Item 1"},{"id":"2","name":"Item 2"}] }} Primary Key: What it is: The name of a field in your data source objects that contains a unique identifier for each item (e.g., id, email, product_sku ). In the example above, id would be the primary key. Why it's needed: This allows the platform to efficiently track, update, and manage interactions for each individual item in the list, especially when items are selected or changed. Auto Select: What it is: This setting determines if an item should be automatically selected when the list first loads. Options: None : No item is selected by default. First Item : The first item from your data source is automatically selected. Last Item : The last item from your data source is automatically selected. Why it's useful: Ideal for creating master-detail layouts where selecting an item in the list displays its details in another part of the page. Auto-selecting the first item can populate the detail view on page load. Collect Child States: What it is: A toggle switch to gather information from components inside your repeated items. Why it's useful: Turn this ON if you have input components (like text fields, toggles, or dropdowns) within your repeatable template and you need to collect the values from all instances at once (e.g., submitting a form that contains a list of items with quantities). When off, the component is more performant as it doesn't track these individual states. Other Properties Add-ons: Configure additional functionalities like search or filtering for the list. Interactions: Define actions that can be triggered by events on the Repeatable component itself, such as On Row Clicked. Permissions: Standard Unify Applications feature to control the visibility of the entire component based on user roles. Binding Data to Child Components To make the Repeatable component useful, you need to display the data for each item. Any component you place inside the Repeatable (your " template ") gets access to a special currentItem object. currentItem: This object represents the data for a single item in the Data Source array for that specific instance. How to use it: You can bind the properties of currentItem to the components inside the Repeatable. For example, if your template has a Text component, you could set its value to {{currentItem.name}} to display the name of each item from your data source. Working with Selected Items A powerful feature of the Repeatable component is its ability to track which item a user has selected. This is the key to building interactive, master-detail interfaces.The component does this by exposing a special property called selectedItem. This property is an object that holds all the data for the currently selected row (e.g., {"id": "user-01", "name": "Alice"} ). When a user clicks on an item in the list, the Repeatable component triggers an On Select Item event. By navigating to the Interactions tab for your Repeatable component and adding an action to this

Encryption

Secure your data with powerful encryption

AES ( Advanced Encryption Standard ) is a symmetric encryption algorithm widely used to secure data . It encrypts data using the same key for both encrypting and decrypting, making it essential to keep the key secret. This guide will walk you through using AES encryption and decryption transformations to protect sensitive data, such as PII (Personally Identifiable Information). AES Encryption AES encryption allows you to secure any field with a 256-bit encryption key. Steps to Apply Encryption AES Encryption Key : This is the 256-bit encryption key required to encrypt the data. Example : 6b71RouelDY2xLFfy1x0oYXq3oUDkfuc. Initialization Vector (IV) : An IV is a 128-bit value used with the encryption key to enhance security. Example : d4QaIQMb8RbOG5ai. Testing Encryption After applying the encryption transformation, test it to ensure it is working correctly. You should compare the encrypted output with expected values to verify the encryption process. Example: Encrypting a customer's social security number before storing it in a database: Input : Sample String Encrypted Output : enhTmMxQS+2o1Oi1nvnpxA== AES Decryption AES decryption uses the same symmetric algorithm to convert encrypted data back to its original form. Steps to Apply Decryption AES Decryption Key : Enter the 256-bit encryption key used for encryption. Example : 6b71RouelDY2xLFfy1x0oYXq3oUDkfuc. Initialization Vector (IV) : Provide the same 128-bit IV used during encryption. Example : d4QaIQMb8RbOG5ai. Testing Decryption After applying the decryption transformation, test it to ensure it is working correctly. You should compare the decrypted output with the original data to verify the decryption process. Example: Decrypting a customer's social security number to verify identity: Encrypted Input : enhTmMxQS+2o1Oi1nvnpxA== Decrypted Output : 123-45-6789 Best Practices Key Management : Implement a secure key management system to handle encryption keys. This may involve using key management services (KMS) provided by cloud providers. Regular Audits : Regularly audit your encryption and decryption processes to ensure they comply with security standards and best practices.

Delay

Unify Automations

The Delay Node in UnifyApps enables precise workflow timing by pausing actions until a specific date or for a set duration, enhancing control and scheduling flexibility.

Overview The Delay Node in UnifyApps is designed to manage timing within automation workflows by introducing pauses at key steps. It provides precise control over scheduling with options to delay actions until a specific date and time or for a set duration between actions. Use Case Example Schedule Delay Until- Scheduled Customer Follow-Ups When a lead reaches a certain stage in a sales pipeline, the automation can use Schedule Delay Until to follow up on a specific date, ensuring timely outreach and engagement. Set Delay Duration - Staggered Marketing Campaign Launch For a marketing campaign, use Set Delay Duration in the automation to introduce timed gaps between campaign rollouts across channels, simultaneously optimising reach without overwhelming audiences. Actions in Delay Schedule Delay Until The " Schedule Delay Until " action pauses an automation sequence until a specified date and time, enabling actions to occur precisely when needed. This is ideal for time-bound tasks that require specific future scheduling. Set Delay Duration The " Set Delay Duration " action introduces a fixed interval between actions in automation, allowing for controlled pauses between sequential steps. This is beneficial when actions need gradual timing rather than instant execution. Notes The Delay Node by UnifyApps provides essential actions for managing timing within automation workflows, enabling users to introduce precise delays between tasks. To make the most of these functionalities, keep in mind the following best practices: Schedule delays thoughtfully to enhance user experience. Utilise duration settings for optimal pacing in automation. Implement error handling to maintain workflow integrity. Monitor for potential timing conflicts in complex sequences. By effectively leveraging the Delay Node, users can create more responsive and organised workflows tailored to their operational needs.

Manual Field Creation

Overview While importing fields from external sources is efficient for bulk schema generation, Manual Field Creation offers the highest level of granular control over your data model. This method is essential when defining custom business logic, creating internal identifiers, or establishing fields that do not exist in any upstream source system. Through the New Field configuration panel, you can explicitly define every attribute of a data point, from its data type to its security properties and search behaviors. The Configuration Process To initiate this process, navigate to the Fields tab of your Entity and click the + Add Field button. The configuration is divided into two strategic sections: Basic Details This section defines the core identity and structural format of the field. Key: The unique, machine-readable identifier for the field (e.g., customer_id ). This key is used in API calls and internal references. Display Label: The human-readable name that appears in the user interface and reports (e.g., "Customer ID"). Description: An optional field to document the purpose of the data point for other developers or data stewards. Field Type: Specifies the data format. Common options include String , Integer , Date , and Boolean . Default Value: Allows you to set a static value that will be automatically populated if the incoming data record is null or missing this attribute. 2. Additional Settings These settings control how the UnifyApps platform indexes, validates, and secures the data stored in this field. Filterable: Enables this field to be used as a filter criteria in dashboards and queries (e.g., "Show all records where Status = Active"). Searchable: Indexes the field for full-text search, allowing users to find records by typing values contained within this field. Hashable: Applies a cryptographic hash to the data. This is often used for high-performance matching algorithms where exact text comparison is costly. Sortable: Allows lists and reports to be ordered in ascending or descending order based on the values in this field. Primary Key: Designates this field as the unique identifier for the record. Every Entity must have at least one Primary Key to ensure data integrity. Is Required: Enforces a validation rule that prevents records from being saved if this field is empty. Secure Field: Encrypts the data at rest. This is critical for handling Sensitive Personal Information (SPI) or Personally Identifiable Information (PII) to ensure compliance with privacy regulations.

Amazon Redshift as Source

Extract and synchronize data from Amazon Redshift using optimized S3-based snapshots for historical data and cursor-based incremental loading for real-time analytics integration.

UnifyApps enables seamless integration with Amazon Redshift as a source for your data pipelines. This article covers essential configuration elements and best practices for connecting to Redshift sources. Overview Amazon Redshift is a fully managed, petabyte-scale data warehouse service optimized for analytics workloads. UnifyApps provides native connectivity to extract data from Redshift clusters efficiently and securely, supporting both historical data loads and continuous data synchronization. Connection Configuration Parameter Description Example Connection Name* Descriptive identifier for your connection "Production Redshift Analytics" Host Address* Redshift cluster endpoint "redshift-cluster.abc123xyz.us-east-1.redshift.amazonaws.com" Port Number* Database port 5439 (default) User* Database username with read permissions "unify_reader" Password* Authentication credentials "********" Database Name* Name of your Redshift database "analytics_db" Server Time Zone* Database server's timezone "UTC" Connection* Method of connecting to the database Direct or Via SSH To set up a Redshift source, navigate to the Connections section, click New Connection , and select Amazon Redshift . Fill in the parameters above based on your Redshift environment details. Server Timezone Configuration When adding objects from a Redshift source, you'll need to specify the database server's timezone. This setting is crucial for proper handling of date and time values. In the Add Objects dialog, find the Server Time Zone setting Select your Redshift server's timezone This ensures all timestamp data is normalized to UTC during processing, maintaining consistency across your data pipeline. Data Extraction Methods UnifyApps uses specialized techniques for Redshift data extraction: Historical Data (Initial Load) For historical data, UnifyApps uses a snapshot-based approach: Data is extracted in chunks from Redshift tables These chunks are temporarily staged in Amazon S3 The data is processed and loaded into the destination S3 staging objects are automatically cleaned up after successful processing This method optimizes for Redshift's architecture and minimizes impact on your cluster performance. Live Data (Incremental Updates) For ongoing changes, UnifyApps implements cursor-based polling You must select a cursor field (typically a timestamp or sequential ID) The pipeline tracks the highest value processed in each run Subsequent runs query only for records with cursor values higher than the last checkpoint Recommended cursor fields are datetime columns that track record modifications Supported Data Types for Cursor Fields Category Supported Cursor Types Numeric INTEGER, DECIMAL, SMALLINT, BIGINT String VARCHAR, CHAR (lexicographically ordered) Date/Time DATE, TIMESTAMP, TIMESTAMPTZ, TIME, TIMETZ Ingestion Modes Mode Description Business Use Case Requirements Historical and Live Loads all existing data and captures ongoing changes Data warehouse migration with continuous synchronization Valid cursor field required Live Only Captures only new data from deployment forward Real-time dashboard without historical context Valid cursor field required Historical Only One-time load of all existing data Point-in-time analytics or compliance snapshot No cursor field needed Choose the mode that aligns with your business requirements during pipeline configuration. CRUD Operations Tracking When tracking changes from Redshift sources: Operation Support Notes Create ✓ Supported New record insertions are detected Read ✓ Supported Data retrieval via full or incremental queries Update ✓ Supported Updates are detected as new inserts with the updated values Delete ✗ Not Supported Delete operations cannot be detected Supported Data Types Category Supported Types Integer SMALLINT, INTEGER, BIGINT Decimal DECIMAL, REAL, DOUBLE PRECISION Date/Time DATE, TIME, TIMESTAMP, TIMESTAMPTZ, TIMETZ String CHAR, VARCHAR Boolean BOOLEAN Other SUPER, VARBYTE All standard Redshift data types

Angular SDK

Embedded Integrations

Angular library for integrating UnifyApps SDK into Angular applications.

Overview Angular library for integrating UnifyApps SDK into Angular applications. Step-by-Step Instructions Step 1: Installation Install the package using npm or your preferred package manager: Step 2: Obtain Credentials To get the required credentials, Contact support@unifyapps.com Required values: HOST_NAME IDP_ID APPLICATION_ID Replace these values in your component configuration. Step 3: Setting Up Basic Setup Import the UnifyAppsComponent in your Angular module or standalone component: Using with Template Reference You can access component methods using a template reference variable: Step 4: Configure Required Parameters unifyAppsSettings (required) Configuration object for UnifyApps SDK: host (required) - The base URL of the host application token (optional) - The temporary session id to authenticate the user identityProviderId (required) - Identity provider, required for authentication applicationId (required) - Application ID: The unique identifier of the application . Retrieve this from the application's overview page in the UnifyApps platform isApplicationPublic (optional) - Whether the application is public pageId (optional) - Page ID: If a specific page needs to be opened . Retrieve this from inside application's page settings (Page Slug) pageInputs (optional) - Page inputs required to render the application's page theme (optional) - Theme to be set for the application. Available themes: light , dark , system . Default is light onPageEvent (optional) - Callback function for page events Signature: (event: { eventType: string; eventPayload: unknown }) => Promise<void> | void Parameters: eventType (string): Name of the emitted page event eventPayload (unknown): Payload with which this event was triggered appConfig (optional) - Application configuration showCopilotChatLauncher (optional) - Show copilot chat launcher in the app loader (optional) - Loader configuration type (optional): Loader type (' shimmer ' | ' spinner ') locale (optional) - Locale to override the locale selection logic client (optional) - Client type: ( ' unifyapps ' | ' external ' ) deployedVersion (optional) - Deployed version renderInShadowDom (optional) - Use ShadowDom to wrap the SDK container element networkHeaders (optional) - An object containing any custom headers to be sent with each request to the host application containerEl (optional) The element where the application will be rendered. Can be: A string selector (e.g., ' #my-container ' or ' .container ') An HTMLElement reference If not provided, it defaults to the component’s host element. Component Methods update(updatedSettings: Partial<UnifyAppsSettings>) Update any of the UnifyApps global settings. goToPage(options) Navigate to a specific page. setTheme(theme: 'light' | 'dark' | 'system') Set the theme of the application.

Microsoft SQL Server

Integrate your app with Microsoft SQL Server to enable robust data management, seamless querying, and real-time business insights

Microsoft SQL Server is a relational database management system that supports data storage , retrieval , and management . Integrating it with your application enables seamless access to advanced database functionalities for efficient data handling and operations. Authentication Before you begin, make sure you have the following information: Connection Name : Choose a meaningful name for your connection. This name helps you identify the connection within your application or integration settings. It could be something descriptive like "My App SQLServer". Database Host : The SQLServer database host's IP address or DNS.Note: For URL-based hostnames, exclude the http:// or https:// part. For example, if the hostname URL is https:/sqlserver-qa.xxxx.ap-south-1.rds.amazonaws.com, enter sqlserver-qa.xxxx.ap-south-1.rds.amazonaws.com. Database Port : The port on which your SQLServer server listens for connections. Default value: 1433. Database User : The authenticated user with permission to read tables in your database. Database Password : The password for the database user. Schema Name : This represents the schema or user namespace within the PostgreSQL database containing tables, views, and other objects. Connect through SSH : Enable this option to connect to Unifyapps using an SSH tunnel instead of directly connecting to your SQLServer database host. This provides additional security to your database by not exposing your SQLServer setup to the public. SSH Host : Enter the hostname or IP address of the SSH server that acts as the gateway to your database. Example: ssh.example.com or 203.0.113.1 SSH Port : Specify the port number on which the SSH server listens. The default is usually 22, but it may differ for security reasons. SSH User: Provide the username for authenticating with the SSH server. This is typically the user account on the remote server with the necessary permissions. RSA Private Key : Provide the RSA private key corresponding to the public key stored on the SSH server. Client Certificate : Obtain a valid client certificate from a trusted Certificate Authority (CA). This certificate authenticates your client to the database server. SSL Certificate Key : This private key corresponds to your client's certificate. Server Certificate : Obtain the database server's SSL certificate. This certificate verifies the server's identity to your client. Often provided by your database administrator or hosting service. Actions The following actions are available to create custom automations on the Unifyapps platform: Action Description Create Snapshot of Table Creates a snapshot of a table and stores it in S3. Execute SQL statement Executes a SQL statement in Microsoft SQL server Insert row Inserts row into a table in Microsoft SQL server List all databases Lists all databases in Microsoft SQL server List tables for a schema Lists tables for a schema in Microsoft SQL server Replicate schema Create/alter table schema in SQL Server Replicate rows (Batch) Replicate batch of rows to table in SQL Server Insert rows(Batch) Insert batch of rows in a table in SQL Server Select rows using custom SQL (Batch) Select rows using custom SQL in SQL Server Export query result (File) Export query result as a CSV file Get table schema Get table schema for SQL Server Bulk load from an on-prem file Bulk load rows into a table in SQL server from an on-prem file Select rows Select rows in a table in SQL Server Update rows (Batch) Update batch of rows in a table in SQL Server Update rows Update rows in a table in SQL Server Upsert rows Upsert row in a table in SQL Server Upsert rows (Batch) Upsert batch of rows in a table in SQL Server Delete rows (Batch) Delete rows in a table in SQL Server Execute stored procedure Execute stored procedure in SQL Server Run long query using custom SQL Run long query using custom SQL in SQL Server Triggers The following actions are available to create custom automations on the Unifyapps platform: Trigger Description New/up

QuickBooks as Source

Extract comprehensive accounting data with OAuth authentication, supporting historical sync and real-time changes for financial reporting and business intelligence.

Overview QuickBooks Online is a cloud-based accounting software widely used by small and medium businesses for financial management, invoicing, and bookkeeping. UnifyApps provides native connectivity to extract data from QuickBooks environments efficiently and securely, supporting historical data synchronization and continuous change tracking. Connection Configuration Parameter Description Example Connection Name * Descriptive identifier for your connection "Production QuickBooks Accounting" Authentication Method * OAuth authentication type OAuth or OAuth with Client Credentials Client ID * Application identifier from Intuit Developer "your_client_id" Client Secret * Application secret from Intuit Developer "your_client_secret" Redirect URI * OAuth callback URL "https://your-app.com/callback" Company ID * QuickBooks company identifier "123456789012345" To set up a QuickBooks source, navigate to the Connections section, click New Connection, and select QuickBooks. Complete the form with your QuickBooks application credentials. Prerequisites and Setup Before configuring QuickBooks as your source, ensure you have: Client ID and Secret Setup These credentials are needed to authenticate your application. Follow these steps to obtain them: Log in to Intuit Developer Go to the Intuit Developer Dashboard and sign in Access your developer account at https://developer.intuit.com Create or Select an App From the Dashboard, click ' Create an App ' or select an existing app Choose the appropriate app type for your integration needs Navigate to Keys & Credentials In the app menu, select ' Keys & Credentials ' Here, you will find your Client ID and Client Secret under either Development or Production environment Use Development credentials for testing and Production credentials for live environments Set Redirect URI After obtaining your Client ID and Secret, follow these steps to set the Redirect URI: Access App Settings Go to the ' Settings ' tab in the left-hand menu of your Intuit Developer app Configure Redirect URIs Select ' Redirect URIs ' Add your Redirect URI (e.g., the URL where OAuth 2.0 will send the authorization code) Click 'Save' to apply the changes Verify Configuration Ensure the redirect URI matches exactly with your application's callback endpoint Multiple redirect URIs can be configured for different environments Authentication Methods OAuth Authentication Standard OAuth 2.0 flow for QuickBooks Online integration: Authorization Request : User is redirected to QuickBooks for authorization Authorization Grant : User grants permission to access their QuickBooks data Access Token : Application receives access token for API calls API Access : Use access token to make authenticated requests to QuickBooks API Required fields: Client ID : Your application's client identifier Client Secret : Your application's client secret Redirect URI : The callback URL for OAuth flow OAuth with Client Credentials Enhanced OAuth flow with additional client credential validation: Client Authentication : Application authenticates using client credentials Authorization Flow : Standard OAuth authorization process Token Exchange : Secure token exchange with client credential verification API Access : Authenticated access to QuickBooks data Required fields: Client ID : Your application's client identifier Client Secret : Your application's client secret Redirect URI : The callback URL for OAuth flow Additional Credentials : Enhanced client credential parameters Ingestion Mode QuickBooks as Source supports Historical and Live ingestion mode only: Mode Description Business Use Case Historical and Live Loads all existing data and captures ongoing changes Complete accounting data migration with continuous synchronization This mode ensures comprehensive data extraction from your QuickBooks account, including all historical records and real-time updates to maintain data consistency across your pipeline. Data Synchronization Capabilities Supported Operations

Module

A group of components which can be reused across multiple applications and pages

Overview Modules are reusable groups of components that can be embedded in multiple pages within the same application—or even across different applications. They help reduce duplication, streamline maintenance, and ensure consistent UI/UX across your apps. Think of modules like mini-pages that can be reused wherever needed. Common use cases include login screens, settings pages, confirmation modals, and file upload dialogs. Whenever you update a module, the changes automatically reflect everywhere it's used—saving you time and effort. How to Use? 1. Application-Based Modules These are standalone modules that can be used across multiple applications. Go to the New Application tab. Click Create Module . This opens a single-page module editor. To add this module to any app, open the Components Panel , search for Module , and select it. Select your module from the dropdown and configure its appearance and interactions. 2. Page-Based Modules These modules are tied to a specific application and can't be reused across others. Inside your app, click the Page Dropdown > New > Module . You’ll be redirected to configure your new module. Use the Content Tab in the module component to link this module from the dropdown. Both types support full configuration, appearance customization, and interaction logic. Best Practices Reusability First: Avoid app-specific logic. Design modules to work in various apps without modification. Consistency: Match styles, spacing, and interaction patterns of the parent app to create a seamless user experience. Responsive Design: Ensure your modules adapt well across desktop, tablet, and mobile views.

Avatar Group

Avatar Groups are customizable UI components that display collections of user avatars in a compact format, supporting both static configurations and dynamic data mapping for team displays and collaborative interfaces.

Overview The Avatar Group component provides a visual representation of multiple users or entities in a compact, organized display. It allows you to showcase a collection of avatars with customizable appearance and behavior. Avatar Groups can display both static lists of avatars or dynamically mapped data from your application sources, making them perfect for team displays, user lists, and collaborative interfaces. Key Properties Type Selection The Avatar Group offers two primary configuration types: Mapped : Connects to dynamic data sources to populate avatars automatically Static : Manually configured avatars with fixed properties Avatar Representation Each avatar within the group can be customized with: Icon or Image : Choose between symbolic icons or actual images Avatar ID : A unique identifier for each avatar in the group Fallback Text : Alternative text displayed when images fail to load Appearance Controls Size : Multiple size options from xxs to 2xl to fit your design needs Max Visible Avatars : Control how many avatars are visible at once Layout : Customize the arrangement and spacing of avatars Background : Set custom background colors and styles Border : Apply border styling to visually separate avatars Configuring an Avatar Group Creating a Static Avatar Group: Add the Avatar Group component to your page from the component library Select " Static " as the Type option Use the Avatars section to add individual avatars: Click the " + " button to add a new avatar Configure each avatar's properties (Avatar 1, Avatar 2, etc.) Use the trash icon to remove unwanted avatars Creating a Mapped Avatar Group: Add the Avatar Group component to your page from the component library Select " Mapped " as the Type option Configure the Mapped Avatars section: Select your data source Map the Avatar ID field to your data Choose between Icon or Image representation Set fallback text options Setting Avatar Appearance: Navigate to the Appearance tab Select the appropriate size for your avatars Set the maximum number of visible avatars Configure layout settings including spacing and alignment Customize background and border styling as needed Use Cases Team Member Display Use Avatar Groups to represent team members working on a project or assigned to a task. Configure the component to display user profile images with appropriate fallback text for accessibility. Collaborative Workspaces Implement Avatar Groups to show active participants in collaborative documents or workspaces. Connect to live data sources to dynamically update as users join or leave the space. Activity Indicators Pair Avatar Groups with interaction components to create interactive user listings that display activity status, online presence, or participation levels. User Selection Interfaces Use Avatar Groups in user selection interfaces, allowing users to quickly identify and select colleagues for sharing, permissions, or collaboration. Best Practices Optimal Visual Presentation Size Consistency : Maintain consistent avatar sizes throughout your application Limited Visibility : Set appropriate " Max Visible Avatars " to prevent overcrowding Adequate Spacing : Ensure enough spacing between avatars for clear visual separation Performance Considerations For large datasets, implement pagination or filtering when displaying Mapped Avatar Groups Use appropriate image optimization for avatar images to ensure fast loading times Accessibility Always provide meaningful fallback text for each avatar Ensure sufficient color contrast between avatars and background Interactive Capabilities Avatar Groups can be enhanced with interactive features: Click Actions : Configure what happens when users click on an avatar Hover States : Define visual feedback when users hover over avatars Selection States : Implement visual indicators for selected avatars Permissions Control who can see or interact with Avatar Groups by setting visibility permissions based on user roles or other contextual facto

Gainsight

Integrate your app with Gainsight to enhance customer success, automate engagement workflows, and drive retention

Gainsight is a customer success platform that helps businesses drive retention, reduce churn, and maximize customer growth through data-driven insights and automation. It offers tools for customer health monitoring, engagement, and lifecycle management. Integrating Gainsight enhances customer retention, reduces churn, and drives growth through data-driven insights and automation. Authentication Before you begin, make sure you have the following information: Connection Name : Choose a descriptive name for your connection (e.g. "MyAppGainsightIntegration") to easily identify it within your integration settings. Authentication Type : Gainsight API uses OAuth 2.0 for secure authentication and authorization. OAuth 2.0 Based Authentication Log in to your Control environment and navigate to Integrations Navigate to API to create or manage your API credentials. For more details on available scopes, endpoint-specific parameters, and additional functionalities such as managing community content, users, and webhooks, please refer to the full Gainsight Customer Communities API Documentation Actions Actions Description Create company records Create a single or multiple company records in Gainsight NXT Create company team record Creates a company team record in Gainsight NXT Delete records Delete a specific record in the company object in Gainsight NXT Get team record details Retrieve the details of a team record in Gainsight NXT Search records Retrieve the details of records in Gainsight NXT Update company records Update company records in Gainsight NXT Update company team record Updates a company team record in Gainsight NXT Upsert person Upsert a single person in Gainsight NXT Upsert persons in bulk Upsert persons in bulk in Gainsight NXT

Screen by UnifyApps

Unify Automations

Airtable

Integrate your app with Airtable to organize data, automate workflows, and create custom databases tailored to your needs

Airtable is a flexible platform that combines the simplicity of a spreadsheet with the power of a database for easy data organization and collaboration. Integrating your application with Airtable empowers you to create custom databases, streamline data management, and collaborate seamlessly with your team. Authentication Ensure you have the following information ready for a seamless integration process: Connection Name : Select a descriptive name for your connection, like "MyAppAirtableIntegration". This helps in easily identifying the connection within your application or integration settings. Authentication Type : Airtable supports the following type of authentication for connecting to your Airtable account: API Token OAUTH 2.0 Access Token Based Authentication L ogin into Airtable account and click on the profile icon at the top right corner. Navigate to the builder hub In Personal Access token section, click on the “ Create new token ” button Provide the name and the required scopes for performing action based on your use case and click on “ Create Token ” Treat this token with high confidentiality, as it allows access to your Airtable account. OAUTH 2.0 Based Authentication L ogin into Airtable account and click on the profile icon at the top right corner. Navigate to the developer hub In Oauth Integrations section, click on the “ Register New OAuth integration ” button Provide the “ Name ” and the “ OAuth Redirect URL ” The OAuth Redirect URL is the destination to which users will be redirected after authorizing their integration. Then click on the “ Register integration ” button After registration fill out the details as mentioned, Note down the Client ID and also generate a client secret by clicking on the “ Generate client secret ” and save it to form a connection Then select the scopes you wish to expose through this connection Actions Actions Description Create comment Create a comment on a record in Airtable Create field Create field in Airtable Create record Creates record in Airtable Delete comment Delete a comment on a record in Airtable Delete multiple records Delete multiple records in Airtable Delete record Deletes record in Airtable Get record Gets record from Airtable List records List records in Airtable Search records Search for records in Airtable Update comment Update a comment on a record in Airtable Update field Update field in Airtable Update record Updates a record in Airtable Upsert record Upsert a record in Airtable Upsert records (Batch) Upsert records in Airtable Triggers Triggers Description New record This trigger will be invoked when a new record is created in Airtable New/Updated Record This trigger will be invoked when a record is created or updated in Airtable Record and cell value changes This trigger will be invoked when a record and cell value changes in Airtable Field change Triggers when a field changes in Airtable

Fuzzy Match Rules

Overview Within the UnifyApps Master Data Management (MDM) framework, Match Rules are the logic engines responsible for identifying duplicate records across your dataset. The Exact Match On criterion is the most deterministic and rigid matching strategy available. Unlike fuzzy matching algorithms that allow for slight variations (e.g., "Jon" vs. "John"), an "Exact Match On" rule requires the data in the selected field to be 100% identical—character for character—to be considered a match. Use Cases This rule type is best suited for high-confidence identifiers where no ambiguity is acceptable: Unique Identifiers: Matching on system-generated IDs like User_ID , Social_Security_Number , or ISBN . Digital Coordinates: Matching on fields like Email Address or Phone Number (normalized) where a single character difference implies a different entity. Codes: Matching on standardized business codes such as Store_ID or Cost_Center_Code . Configuration Guide Configuring an exact match rule involves defining the criteria in the Match Rule Definition panel. Navigate to Rule Definitions From the specific Entity's dashboard, select the Match Rules tab and click + New Match Rule. Enter a descriptive Rule Name (e.g., "Primary Key Exact Match") and Description to document the rule's intent. Set the Match Condition In the Match Rule Definition section, you will define the logic logic used to compare records: Where: Select Exact Match On from the primary condition dropdown. This instructs the system to look for strict equality. Select a Field: Choose the specific attribute you want to compare (e.g., Branch_Code or Primary_Key ). Advanced Combinations For more complex validation, you can layer multiple exact match conditions: Add Field: Clicking this allows you to create a compound key match (e.g., Match EXACTLY on First Name AND EXACTLY on Last Name ). Add Field Group: This enables more sophisticated logic groupings, effectively allowing for "OR" conditions within your match strategy. Define Merge Policy Once the system identifies records that satisfy the "Exact Match" criteria, you must define the action to take: Automatically Merge: The confidence level is high enough to merge records without human intervention. Flag for Review: The match is detected but requires a data steward to verify it in the "Potential Matches" queue.

Carousel