Consensus Demo Automation Platform

Consensus is a video demo automation platform for interactive product demos, DemoBoards, and buyer engagement analytics. This connector reads demo, viewer, lead, and demolytics reporting data from Consensus and writes leads, sent demos, marketing links, webhooks, and CRM opportunity updates back to your Consensus account through its REST API.

Power end-to-end data operations for your Consensus Demo Automation Platform API with Nexla. Our bi-directional Consensus Demo Automation Platform connector is purpose-built for Consensus Demo Automation Platform, 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 Consensus Demo Automation Platform or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Consensus Demo Automation Platform 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 Consensus credential, you need an API Key and API Secret generated from your Consensus account, along with the email address of the Consensus user the integration acts on behalf of. Consensus authenticates each request with an auth object sent in the JSON request body, containing the API key, API secret, the requester's user email, and a source name that identifies your integration.

To obtain your Consensus API credentials, follow these steps:

1. Sign in to the Consensus web app at app.goconsensus.com with an account that has permission to manage integrations.

2. Click Integrations in the Consensus web app, then open the API Credentials tab.

3. If you have not generated credentials yet, click Regenerate (also labeled Generate) to create your API Key and API Secret. The same button refreshes existing credentials.

4. Copy the API Key and API Secret and store them securely. Treat them as sensitive information and share them only with trusted integrations.

5. Note the email address of the Consensus user on whose behalf API requests will be made, and decide on a Source Name to identify this Nexla integration in Consensus.

Regenerating credentials invalidates the previous API Key and API Secret. If you already use these credentials for another integration, regenerating them will break that integration. For request and response details, see the Consensus API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key generated under Integrations > API Credentials in the Consensus web app.
API Secret	Yes	Yes	API secret generated alongside the API key under Integrations > API Credentials.
User Email	Yes	No	Email address of the Consensus user on whose behalf API requests are made.
Source Name	Yes	No	Name identifying this integration/source system to Consensus, sent with each request's auth object.

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 API Key and API Secret in the corresponding fields. These are generated under Integrations > API Credentials in the Consensus web app and are sent in the auth object of every API request.

4. Enter the User Email of the Consensus user the integration acts on behalf of, and a Source Name that identifies this Nexla integration to Consensus.

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 Consensus Demo Automation Platform connector tile, then select the credential that will be used to connect to Consensus, and click Next; or, create a new Consensus 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 Consensus 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] Users

Retrieves Consensus user account metadata: name, email, role, group, status, and last-activity timestamp for each user in the account.

[Rest API] Demos

Retrieves metadata for demos created in the account, including title, type, visibility, creator, main video, features, and sub-demos.

[Rest API] Sales By Customer (Demolytics)

Retrieves detailed sales/demolytics reporting data broken out by customer, used to measure demo engagement against sales activity.

[Rest API] DemoBoards

Retrieves DemoBoard report data, tracking curated collections of demo content shared with prospects, including viewer activity.

[Rest API] Demo Search

Searches sent/created demos and returns per-demo metadata including owner, folder, permissions, and included tours.

[Rest API] Get Demo By Link Hash

Retrieves a single demo's details by its public share link hash. Provide the Link Hash parameter from a Consensus share URL when configuring this endpoint.

[Rest API] User Info

Fetches account/profile information for the authenticated (or specified) Consensus user.

[Rest API] Search Leads

Searches marketing lead/contact records captured through Consensus demo engagement.

[Rest API] Sales Search

Searches sales activity records (sent demos) associated with the account.

[Rest API] List Webhooks

Lists webhook subscriptions configured for the account.

[Rest API] Get Recipient

Returns leads (recipients) matching a given email address, for the current organization. Provide the Email parameter for the lead to look up when configuring this endpoint.

[Rest API] Get Mail Merge

Retrieves a single mail-merge template's configuration by ID. Provide the Mail Merge UUID of the mail-merge link to retrieve when configuring this endpoint.

[Rest API] List Mail Merges

Lists mail-merge templates configured for the account.

[Rest API] List Mail Merge Platforms

Lists mail-merge/CRM platforms supported for integration links.

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

Consensus data sources can also be manually configured to ingest data from any valid Consensus 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 Consensus 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 Consensus destination, and select the Send to Destination option from the menu. Select the Consensus Demo Automation Platform connector from the list of available destination connectors, then select the credential that will be used to connect to Consensus, and click Next; or, create a new Consensus 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 Consensus 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] Update CRM Opportunity Data

Updates CRM sync opportunity data associated with a demo/send, used to keep CRM opportunity fields aligned with Consensus activity.

[Rest API] Create Lead

Creates a new marketing lead/contact record in Consensus.

[Rest API] Create Marketing Link

Creates a public marketing demo link.

[Rest API] Create Send Demo

Creates (sends) a new demo to a prospect/recipient.

[Rest API] Update Send Demo

Updates an existing sent-demo record.

[Rest API] Create Webhook

Creates a new webhook subscription for the account.

[Rest API] Delete Webhook

Deletes an existing webhook subscription.

[Rest API] Delete Recipient

Anonymizes a lead's info (email, name, title) by email address, for the current organization. This is an asynchronous background operation, and requires the Email parameter identifying the lead to anonymize.

[Rest API] Create Mail Merge

Creates a new mail-merge template.

[Rest API] Update Mail Merge

Updates an existing mail-merge template.

Manual configuration

Consensus destinations can also be manually configured to send data to any valid Consensus 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 Consensus endpoint, open the destination resource menu, and select Activate.

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