Skip to main content

Float Data Source

The Float connector enables you to ingest scheduling, workforce, and project data from your Float account into Nexla data flows. This is particularly useful for analytics pipelines, capacity reporting, workforce dashboards, and cross-system integrations that need access to Float's people, project, allocation, time off, and time-tracking data. Follow the instructions below to create a new data flow that ingests data from a Float source in Nexla.
float_api.png

Float

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 Float connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Float instance, and click Next; or, create a new Float credential for use in this flow.

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

    Float sources can also be configured manually, allowing you to ingest data from Float 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 Float API endpoints. Each template is designed specifically for the corresponding Float 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.

List Accounts

Returns a list of all accounts accessible to the authenticated user. Use this endpoint to retrieve Float account-level information, including account IDs and configuration details, which can be useful as a reference for other API operations or for audit purposes.

  • This endpoint requires no additional configuration beyond selecting the template. Nexla will automatically retrieve all account records accessible to the API key associated with your credential.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

Float returns up to 200 records per page. For accounts with a large number of accessible accounts, Nexla will handle multi-page retrieval automatically using page-based pagination.

List Departments

Returns a list of all departments defined in your Float account. Use this endpoint to extract organizational structure data, such as department names and IDs, which can be joined with people and project data for workforce reporting and analysis.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all department records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

Department records include the department name and its unique identifier. Use the department ID when cross-referencing people records that include a department_id field.

List People

Returns a list of all people (team members) in your Float account. This is one of the most commonly used endpoints, providing access to all team member records including names, job titles, departments, roles, work hours configurations, contractor status, email addresses, and tags. Use this endpoint for workforce reporting, headcount analysis, or to build a people directory.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all people records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

People records include the people_id field, which is used as a foreign key in allocations, time off, and logged time records. Retaining this field is recommended when building joins across Float data sets.

List Roles

Returns a list of all roles defined in your Float account. Roles represent job functions or skill categories (e.g., "Designer," "Developer," "Project Manager") that can be assigned to team members. Use this endpoint to extract role definitions for workforce planning reports or skills-based analytics.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all role records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Public Holidays

Returns a list of all public holidays configured in your Float account. Float allows teams to configure public holiday calendars so that scheduled time off and work hours respect regional holidays. Use this endpoint to extract public holiday data for capacity planning, payroll systems, or compliance reporting.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all public holiday records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Holidays

Returns a list of all team holidays in your Float account. Unlike public holidays, team holidays are custom holidays defined specifically for your team or organization. Use this endpoint to retrieve team-specific time-off periods for capacity planning or HR reporting.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all team holiday records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Projects

Returns a list of all projects in your Float account. Project records include fields such as project name, client, color, tags, budget type, budget totals, project managers, and project team members. Use this endpoint to extract project data for project portfolio reporting, budget tracking, or integration with project management tools.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all project records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

Projects include a project_id field that is referenced in allocations, phases, milestones, and project tasks. Retaining this field is recommended when building joins across Float data sets.

Get Status

Returns current status information from the Float API, including status records associated with people or projects. Use this endpoint to retrieve status data for reporting or monitoring purposes.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all status records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Time Off

Returns a list of all time off entries in your Float account. Time off records include information about which team members have scheduled time away, the type of time off, and the associated dates and hours. Use this endpoint for absence reporting, capacity planning, and HR analytics.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all time off records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

Time off records reference people_id and timeoff_type_id fields. Use the List People and List Time Off Types endpoints to retrieve the corresponding reference data for building complete reports.

List Time Off Types

Returns a list of all time off types defined in your Float account (e.g., "Vacation," "Sick Leave," "Personal"). Use this endpoint to retrieve time off type definitions for use as a lookup reference when analyzing time off entries.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all time off type records from your Float account.

List Clients

Returns a list of all clients in your Float workspace. Client records store client names and their unique identifiers, which are referenced by project records. Use this endpoint to extract client data for billing reports, client portfolio analysis, or CRM integrations.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all client records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Phases

Returns a list of all project phases in your Float workspace. Phases represent distinct stages within a project (e.g., "Discovery," "Design," "Development," "Launch") and include start and end dates. Use this endpoint to track project progress across phases or to feed project timeline data into reporting tools.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all phase records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Project Tasks

Returns a list of all project tasks in your Float workspace. Project tasks define the types of work that can be allocated to team members within a project, including task names and associated budget hours. Use this endpoint to extract task definitions for project planning reports or budget utilization analysis.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all project task records from your Float account.

List Milestones

Returns a list of all project milestones in your Float workspace. Milestones mark key dates or deliverables within a project. Use this endpoint to extract milestone data for project tracking dashboards, delivery reporting, or project management tool integrations.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all milestone records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

List Tasks

Returns a list of all allocations (tasks) in your Float workspace. In Float, allocations represent scheduled work assignments that link a team member to a project for a specified date range and number of hours. Allocation records include fields such as people_id, project_id, start and end dates, hours, billable status, and repeat settings. This is one of the most analytically rich endpoints for understanding how team capacity is being utilized across projects.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all allocation records from your Float account.
  • Results are paginated automatically; Nexla will continue fetching pages until all records have been retrieved.

Allocation records reference both people_id and project_id. Use the List People and List Projects endpoints to retrieve the corresponding reference data for building complete utilization and capacity reports. The Float API documentation refers to allocations as "tasks" in its endpoint path (/v3/tasks).

List Logged Time

Returns a list of all time log entries in your Float workspace. Logged time records capture actual hours worked by team members against projects and tasks, as distinct from planned allocations. Use this endpoint to extract actuals data for timesheet reporting, billing, payroll, or planned-vs-actual analysis.

  • This endpoint requires no additional configuration. Nexla will automatically retrieve all logged time records from your Float account.

Logged time records include people_id, project_id, date, and hours fields. Combining logged time data with allocation data enables planned-versus-actual utilization analysis across your team.

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​

Float data sources can be manually configured to ingest data from any valid Float 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 Float sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

All Float API endpoints are accessible at the base URL https://api.float.com/v3. A full list of available endpoints is documented in the Float API Reference.

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 Float API from the Method pulldown menu. Float's read endpoints exclusively use the GET method. The most common methods are:

    • GET: For retrieving data from the Float API (used by all read/list endpoints)
    • POST: For sending data to the API or triggering actions (used when creating records)

API Endpoint URL​

  1. Enter the URL of the Float 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 the full endpoint path.

All Float API endpoints use the base URL https://api.float.com/v3. For example, to retrieve people records, use https://api.float.com/v3/people. To retrieve project records, use https://api.float.com/v3/projects. A full list of available endpoint paths is available in the Float API Reference.

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.

Date/time macros are particularly useful for Float endpoints that support date range filtering, such as filtering allocations or logged time entries by start and end date. For example, you can use macros to retrieve only records from the current month or the previous week.

  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}. Float's API accepts dates in yyyy-MM-dd format.

  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 Float API endpoints that reference specific IDs—for example, using a project ID retrieved from a List Projects source to fetch allocations for that specific project.

  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 the Float 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.

Float API endpoints typically return arrays of records directly at the top level of the JSON response (e.g., $[*]). For example, a call to /v3/people returns a top-level JSON array of person objects.

Path to Data is particularly useful when Float API responses contain nested structures or metadata alongside the primary data. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • 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 Float endpoints that return a top-level array, use $[*] as the path to data.

    Path to Data Example:

    If the Float API response returns a top-level JSON array of records, the path to the data would be entered as $[*].

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.

Metadata paths are particularly useful for preserving Float API response context like request IDs, pagination details, 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.

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). The Float API requires that all requests include a User-Agent header containing the name of your application and a contact email address.

    You do not need to include the Authorization header in this field, as it is automatically added by Nexla from your Float credential. However, you should include the required User-Agent header if it is not already configured. Example: User-Agent:NexlaFloatIntegration/1.0 (your@email.com).

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 Float 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.