Skip to main content

Float 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 Float location.
float_api.png

Float

Create a Float Destination​

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

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

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

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

    Creates a new client record in Float. Use this endpoint when you need to add client records to Float programmatically—for example, when synchronizing a CRM or project management tool with Float, or when onboarding new clients in bulk.

    • Map the client name to the name field in your Nexset. This is the required field for creating a client record in Float. Float will reject requests where the name field is absent or empty.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one client per record.

    After creation, Float assigns each client a unique client_id. This ID is referenced by project records when associating a project with a client. Consider chaining a List Clients source after this destination if downstream flows need the assigned client IDs.

    Create Person

    Creates a new team member (person) record in Float. Use this endpoint to add team members to Float programmatically—for example, when synchronizing an HR system or directory with Float, or when onboarding multiple new employees at once.

    • Map the following fields from your Nexset to the corresponding Float fields:

      • name (required): The full name of the team member.
      • email (optional): The team member's email address.
      • job_title (optional): The team member's job title.
      • department_id (optional): The ID of the department to which this person belongs. Use the List Departments source to retrieve valid department IDs.
      • tags (optional): An array of tags to associate with this person.
      • work_days_hours (optional): A configuration array specifying the number of working hours per day for each day of the week.
      • contractor (optional): A boolean indicating whether this person is a contractor (true) or a full-time employee (false).
    • Each record in your Nexset will be sent to Float as a separate API call, creating one person per record.

    After creation, Float assigns each person a unique people_id. This ID is referenced by allocations, time off entries, and logged time records. Consider chaining a List People source after this destination if downstream flows need the assigned IDs.

    Create Project

    Creates a new project record in Float. Use this endpoint to add projects to Float programmatically—for example, when synchronizing a project management tool, ERP system, or CRM with Float to keep project records in sync.

    • Map the following fields from your Nexset to the corresponding Float fields:

      • name (required): The name of the project.
      • client_id (optional): The ID of the client associated with this project. Use the List Clients source to retrieve valid client IDs.
      • color (optional): A hex color code used to display the project in the Float schedule (e.g., #FF5733).
      • tags (optional): An array of tags to associate with this project.
      • budget_type (optional): The type of budget tracking for this project (e.g., hours or money-based).
      • budget_total (optional): The total budget allocated to this project.
      • project_manager (optional): The people_id of the team member assigned as project manager.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one project per record.

    After creation, Float assigns each project a unique project_id. This ID is referenced by allocations, phases, milestones, and project tasks. Consider chaining a List Projects source after this destination if downstream flows need the assigned project IDs.

    Create Allocation

    Creates a new allocation (scheduled work assignment) in Float. An allocation links a team member to a project for a specific date range and number of hours. Use this endpoint to programmatically schedule work in Float—for example, when ingesting project plans from an external tool or automating resource assignment workflows.

    • Map the following fields from your Nexset to the corresponding Float fields:

      • people_id (required): The ID of the team member to whom this work is assigned. Use the List People source to retrieve valid people IDs.
      • project_id (required): The ID of the project this allocation is associated with. Use the List Projects source to retrieve valid project IDs.
      • start_date (required): The start date of the allocation in yyyy-MM-dd format.
      • end_date (required): The end date of the allocation in yyyy-MM-dd format.
      • hours (required): The number of hours per day allocated for this assignment.
      • name (optional): A label or note for this allocation.
      • notes (optional): Additional notes about the allocation.
      • status (optional): The status of the allocation (e.g., confirmed or tentative).
      • billable (optional): A boolean indicating whether this allocation is billable.
      • repeat_state (optional): A value indicating whether and how the allocation repeats.
      • repeat_end_date (optional): The date on which a repeating allocation should stop, in yyyy-MM-dd format.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one allocation per record.

    Dates must be provided in yyyy-MM-dd format (e.g., 2026-06-15). The people_id and project_id values must correspond to existing records in Float. Use the List People and List Projects source endpoints to retrieve valid IDs before creating allocations.

    Create Logged Time

    Creates a new logged time entry in Float. Logged time records capture actual hours worked by a team member on a project on a specific date. Use this endpoint to write time-tracking data into Float from an external timesheet system or to bulk-import historical time records.

    • Map the following fields from your Nexset to the corresponding Float fields:

      • people_id (required): The ID of the team member who logged the time. Use the List People source to retrieve valid people IDs.
      • project_id (required): The ID of the project the time was logged against. Use the List Projects source to retrieve valid project IDs.
      • date (required): The date on which the time was worked, in yyyy-MM-dd format.
      • hours (required): The number of hours logged.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one logged time entry per record.

    The people_id and project_id values must correspond to existing records in Float. Dates must be in yyyy-MM-dd format.

    Create Department

    Creates a new department record in Float. Use this endpoint to add departments to Float programmatically—for example, when syncing organizational structure from an HR system.

    • Map the department name to the name field in your Nexset. This is the primary field for creating a department in Float.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one department per record.

    Create Project Expense

    Creates a new project expense entry in Float. Project expenses track costs incurred for a project, such as software subscriptions, travel, or materials. Use this endpoint to log project expenses in Float from an external expense management system or financial tool.

    • Map the following fields from your Nexset to the corresponding Float fields:

      • name (required): A descriptive name for the expense (e.g., "Software License," "Travel").
      • date (required): The date of the expense in yyyy-MM-dd format.
      • cost (required): The cost amount of the expense.
      • project_id (required): The ID of the project this expense is associated with. Use the List Projects source to retrieve valid project IDs.
      • billable (optional): A boolean indicating whether this expense is billable to the client.
      • markup (optional): A markup percentage or amount applied to the expense for billing.
      • markup_type (optional): The type of markup (e.g., percentage or fixed amount).
    • Each record in your Nexset will be sent to Float as a separate API call, creating one expense record per record.

    Create Milestone

    Creates a new project milestone in Float. Milestones mark key dates or deliverables within a project. Use this endpoint to programmatically add milestones to Float projects—for example, when importing a project plan from an external scheduling or project management tool.

    • Map the milestone name, associated project ID, and target date fields from your Nexset to the corresponding Float fields.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one milestone per record.

    The project_id value must correspond to an existing project in Float. Dates must be in yyyy-MM-dd format.

    Update Client

    Updates an existing client record in Float. Use this endpoint to modify client attributes—for example, renaming a client or updating their details when a change occurs in your CRM or billing system.

    • Enter the ID of the client to be updated in the Client Id parameter field. This is a required parameter that identifies which client record Float should update. Use the List Clients source to retrieve valid client IDs.
    • Map the updated client fields from your Nexset (such as name) to the corresponding Float fields. Only the fields included in the payload will be updated; other fields will remain unchanged.
    • Each record in your Nexset will be sent to Float as a separate PATCH request, updating one client per record.

    The Float API uses PATCH for update operations, meaning only the fields included in the request body will be modified. Fields not included in the payload will retain their existing values.

    Update Department

    Updates an existing department record in Float. Use this endpoint to rename or modify department attributes when organizational changes occur.

    • Enter the ID of the department to be updated in the Department Id parameter field. This is a required parameter. Use the List Departments source to retrieve valid department IDs.
    • Map the updated department fields from your Nexset to the corresponding Float fields. Only the fields included in the payload will be updated.
    • Each record in your Nexset will be sent to Float as a separate PATCH request, updating one department per record.

    Update Logged Time

    Updates an existing logged time entry in Float. Use this endpoint to correct or modify previously logged time records—for example, to adjust hours, update the date, or add notes to an existing entry.

    • Enter the ID of the logged time entry to be updated in the Logged Time Id parameter field. This is a required parameter. Use the List Logged Time source to retrieve valid logged time IDs.
    • Map the updated fields from your Nexset (such as hours, date, or notes) to the corresponding Float fields. Only the fields included in the payload will be updated.
    • Each record in your Nexset will be sent to Float as a separate PATCH request, updating one logged time entry per record.

    Update Project Task

    Updates an existing project task definition in Float. Use this endpoint to modify project task attributes such as task name or budget hours when project scope or planning changes.

    • Enter the ID of the project task to be updated in the Task Id parameter field. This is a required parameter. Use the List Project Tasks source to retrieve valid task IDs.
    • Map the updated task fields from your Nexset (such as name or budget_hours) to the corresponding Float fields. Only the fields included in the payload will be updated.
    • Each record in your Nexset will be sent to Float as a separate PATCH request, updating one project task per record.

    Update Time Off

    Updates an existing time off entry in Float. Use this endpoint to modify time off records when dates, hours, or other attributes change—for example, when syncing approved time off from an HR system into Float.

    • Enter the ID of the time off entry to be updated in the Timeoff Id parameter field. This is a required parameter. Use the List Time Off source to retrieve valid time off IDs.
    • Map the updated fields from your Nexset to the corresponding Float fields. Only the fields included in the payload will be updated.
    • Each record in your Nexset will be sent to Float as a separate PATCH request, updating one time off entry per record.

    The Float API uses PATCH for update operations, meaning only the fields included in the request body will be modified. Fields not included in the payload will retain their existing values.

    Create a Project Phase

    Creates a new project phase in Float. Phases represent distinct stages within a project (e.g., "Discovery," "Design," "Development," "Launch") and include start and end dates. Use this endpoint to programmatically add phases to Float projects when managing project timelines from an external planning tool.

    • Map the phase name, associated project ID, start date, and end date fields from your Nexset to the corresponding Float fields.
    • Each record in your Nexset will be sent to Float as a separate API call, creating one phase per record.

    The project_id value must correspond to an existing project in Float. Dates must be in yyyy-MM-dd format.

Configure Manually​

Float destinations can be manually configured to send data to any valid Float API endpoint. Manual configuration provides maximum flexibility for sending data to Float write endpoints not covered by pre-built templates or for applying additional customizations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Float 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 Float API from the Method pulldown menu. Float uses the following HTTP methods for write operations:

    • POST: For creating new records (clients, people, projects, allocations, logged time, etc.)
    • PATCH: For updating existing records (partial updates — only specified fields are changed)
    • PUT: For replacing existing records entirely
    • DELETE: For removing records

Data Format​

  1. Select the format in which the Nexset data will be sent to the Float API from the Content Format pulldown menu. Float's API accepts data in JSON format (application/json). Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Float 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 the full endpoint path. For update or delete operations, include the record's unique ID at the end of the URL.

All Float API write endpoints use the base URL https://api.float.com/v3. For example, to create a new project, the endpoint URL is https://api.float.com/v3/projects. To update a specific client with ID 123, the endpoint URL is https://api.float.com/v3/clients/123. A full list of available endpoint paths is available in the Float API Reference.

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

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

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Float 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 Float 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—for example, to capture the newly assigned record IDs returned by Float after creating people, projects, or allocations.

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

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