Skip to main content

BoostUp Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a BoostUp location.
boostup_api.png

BoostUp

Create a BoostUp Destination​

  1. Click the + icon on the Nexset that will be sent to the BoostUp destination, and select the Send to Destination option from the menu.

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

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

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

Configure Using a Template​

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

  • To configure this destination using a template, 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.

    Update Opportunity

    Sends opportunity data to BoostUp to create or update opportunity records. Use this endpoint when you need to push CRM opportunity data or enriched deal information from another system into BoostUp, keeping revenue intelligence data current and accurate.

    • This endpoint accepts opportunity data in JSON format. The Nexset data will be serialized as a JSON payload and sent to the BoostUp opportunities endpoint using a POST request.
    • Ensure that the Nexset contains the required opportunity fields expected by BoostUp, such as opportunity identifiers and any relevant CRM field mappings. Refer to the BoostUp OpenAPI specification at app.boostup.ai/export/docs/ for the full list of accepted fields and required parameters.
    • No additional template-level configuration is required. The endpoint uses your credential's Base URL and API Key for authentication.

    BoostUp processes incoming opportunity data and reconciles it with existing CRM records based on the opportunity identifiers provided. Ensure that the data you send includes valid identifiers that match your BoostUp data model to avoid creating duplicate records.

Configure Manually​

BoostUp destinations can be manually configured to send data to any valid BoostUp API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the BoostUp API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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. For most BoostUp write operations, use:

    • POST: For creating new records or submitting data
    • PUT: For replacing existing records in full
    • PATCH: For partially updating existing records

Data Format​

  1. Select the format in which the Nexset data will be sent to the BoostUp API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The BoostUp API accepts JSON-formatted request bodies for write operations.

API Endpoint URL​

  1. Enter the URL of the BoostUp API endpoint to which you want to send the Nexset data in the 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 update operations that target a specific record, include the record identifier at the end of the URL (for example, https://app.boostup.ai/api/opportunities/{'{opportunity_id}'}).

Refer to the BoostUp OpenAPI specification at app.boostup.ai/export/docs/ for the complete list of available endpoints, accepted request body schemas, and required path or query parameters for each operation.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization header here — it is automatically managed by your BoostUp credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this BoostUp destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the BoostUp API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the BoostUp API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the BoostUp API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the BoostUp API using the current settings.

Save & Activate the Destination​

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

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