Pipeliner

Learn how to use Pipeliner Connector in DBSync Cloud Workflow

Overview

The Pipeliner connector in DBSync Cloud Workflow enables seamless integration between DBSync and Pipeliner CRM. It allows data synchronization between Pipeliner CRM and various applications, improving data consistency and operational efficiency. This article provides a step-by-step guide on how to configure and use the Pipeliner connector within DBSync.

Pre-requisites

Before using the Pipeliner connector in DBSync, ensure that:

  1. You have an active DBSync Cloud Workflow account.

  2. You have valid credentials and API access for your Pipeliner CRM account.

  3. The required modules (like accounts, contacts, opportunities, etc.) are set up in Pipeliner CRM.

Key Features

  • Data Synchronization: Synchronize accounts, contacts, opportunities, and other data entities between DBSync and Pipeliner CRM.

  • Automation: Schedule and automate workflows for continuous data updates.

  • Customization: Configure mappings and transformation rules based on business needs.

Setup Guide

Connecting Pipeliner CRM to DBSync

  1. Log into DBSync: Open your DBSync Cloud Workflow account.

  2. Navigate to Connectors: From the main menu, go to Apps and select Add Connector.

  3. Select Pipeliner Connector: Choose Pipeliner from the list of available connectors and click Add.

  4. Enter Pipeliner Credentials: Provide your Pipeliner API URL, username, and API token. These credentials are required to establish a secure connection.

  5. Test Connection: Once credentials are entered, click Test Connection to verify connectivity.

Configuring Connector Settings

  • Data Entities: Select the data entities you wish to sync, such as Accounts, Contacts, Leads, or Opportunities.

  • Frequency: Set the sync frequency (e.g., daily, hourly) or use real-time sync if available.

  • Data Mapping: Map fields between Pipeliner CRM and the connected application. Use DBSync’s drag-and-drop interface to match fields.

  • Transformation Rules: Add any transformation rules to ensure data format consistency across systems.

Mapping Fields

  1. Go to the Field Mapping section and review the default mappings.

  2. If customization is needed, drag and drop fields from the source (Pipeliner CRM) to the target application.

  3. Use advanced options like calculated fields or condition-based mapping if specific transformation logic is required.

Setting Up Workflows

  • Create a New Workflow: Go to Workflows and click Create New Workflow.

  • Define Trigger Events: Choose events in Pipeliner that will trigger data synchronization (e.g., new contact creation, opportunity update).

  • Select Action Steps: Define the actions that DBSync should perform when the trigger event occurs. You can specify operations like Insert, Update, or Delete on target systems.

  • Test Workflow: Run a test to verify that the data flows correctly between Pipeliner CRM and the connected application.

Advanced Options

  • Data Filtering Use data filtering to sync only specific records based on conditions (e.g., sync opportunities with a status of "Closed").

  • Error Handling and Logging

    • Enable logging to capture all data sync activities for troubleshooting.

    • Configure error-handling settings to manage failed syncs (e.g., retry on failure, email notifications).

Scheduling Sync Jobs

Go to Scheduling under the Workflow settings to set specific times for data sync operations.

Troubleshooting

  1. Connection Errors: Check API credentials and verify that they haven’t expired.

  2. Field Mapping Issues: Ensure that all mandatory fields in Pipeliner and the connected app are mapped.

  3. Data Transformation Errors: Review transformation rules for accuracy, especially for calculated fields and condition-based mappings.

Best Practices

  • Test Before Production: Run workflows in a sandbox environment before pushing them live.

  • Regularly Update API Credentials: For security and continuity, update Pipeliner API tokens regularly.

  • Monitor Sync Logs: Regularly review logs for any sync errors and update configurations as needed.

Last updated