Skip to main content

BoostUp Data Source

The BoostUp connector enables you to ingest sales intelligence data including opportunities, accounts, and AI-generated forecast data from your BoostUp revenue command center. Follow the instructions below to create a new data flow that ingests data from a BoostUp source in Nexla.
boostup_api.png

BoostUp

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the BoostUp connector tile from the list of available connectors. Then, select the credential that will be used to connect to the BoostUp instance, and click Next; or, create a new BoostUp credential for use in this flow.

  3. In Nexla, BoostUp data sources can be created using pre-built endpoint templates, which expedite source setup for common BoostUp endpoints. Each template is designed specifically for the corresponding BoostUp endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    BoostUp sources can also be configured manually, allowing you to ingest data from BoostUp endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common BoostUp endpoints. Each template is designed specifically for the corresponding BoostUp endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Get Opportunities

    Retrieves sales opportunities and pipeline data from your BoostUp account. Use this endpoint to pull opportunity records into Nexla for analysis, reporting, or integration with downstream systems such as data warehouses or BI tools. This is one of the most commonly used BoostUp endpoints for revenue operations workflows.

    • This endpoint retrieves all opportunity records accessible to the authenticated user, including deal stage, close date, amount, owner, and AI-scored risk signals generated by BoostUp's machine learning models.
    • Results are paginated automatically. Nexla will retrieve all available pages of opportunity data in sequence.
    • No additional configuration parameters are required beyond selecting this template. The endpoint uses your credential's Base URL and API Key to authenticate and retrieve data.

    BoostUp enriches opportunity records with AI-generated attributes such as deal risk scores and forecast categories. These enriched fields are included in the response and will be available as attributes in the generated Nexset.

    Get Accounts

    Retrieves account records and associated revenue data from BoostUp. Use this endpoint when you need to analyze account-level revenue intelligence, engagement signals, or customer health data for pipeline reporting or customer success workflows.

    • This endpoint returns all account records in your BoostUp organization, including account name, CRM identifiers, engagement score, and any revenue or health signals tracked by BoostUp.
    • Results are paginated automatically. Nexla will retrieve all available pages of account data in sequence.
    • No additional configuration parameters are required beyond selecting this template.

    Account records in BoostUp are synchronized from your connected CRM (such as Salesforce or HubSpot) and enriched with BoostUp's engagement and activity intelligence. The data returned reflects the current state of accounts as tracked in BoostUp.

    Get Forecasts

    Retrieves AI-powered sales forecast data and predictions from BoostUp. Use this endpoint to pull forecast snapshots into Nexla for trend analysis, forecast accuracy tracking, or integration with financial planning and reporting systems.

    • This endpoint returns current forecast data generated by BoostUp's machine learning models, including AI-predicted pipeline amounts, commit categories, best-case figures, and historical forecast snapshots by time period and team hierarchy.
    • This endpoint returns a single response without pagination, as forecast data is returned as a structured summary rather than a large record set.
    • No additional configuration parameters are required beyond selecting this template.

    BoostUp forecast data reflects AI-generated predictions based on CRM data, engagement signals, and historical win/loss patterns. The forecast values returned by this endpoint may differ from manually submitted rep forecasts — both are typically available in the BoostUp platform.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

BoostUp data sources can be manually configured to ingest data from any valid BoostUp API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex BoostUp sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the BoostUp API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

API Endpoint URL​

  1. Enter the URL of the BoostUp API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters.

    The BoostUp API base URL is https://app.boostup.ai/api. Append the specific endpoint path to this base URL. For example, to retrieve opportunities, the full URL would be https://app.boostup.ai/api/opportunities.

The full BoostUp OpenAPI specification, including all available endpoints and their parameters, is available at app.boostup.ai/export/docs/. Refer to the specification to identify the correct endpoint paths and any required query parameters for your use case.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Macros are particularly useful for BoostUp endpoints that support date-range filtering, such as retrieving opportunities or activities modified within a specific time window. Using macros allows Nexla to automatically adjust the time range on each data ingestion run.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to create BoostUp API endpoints that reference specific account IDs, opportunity IDs, or other identifiers retrieved from a prior data source in your Nexla environment.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch a list of opportunities, the BoostUp API will typically return an array of records along with metadata in a data wrapper. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when BoostUp API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records. For most BoostUp list endpoints, the data array is available at $.data[*].

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data.items[*] to access an array of items within a data object).

    • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/data/item to access item elements within a data element).

    Path to Data Example:

    If the BoostUp API response is in JSON format and includes a top-level array named data that contains the relevant records, the path to the response data would be entered as $.data[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For example, when a request call is used to fetch a list of BoostUp opportunities, the API response will typically include an array of records along with metadata such as total count or pagination details. If you have specified the path to the relevant data but metadata of interest is located in a different part of the response, you can specify a path to this metadata to include it with each record in the generated Nexset(s).

Metadata paths are particularly useful for preserving BoostUp response context like request IDs, timestamps, or summary statistics that apply to all records in the response.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata, and for responses in XML format, enter the XPath.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include the Authorization header here — it is automatically handled by your BoostUp credential configuration. Common headers like Authorization, Content-Type, and Accept are typically managed automatically by Nexla based on your credential.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new BoostUp 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.