Skip to main content

Bluetally Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow or Spark ETL data flow that sends data to a Bluetally location.
bluetally_api.png

Bluetally

Create a Bluetally Destination​

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

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

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

    Bluetally destinations can also be configured manually, allowing you to send data to BlueTally 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 BlueTally endpoints. Each template is designed specifically for the corresponding BlueTally 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.

    Create Asset

    Creates a new asset record in BlueTally. Send a Nexset whose records contain the asset attributes (e.g., name, serial number, model, status, location) you want to track.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/assets with content type application/json.
    • Map your incoming data attributes to the field names expected by the BlueTally Create Asset API. Refer to the BlueTally API Reference for the complete schema.

    Update Asset

    Updates an existing asset by ID. Use this endpoint to push attribute changes (status, location, custom fields, etc.) from upstream systems into BlueTally.

    • Enter the unique identifier of the asset to update in the Asset ID field. This is typically mapped from an upstream Nexset attribute.
    • The Nexset record is sent as a JSON body to PUT /api/v1/assets/{id}.

    See the Update Asset reference for the list of updatable fields and any required attributes.

    Delete Asset

    Deletes or retires an asset by ID. The request body is empty—only the asset identifier is required.

    • Enter the unique identifier of the asset to delete in the Asset ID field.
    • The action is performed via DELETE /api/v1/assets/{id}.

    Deleting an asset in BlueTally is typically irreversible. Verify the source data before activating this destination.

    Create Employee

    Creates a new employee record in BlueTally. Use this endpoint to onboard employees from an HRIS or directory system.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/employees.

    Update Employee

    Updates an existing employee by ID. Use this endpoint to synchronize employee attribute changes from authoritative HR systems.

    • Enter the unique identifier of the employee in the Employee ID field.
    • The Nexset record is sent as a JSON body to PUT /api/v1/employees/{id}.

    Delete Employee

    Deletes/offboards an employee by ID. The request body is empty—only the employee identifier is required.

    • Enter the unique identifier of the employee in the Employee ID field.

    Create Accessory

    Creates a new accessory record in BlueTally (e.g., cables, chargers, peripherals).

    • The Nexset record is serialized as JSON and posted to POST /api/v1/accessories.

    Update Accessory

    Updates an existing accessory with new details and attributes.

    • Enter the accessory identifier in the Id field.
    • The Nexset record is sent as a JSON body to PUT /api/v1/accessories/{id}.

    Delete Accessory

    Deletes a specific accessory by ID. Supports an optional tenant ID for multi-tenant accounts.

    • Enter the accessory identifier in the Id field.
    • If your BlueTally account is multi-tenant, enter the tenant identifier in the Tenant Id field; otherwise leave this field blank.

    Create Component

    Creates a new component record in BlueTally. Components represent parts (e.g., RAM modules, drives) that can be checked out to assets.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/components.

    Create Accessory (alias) — Create License

    Creates a new software license record in BlueTally.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/licenses.

    Checkout Asset

    Checks out an asset to an employee or location. Use this endpoint to record asset assignments in BlueTally.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/asset. The body should reference the asset and the target employee or location per the BlueTally API specification.

    Checkin Asset

    Checks an asset back in from an employee or location, ending the current assignment.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkin/asset.

    Checkout Accessory

    Checks out an accessory to an employee.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/accessory.

    Checkin Accessory

    Checks an accessory back in from an employee.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkin/accessory.

    Checkout Component

    Checks out a component to an asset (e.g., installing a RAM module into a tracked device).

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/component.

    Checkout Consumable

    Checks out a consumable to an employee.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/consumable.

    Checkout License

    Checks out a license to an employee or asset.

    • The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/license.

    Refer to the BlueTally API Reference for the request body schema expected by each checkout/checkin endpoint.

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the BlueTally API after each call to a new Nexla webhook data source, which is useful for tracking newly assigned IDs after create operations.

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 BlueTally API from the Method pulldown menu. Use POST to create records or trigger checkout/checkin actions, PUT to update existing records, and DELETE to remove records.

Data Format​

  1. Select the format in which the Nexset data will be sent to the BlueTally API from the Content Format pulldown menu. The BlueTally API expects application/json, so JSON is the appropriate format for all BlueTally destinations.

API Endpoint URL​

  1. Enter the URL of the BlueTally API endpoint to which you want to send the Nexset data in the URL field. The base URL for the BlueTally API is https://app.bluetallyapp.com/api/v1. For update/upsert operations, include the ID of the object to be updated at the end of the URL (e.g., https://app.bluetallyapp.com/api/v1/assets/12345).

For multi-tenant accounts, append the tenant_id query parameter to the URL (e.g., {'https://app.bluetallyapp.com/api/v1/assets?tenant_id={tenant_id}'}).

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. Nexla automatically attaches the Bearer token from your selected credential, and the Content-Type header is set based on the data format selected above.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Bluetally 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.

Most BlueTally write endpoints (e.g., Create Asset, Update Asset) operate on a single record per request. Verify that the target endpoint supports batched payloads before enabling record batching.

Response Webhook​

Optional

Nexla can automatically send the response received from the BlueTally 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 capture newly created BlueTally IDs for downstream processing.

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

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