SignNow
SignNow is an e-signature platform for sending, signing, and managing legally binding documents. This connector uses the SignNow REST API to read documents, users, and document history, and to write document, user, and signing-invite operations. It authenticates with SignNow's OAuth2 password grant flow using your application's client credentials and your account username and password.

Power end-to-end data operations for your SignNow API with Nexla. Our bi-directional SignNow connector is purpose-built for SignNow, 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 SignNow or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your SignNow workflows fast, secure, and fully governed.
Features
Type: API
- 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 SignNow credential, you need a SignNow account and an API application that provides a Client ID and Client Secret. SignNow authorizes API requests using the OAuth 2.0 protocol; Nexla uses the password grant flow, which combines your application's client credentials (sent as Basic authentication) with your SignNow account email and password.
To obtain your SignNow API credentials, follow these steps:
-
Sign in to the SignNow API dashboard with your SignNow account.
-
Create (or select) an application. SignNow generates a Client ID and Client Secret for the application in the dashboard's Keys section.
-
Copy the Client ID and Client Secret and store them securely. These identify your application when requesting an OAuth 2.0 access token.
-
Have your SignNow account email and password ready. Under the password grant flow, these authenticate the account whose documents and users the connector will access.
The client credentials are used as Basic authentication only when requesting an access token from SignNow's /oauth2/token endpoint; the resulting bearer access token authorizes all other API requests. For details on registering an application, authentication, and available endpoints, see the SignNow API documentation.
Authenticate
Credentials required
Authenticate to SignNow using client credentials (Basic auth) plus your account username and password, per SignNow's OAuth2 password grant flow.
| Field | Required | Secret | Description |
|---|---|---|---|
| Client ID | Yes | No | Your SignNow app's Client ID |
| Client Secret | Yes | Yes | Your SignNow app's Client Secret |
| Username (Email) | Yes | No | Your SignNow account email |
| Password | Yes | Yes | Your SignNow account password |
Create a credential in Nexla
-
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 SignNow app's Client ID and Client Secret, and your SignNow account Username (Email) and Password, in the corresponding fields. These values were obtained in Prerequisites.
-
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.
The Client Secret and Password are sensitive values and are stored securely by Nexla. If either is compromised, rotate the credentials in your SignNow account and update the Nexla credential.
For detailed information about SignNow authentication and available endpoints, see the SignNow API documentation.
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 SignNow connector tile, then select the credential that will be used to connect to SignNow, and click Next; or, create a new SignNow 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 SignNow 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.
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
SignNow data sources can also be manually configured to ingest data from any valid SignNow 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 SignNow 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 SignNow destination, and select the Send to Destination option from the menu. Select the SignNow connector from the list of available destination connectors, then select the credential that will be used to connect to SignNow, and click Next; or, create a new SignNow 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 SignNow 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.
Manual configuration
SignNow destinations can also be manually configured to send data to any valid SignNow 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.
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 SignNow endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the SignNow endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.