OnePageCRM

OnePageCRM is an action-focused sales CRM that helps small businesses and sales teams manage contacts, companies, deals, actions, and notes with a next-action workflow. The Nexla connector uses the OnePageCRM REST API (v3) to read CRM records into your data flows and to create or update records from your Nexsets.

Power end-to-end data operations for your OnePageCRM API with Nexla. Our bi-directional OnePageCRM connector is purpose-built for OnePageCRM, 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 OnePageCRM or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your OnePageCRM 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

Prerequisites

Before creating a OnePageCRM credential, you need the user ID and API key associated with your OnePageCRM account. The OnePageCRM API uses HTTP Basic Authentication, where your username is your user_id and your password is your api_key.

To obtain your OnePageCRM API credentials, follow these steps:

1. Sign in to your OnePageCRM account at https://app.onepagecrm.com using your account credentials.

2. Navigate to the API settings page at https://app.onepagecrm.com/app/api.

3. Open the Configuration tab to view the user ID and API key associated with your account.

4. Copy your user ID and API key. You will enter the user ID (or username) in the credential's username field and the API key in the password field when configuring your Nexla credential.

HTTP Basic Authentication with the user_id and api_key is the recommended authentication method for new integrations. Treat the API key as a secret and keep it confidential.

For detailed information about authentication, resources, and available endpoints, see the OnePageCRM API Documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Username Or API Key	Yes	No	Your username or personal API Key
Password	Yes	Yes	Your password

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your OnePageCRM user ID (or username) in the Username Or API Key field. This is the user_id found on the OnePageCRM API settings page that you obtained in Prerequisites.

4. Enter your OnePageCRM API key in the Password field. This is the api_key found on the OnePageCRM API settings page and is sent as the password for HTTP Basic Authentication.

   The API key provides access to your OnePageCRM account data and should be treated as sensitive information. If your API key is compromised, revoke or regenerate it from the OnePageCRM API settings page.

   For detailed information about authentication and available endpoints, see the OnePageCRM API Documentation.

5. 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.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the OnePageCRM connector tile, then select the credential that will be used to connect to OnePageCRM, and click Next; or, create a new OnePageCRM credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common OnePageCRM 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] Get a list of contacts

Get a list of contacts. Defaults to contacts owned by the logged user, alpha sorted.

This endpoint template retrieves contact records from your OnePageCRM account. Optional query parameters, such as search, team, owner, tag, and date filters, can be used to narrow the results returned. For detailed information about the available query parameters and response fields, see the OnePageCRM Contacts API Documentation.

[Rest API] Get a specific contact

Get a specific contact by ID.

This endpoint template retrieves a single contact record identified by its contact ID. Provide the ID of the contact you want to fetch in the endpoint's Contact Id parameter. For detailed information about response fields, see the OnePageCRM Contacts API Documentation.

[Rest API] Get a list of deals

Get a list of deals.

This endpoint template retrieves deal records from your OnePageCRM account. For detailed information about the available query parameters and response fields, see the OnePageCRM Deals API Documentation.

[Rest API] Get a specific deal

Get a specific deal by ID.

This endpoint template retrieves a single deal record identified by its deal ID. Provide the ID of the deal you want to fetch in the endpoint's Deal Id parameter. For detailed information about response fields, see the OnePageCRM Deals API Documentation.

[Rest API] Get a list of companies

Get a list of companies. Default sort order is company name, alphabetical.

This endpoint template retrieves company records from your OnePageCRM account. For detailed information about the available query parameters and response fields, see the OnePageCRM Companies API Documentation.

[Rest API] Get a specific company

Get a specific company by ID.

This endpoint template retrieves a single company record identified by its company ID. Provide the ID of the company you want to fetch in the endpoint's Company Id parameter. For detailed information about response fields, see the OnePageCRM Companies API Documentation.

[Rest API] Get a list of actions

Get a list of actions (tasks). Default sort order: ASAP first, then dated actions ordered by due date (overdue first), then waiting-for (blocked), then queued actions, then completed actions.

This endpoint template retrieves action (task) records from your OnePageCRM account. For detailed information about the available query parameters and response fields, see the OnePageCRM Actions API Documentation.

[Rest API] Get a specific action

Get a specific action by ID.

This endpoint template retrieves a single action (task) record identified by its action ID. Provide the ID of the action you want to fetch in the endpoint's Action Id parameter. For detailed information about response fields, see the OnePageCRM Actions API Documentation.

[Rest API] Get a list of notes

Get a list of notes.

This endpoint template retrieves note records from your OnePageCRM account. For detailed information about the available query parameters and response fields, see the OnePageCRM Notes API Documentation.

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.

Manual configuration

OnePageCRM data sources can also be manually configured to ingest data from any valid OnePageCRM 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 OnePageCRM 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the OnePageCRM destination, and select the Send to Destination option from the menu. Select the OnePageCRM connector from the list of available destination connectors, then select the credential that will be used to connect to OnePageCRM, and click Next; or, create a new OnePageCRM credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common OnePageCRM 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 a contact

Create a new contact.

This endpoint template creates a new contact in your OnePageCRM account using records from a Nexset. Each record is sent as a JSON request body. Ensure your record fields match the format expected by the OnePageCRM API. For detailed information about the request body and available fields, see the OnePageCRM Contacts API Documentation.

[Rest API] Update a specific contact

Update a specific contact. When updating a custom field, either the id or name and the value must be present.

This endpoint template updates an existing contact identified by its contact ID using records from a Nexset. When updating a custom field, either the id or the name and the value must be present. For detailed information about the request body and available fields, see the OnePageCRM Contacts API Documentation.

[Rest API] Delete a specific contact

Delete a specific contact. Only users with the delete_contacts permission can delete contacts.

This endpoint template deletes an existing contact identified by its contact ID. Only users with the delete_contacts permission can delete contacts. For detailed information, see the OnePageCRM Contacts API Documentation.

[Rest API] Create a new deal

Create a new deal.

This endpoint template creates a new deal in your OnePageCRM account using records from a Nexset. Each record is sent as a JSON request body. For detailed information about the request body and available fields, see the OnePageCRM Deals API Documentation.

[Rest API] Update a specific deal

Update a specific deal.

This endpoint template updates an existing deal identified by its deal ID using records from a Nexset. For detailed information about the request body and available fields, see the OnePageCRM Deals API Documentation.

[Rest API] Update a specific company

Update a specific company. When updating a company field, either the id or name and the value must be present.

This endpoint template updates an existing company identified by its company ID using records from a Nexset. When updating a company field, either the id or the name and the value must be present. For detailed information about the request body and available fields, see the OnePageCRM Companies API Documentation.

[Rest API] Create a new action

Create a new action (task).

This endpoint template creates a new action (task) in your OnePageCRM account using records from a Nexset. Each record is sent as a JSON request body. For detailed information about the request body and available fields, see the OnePageCRM Actions API Documentation.

[Rest API] Update a specific action

Update a specific action (task).

This endpoint template updates an existing action (task) identified by its action ID using records from a Nexset. For detailed information about the request body and available fields, see the OnePageCRM Actions API Documentation.

[Rest API] Create a new note

Create a new note.

This endpoint template creates a new note in your OnePageCRM account using records from a Nexset. Each record is sent as a JSON request body. For detailed information about the request body and available fields, see the OnePageCRM Notes API Documentation.

Manual configuration

OnePageCRM destinations can also be manually configured to send data to any valid OnePageCRM 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.

OnePageCRM APIs expect JSON format for create and update operations. For update operations, include the ID of the object to be updated at the end of the URL.

Save & activate

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 OnePageCRM endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the OnePageCRM endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.