Skip to main content

Leapsome 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 Leapsome location.
leapsome_api.png

Leapsome

Create a Leapsome Destination​

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

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

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

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

    Writes the current progress value to a Leapsome goal from an external system. This is the primary automation use case for Leapsome's API — it allows CRM metrics, project tracking tools, or any external data source to automatically push progress updates to Leapsome goals without manual entry.

    • Enter the Leapsome goal ID in the Goal ID field. This field is required. The goal ID identifies which goal in Leapsome will receive the progress update.

      • Goal IDs can be obtained by first reading data from Leapsome using the List Goals source endpoint and extracting the id field from the returned records.

    • The request body sent to Leapsome must include a currentValue field containing the numeric progress value. Ensure that the Nexset field carrying the progress value is mapped to currentValue in the data transformation step before this destination.

    This endpoint sends a POST request to https://api.leapsome.com/v1/goals/{goalId}/progress. The Leapsome API will update the goal's current progress value and recalculate its status (On Track, At Risk, or Off Track) based on the new value relative to the target.

    Update Key Result Progress

    Writes the current progress value to a specific key result within a Leapsome goal. This enables CRM-to-OKR pipeline automation at the key result (KR) level, allowing individual key results to be automatically updated from external metric sources such as Salesforce, Jira, or a data warehouse.

    • Enter the parent goal's Leapsome ID in the Goal ID field. This field is required and identifies the goal that contains the key result to be updated.

      • Goal IDs can be obtained from the List Goals source endpoint.

    • Enter the Leapsome key result ID in the Key Result ID field. This field is required and identifies the specific key result to update within the parent goal.

      • Key result IDs can be obtained from the List Key Results source endpoint by specifying the parent goal ID.

    • The request body sent to Leapsome must include a currentValue field containing the numeric progress value. Ensure that the Nexset field carrying the updated metric is mapped to currentValue in the data transformation step before this destination.

    This endpoint sends a POST request to https://api.leapsome.com/v1/goals/{goalId}/key-results/{krId}/progress. Updating a key result's progress also affects the parent goal's overall progress, as Leapsome recalculates goal progress based on the weighted contribution of its key results.

    Create Instant Feedback

    Pushes feedback events from external tools — such as Slack, Microsoft Teams, Jira, or a custom recognition tool — directly into the Leapsome continuous feedback stream. This allows organizations to centralize all employee feedback in Leapsome regardless of where it originates.

    • This endpoint does not require any URL path parameters. Nexla sends the entire Nexset record as a JSON body to the Leapsome instant feedback endpoint.

    • Ensure that the Nexset fields are mapped to the appropriate Leapsome feedback payload fields before this destination. Consult the Leapsome API documentation for the full list of required and optional body fields for the instant feedback creation endpoint.

    Feedback submitted via the API appears in the Leapsome platform in the same way as feedback submitted manually through the UI. Recipients receive notifications through their configured Leapsome notification settings.

    Create Meeting Action Item

    Writes action items from external meeting tools — such as Zoom, Google Meet, or Notion — back into a Leapsome 1-on-1 meeting record. This keeps meeting follow-up actions synchronized between Leapsome and the tools your teams use to run meetings.

    • Enter the Leapsome meeting ID in the Meeting ID field. This field is required and identifies which 1-on-1 meeting record will receive the new action item.

      • Meeting IDs can be obtained from the List Meetings source endpoint.

    • Nexla sends the Nexset record as a JSON body to the Leapsome meeting action items endpoint. Ensure that Nexset fields are mapped to the appropriate Leapsome action item payload fields. Consult the Leapsome API documentation for required body fields.

    Action items created via the API appear in the Leapsome meeting record and are visible to all meeting participants. They can be tracked and marked as complete within Leapsome.

Configure Manually​

Leapsome destinations can be manually configured to send data to any valid Leapsome API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the Leapsome 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 Leapsome API from the Method pulldown menu. Common methods for Leapsome write operations include:

    • POST: For creating new records or writing progress updates to goals, key results, feedback, and meeting action items.
    • PUT: For fully replacing an existing resource.
    • PATCH: For partial updates to an existing resource.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Leapsome API from the Content Format pulldown menu. Leapsome's API accepts JSON for all write operations. Nexla will automatically convert the data to JSON format for each API call.

API Endpoint URL​

  1. Enter the URL of the Leapsome API endpoint to which you want to send the Nexset data in the URL field. All Leapsome Content API endpoints begin with https://api.leapsome.com/v1/. For write operations that target a specific resource (such as updating a goal or key result), include the resource ID at the appropriate position in the URL path.

For endpoints that require resource IDs in the URL path (for example, https://api.leapsome.com/v1/goals/{'{goalId}'}/progress), ensure the ID is included in the URL. The full list of available Leapsome API endpoints is documented at api.leapsome.com/v1/api-docs.

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 — Nexla automatically adds the Bearer token from your Leapsome credential to every request.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Leapsome 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 Leapsome write endpoints (such as Update Goal Progress and Update Key Result Progress) are designed to receive one record per API call. For these endpoints, leave record batching disabled. Batching is more useful for Leapsome endpoints that accept bulk payloads.

Response Webhook​

Optional

Nexla can automatically send the response received from the Leapsome 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 Leapsome 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 Leapsome 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 Leapsome 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 begin sending data to the configured Leapsome endpoint, open the destination resource menu, and select Activate.

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