Pipeliner CRM is a sales customer relationship management platform that helps sales teams manage accounts, contacts, leads, opportunities, activities, and forecasts through a visual pipeline. Its REST API exposes these CRM entities so you can read and write records programmatically. This connector lets Nexla ingest data from Pipeliner as a source and send records back to Pipeliner as a destination.
Power end-to-end data operations for your Pipeliner API with Nexla. Our bi-directional Pipeliner connector is purpose-built for Pipeliner, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pipeliner or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pipeliner workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Pipeliner credential, you need an API token, API password, and the API base URL (service URL) for your Pipeliner team space. The Pipeliner REST API uses HTTP Basic authentication, with the API token as the username and the API password as the password. Each team space has its own API keys.
To obtain your Pipeliner API credentials, follow these steps:
Sign in to your Pipeliner CRM account with an administrator account.
Open your team space and access the space administration area.
Locate the API access settings for the space and select the option to obtain (generate) an API key. The API token becomes your username, and the API password becomes your password.
The API token and API password are generated only once and are not shown again after you leave the page. Copy and store both values securely before continuing. If they are lost or compromised, generate a new API key.
Note your space's Space ID and Service URL. Both are part of every API request. The base URL follows the pattern https://SERVICE_URL/api/v100/rest/spaces/SPACE_ID, where SERVICE_URL is the regional service host for your space and SPACE_ID identifies the space you are connecting to.
Store the API token, API password, and the assembled base URL. You will enter these when creating your Nexla credential.
For complete information about API authentication, request formats, and available entities, see the Pipeliner API Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Pipeliner API token in the Username field. This is the API token generated for your team space and is used as the username for HTTP Basic authentication.
Enter your Pipeliner API password in the Password field. This is the API password generated alongside the API token and is used as the password for HTTP Basic authentication. This value is stored securely and must be kept confidential.
Enter your Pipeliner API base URL in the Base URL field. This is the full base URL for your team space, in the form https://SERVICE_URL/api/v100/rest/spaces/SPACE_ID, combining your space's service URL and Space ID.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pipeliner connector tile, then select the credential that will be used to connect to the Pipeliner instance, and click Next; or, create a new Pipeliner credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pipeliner endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Accounts
This endpoint template retrieves accounts from your Pipeliner space. Use this template when you need to ingest company or organization records for analysis, reporting, or integration purposes.
This endpoint reads records from the Accounts entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Clients
This endpoint template retrieves clients from your Pipeliner space. Use this template when you need to ingest client records for analysis, reporting, or integration purposes.
This endpoint reads records from the Clients entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Contacts
This endpoint template retrieves contacts from your Pipeliner space. Use this template when you need to ingest individual contact records for analysis, reporting, or integration purposes.
This endpoint reads records from the Contacts entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Profiles
This endpoint template retrieves profiles from your Pipeliner space. Use this template when you need to ingest profile records for analysis, reporting, or integration purposes.
This endpoint reads records from the Profiles entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Activities
This endpoint template retrieves activities from your Pipeliner space. Use this template when you need to ingest task, call, or appointment records for analysis, reporting, or integration purposes.
This endpoint reads records from the Activities entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Entities
This endpoint template retrieves entities from your Pipeliner space. Use this template when you need to ingest entity records for analysis, reporting, or integration purposes.
This endpoint reads records from the Entities entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Data
This endpoint template retrieves data records from your Pipeliner space. Use this template when you need to ingest data records for analysis, reporting, or integration purposes.
This endpoint reads records from the Data entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Cloud Objects
This endpoint template retrieves cloud objects from your Pipeliner space. Use this template when you need to ingest cloud object records for analysis, reporting, or integration purposes.
This endpoint reads records from the CloudObjects entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Fields
This endpoint template retrieves field definitions from your Pipeliner space. Use this template when you need to ingest field metadata for analysis, reporting, or integration purposes.
This endpoint reads records from the Fields entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Forecasts
This endpoint template retrieves forecasts from your Pipeliner space. Use this template when you need to ingest forecast records for analysis, reporting, or integration purposes.
This endpoint reads records from the Forecasts entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Form Views
This endpoint template retrieves form views from your Pipeliner space. Use this template when you need to ingest form view records for analysis, reporting, or integration purposes.
This endpoint reads records from the FormViews entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Entity Scorings
This endpoint template retrieves entity scorings from your Pipeliner space. Use this template when you need to ingest scoring records for analysis, reporting, or integration purposes.
This endpoint reads records from the EntityScorings entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Leads
This endpoint template retrieves leads from your Pipeliner space. Use this template when you need to ingest lead records for analysis, reporting, or integration purposes.
This endpoint reads records from the Leads entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Lead Oppties
This endpoint template retrieves lead opportunities from your Pipeliner space. Use this template when you need to ingest lead opportunity records for analysis, reporting, or integration purposes.
This endpoint reads records from the LeadOppties entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Memos
This endpoint template retrieves memos from your Pipeliner space. Use this template when you need to ingest memo records for analysis, reporting, or integration purposes.
This endpoint reads records from the Memos entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Notes
This endpoint template retrieves notes from your Pipeliner space. Use this template when you need to ingest note records for analysis, reporting, or integration purposes.
This endpoint reads records from the Notes entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Entity Fitnesses
This endpoint template retrieves entity fitnesses from your Pipeliner space. Use this template when you need to ingest entity fitness records for analysis, reporting, or integration purposes.
This endpoint reads records from the EntityFitnesses entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Pipelines
This endpoint template retrieves pipelines from your Pipeliner space. Use this template when you need to ingest pipeline records for analysis, reporting, or integration purposes.
This endpoint reads records from the Pipelines entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Products
This endpoint template retrieves products from your Pipeliner space. Use this template when you need to ingest product records for analysis, reporting, or integration purposes.
This endpoint reads records from the Products entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
[Rest API] List Oppty Product Relations
This endpoint template retrieves opportunity-product relations from your Pipeliner space. Use this template when you need to ingest the records that associate opportunities with products for analysis, reporting, or integration purposes.
This endpoint reads records from the OpptyProductRelations entity and returns paginated results, which Nexla automatically iterates through to fetch all available data.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Pipeliner data sources can also be manually configured to ingest data from any valid Pipeliner API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pipeliner data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Pipeliner destination, and select the Send to Destination option from the menu. Select the Pipeliner connector from the list of available destination connectors, then select the credential that will be used to connect to the Pipeliner space, and click Next; or, create a new Pipeliner credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Pipeliner endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create or Update Accounts
This endpoint template bulk creates or updates Account records in your Pipeliner space using records from a Nexset. Include an 'id' in each object to update an existing record; omit the 'id' to create a new record.
This endpoint sends records as JSON to the Accounts batch-modify endpoint. Ensure each record matches the field structure expected by the Pipeliner Accounts entity.
[Rest API] Create or Update Contacts
This endpoint template bulk creates or updates Contact records in your Pipeliner space using records from a Nexset. Include an 'id' in each object to update an existing record; omit the 'id' to create a new record.
This endpoint sends records as JSON to the Contacts batch-modify endpoint. Ensure each record matches the field structure expected by the Pipeliner Contacts entity.
[Rest API] Create or Update Leads
This endpoint template bulk creates or updates Lead records in your Pipeliner space using records from a Nexset. Include an 'id' in each object to update an existing record; omit the 'id' to create a new record.
This endpoint sends records as JSON to the Leads batch-modify endpoint. Ensure each record matches the field structure expected by the Pipeliner Leads entity.
[Rest API] Create or Update Activities
This endpoint template bulk creates or updates Activity records in your Pipeliner space using records from a Nexset. Include an 'id' in each object to update an existing record; omit the 'id' to create a new record.
This endpoint sends records as JSON to the Activities batch-modify endpoint. Ensure each record matches the field structure expected by the Pipeliner Activities entity.
[Rest API] Delete Accounts
This endpoint template bulk deletes Account records in your Pipeliner space by ID using records from a Nexset. Use this template when you need to remove account records that are no longer needed.
This endpoint sends account IDs as JSON to the Accounts batch-delete endpoint. Deletion is permanent, so verify the records before activating this destination.
Pipeliner destinations can also be manually configured to send data to any valid Pipeliner API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Pipeliner APIs expect JSON format for create, update, and delete operations. For bulk create or update endpoints, include the id of each record to update an existing object, or omit it to create a new one.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Pipeliner endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Pipeliner endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
