Skip to main content

Flowlu 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 Flowlu location.
flowlu_api.png

Flowlu

Create a Flowlu Destination​

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

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

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

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

    Create Task

    Creates a new task in your Flowlu workspace. Use this endpoint to programmatically create tasks from data in any Nexset—for example, to automatically generate Flowlu tasks from form submissions, external ticketing systems, or other business data sources.

    • Select this endpoint template and map the fields from your Nexset to the required Flowlu task fields. At minimum, Flowlu requires a task name. Additional fields such as assignee, due date, priority, and project association are optional but recommended for well-organized tasks.
    • Each record in the Nexset will result in one new task being created in Flowlu. Ensure the data in your Nexset includes all required task fields before activating the destination.

    For a complete list of fields supported when creating a task, refer to the Flowlu API documentation. Flowlu tasks can be assigned to projects, agile boards, and specific team members.

    Update Task

    Updates an existing task in your Flowlu workspace. Use this endpoint to keep Flowlu task data in sync with other systems—for example, to update task status, reassign tasks, change due dates, or modify other task attributes based on data from external sources.

    • Each record in the Nexset must include the unique Flowlu task ID of the task to be updated. The task ID can be obtained from the Flowlu API (using the List Tasks endpoint as a source) or from the Flowlu UI. Map the following fields from your Nexset to the appropriate Flowlu task fields:

      • Task ID: The unique identifier of the task to be updated (required).
      • Status: The new status for the task (optional).
      • Assignee: The user to whom the task should be reassigned (optional).
      • Due Date: The updated due date for the task (optional).
    • Only include fields that should be updated. Fields not included in the payload will retain their current values in Flowlu.

    Create Project

    Creates a new project in your Flowlu workspace. Use this endpoint to automatically provision Flowlu projects from data in other systems—for example, to create a new Flowlu project whenever a deal is closed in your CRM or a new client is onboarded.

    • Select this endpoint template and map the fields from your Nexset to the required Flowlu project fields. Flowlu requires a project name at minimum. Additional fields such as owner, start date, end date, budget, and client association are optional.
    • Each record in the Nexset will result in one new project being created in Flowlu.

    For a complete list of fields supported when creating a project, refer to the Flowlu API documentation.

    Create CRM Account

    Creates a new CRM account (company or organization record) in your Flowlu workspace. Use this endpoint to sync company data from other systems into Flowlu—for example, to import accounts from a marketing database, ERP system, or external CRM.

    • Select this endpoint template and map the fields from your Nexset to the Flowlu CRM account fields. Required fields include the account name. Additional fields such as industry, website, phone, address, and assigned owner are optional.
    • Each record in the Nexset will result in one new CRM account being created in Flowlu.

    Update CRM Account

    Updates an existing CRM account record in your Flowlu workspace. Use this endpoint to keep CRM account data synchronized with other systems—for example, to update company information, contact details, or custom fields from an external database or data source.

    • Each record in the Nexset must include the unique Flowlu account ID of the account to be updated. Map the following fields from your Nexset as needed:

      • Account ID: The unique identifier of the CRM account to be updated (required).
      • Any additional account fields that should be updated, such as name, phone, address, or custom fields.
    • Only include fields that should be updated. Fields not included in the payload will retain their current values in Flowlu.

    Create CRM Lead

    Creates a new CRM lead in your Flowlu workspace. Use this endpoint to automatically import leads from web forms, marketing platforms, or other lead generation tools directly into Flowlu's CRM pipeline.

    • Select this endpoint template and map the fields from your Nexset to the required Flowlu CRM lead fields. Flowlu requires a lead name at minimum. Additional fields such as contact information, source, pipeline, assigned owner, and custom fields are optional.
    • Each record in the Nexset will result in one new CRM lead being created in Flowlu.

    For a complete list of fields supported when creating a lead, refer to the Flowlu API documentation.

    Update CRM Lead

    Updates an existing CRM lead in your Flowlu workspace. Use this endpoint to keep lead data in sync with other systems—for example, to update a lead's pipeline stage, owner, or field values based on activity in external marketing or sales tools.

    • Each record in the Nexset must include the unique Flowlu lead ID of the lead to be updated. Map the following fields from your Nexset as needed:

      • Lead ID: The unique identifier of the CRM lead to be updated (required).
      • Any additional lead fields that should be updated, such as stage, owner, contact information, or custom fields.
    • Only include fields that should be updated. Fields not included in the payload will retain their current values in Flowlu.

    Create CRM Opportunity

    Creates a new CRM deal or opportunity in your Flowlu workspace. Use this endpoint to automatically create opportunities from external sales or marketing platforms—for example, to open a new Flowlu opportunity whenever a lead reaches a qualification threshold in another system.

    • Select this endpoint template and map the fields from your Nexset to the Flowlu CRM opportunity fields. Required fields include opportunity name. Additional fields such as associated account, pipeline, stage, expected close date, value, and assigned owner are optional.
    • Each record in the Nexset will result in one new CRM opportunity being created in Flowlu.

    Create Invoice

    Creates a new invoice in the Flowlu finance module. Use this endpoint to automatically generate invoices in Flowlu from billing data in other systems—for example, to create invoices from completed project milestones, subscription billing events, or orders in an e-commerce platform.

    • Select this endpoint template and map the fields from your Nexset to the required Flowlu invoice fields. Invoice fields include client reference, line items, amounts, due date, and any applicable taxes or discounts.
    • Each record in the Nexset will result in one new invoice being created in the Flowlu finance module.

    For a complete list of fields supported when creating an invoice, refer to the Flowlu API documentation.

    Create Agile Issue

    Creates a new agile issue or user story in the Flowlu agile module. Use this endpoint to automatically populate Flowlu agile boards from bug trackers, feedback tools, support ticket systems, or other external sources.

    • Select this endpoint template and map the fields from your Nexset to the Flowlu agile issue fields. Required fields include issue title. Additional fields such as issue type, description, assignee, story points, sprint, and associated project are optional.
    • Each record in the Nexset will result in one new agile issue being created on the corresponding Flowlu agile board.

    Agile issues in Flowlu include user stories, bugs, tasks, and other work items managed on agile boards. For a complete list of fields supported when creating an agile issue, refer to the Flowlu API documentation.

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the Flowlu 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 Flowlu API from the Method pulldown menu. Most Flowlu write operations (create and update) use POST.

Data Format​

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

API Endpoint URL​

  1. Enter the URL of the Flowlu API endpoint to which you want to send the Nexset data in the URL field. Flowlu API URLs follow the pattern https://{'{account_domain}'}.flowlu.com/api/v1/module/{'{module}'}/{'{resource}'}/create for create operations and .../update for update operations.

    For example, to create a task: https://mycompany.flowlu.com/api/v1/module/task/tasks/create

Your Flowlu API key is automatically appended as the api_key URL parameter by Nexla based on your credential configuration. You do not need to add it manually to the URL. For a complete list of available Flowlu API write endpoints, refer to the Flowlu API documentation.

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 any headers already present in the credentials. Authorization and authentication headers are handled automatically by Nexla based on your Flowlu credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Flowlu 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 Flowlu 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, the ID of a newly created record.

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

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