Flowlu Data Source

The Flowlu connector enables you to ingest data from your Flowlu workspace into Nexla, including tasks, projects, CRM leads, accounts, contacts, pipelines, invoices, financial transactions, agile boards, calendar events, and products. Follow the instructions below to create a new data flow that ingests data from a Flowlu source in Nexla.

Flowlu

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

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

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

Returns a list of all tasks in your Flowlu workspace. Use this endpoint to ingest task data for reporting, analysis, or synchronization with other systems. This endpoint uses paginated fetching, automatically retrieving all pages of results.

• This endpoint automatically retrieves all tasks in your Flowlu account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint fetches tasks in pages of up to 100 records per request and continues until all tasks have been retrieved.

Task records include details such as task name, assignee, due date, status, priority, and associated project. For complete information about the task fields returned by this endpoint, refer to the Flowlu API documentation.

List Projects

Returns a list of all projects in your Flowlu workspace. Use this endpoint to ingest project data for portfolio analysis, progress tracking, or integration with external reporting tools. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all projects in your Flowlu account. No additional configuration is required beyond selecting this endpoint template.
• Project records include details such as project name, status, owner, start and end dates, and budget information.

For complete information about the project fields returned by this endpoint, refer to the Flowlu API documentation.

List Accounts

Returns a list of all CRM accounts (companies and organizations) in your Flowlu workspace. Use this endpoint to sync your Flowlu CRM company data with external CRM platforms, data warehouses, or analytics tools.

• This endpoint retrieves all CRM account records from the Flowlu CRM module. No additional configuration is required beyond selecting this endpoint template.
• Account records include company name, contact details, assigned owner, and any custom fields configured for your workspace.

List Contacts

Returns a list of CRM contacts (individual people, distinct from company accounts) in your Flowlu workspace. Use this endpoint to sync individual contact records with marketing platforms, external CRM systems, or analytics tools.

• This endpoint retrieves all individual contact records from the Flowlu CRM module. No additional configuration is required beyond selecting this endpoint template.
• Contact records include first and last name, email addresses, phone numbers, associated accounts, and any custom fields configured in your workspace.

List Leads

Returns a list of all CRM leads in your Flowlu workspace. Use this endpoint to analyze lead data, track conversion rates, or sync lead information with marketing automation or external CRM systems.

• This endpoint retrieves all lead records from the Flowlu CRM module. No additional configuration is required beyond selecting this endpoint template.
• Lead records include lead name, source, status, assigned owner, associated pipeline, and any custom fields configured for leads in your workspace.

List Pipelines

Returns a list of all CRM pipelines in your Flowlu workspace. Use this endpoint to retrieve pipeline definitions and stages for reporting or to synchronize pipeline configuration data with other systems.

• This endpoint retrieves all CRM pipeline records from the Flowlu CRM module. No additional configuration is required beyond selecting this endpoint template.
• Pipeline records include pipeline name, stages, and configuration details.

List Emails

Returns a list of emails from the Flowlu CRM module. Use this endpoint to analyze email communications with leads and customers, track engagement, or archive CRM email activity in an external system. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all CRM email records in your Flowlu account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint fetches email records in pages of up to 100 records per request and continues until all records have been retrieved.

List Invoices

Returns a list of invoices from the Flowlu finance module. Use this endpoint to sync invoice data with accounting platforms, generate financial reports, or analyze billing activity. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all invoice records from the Flowlu finance module. No additional configuration is required beyond selecting this endpoint template.
• Invoice records include invoice number, client, line items, amounts, due dates, payment status, and associated project or opportunity.

For detailed information about the invoice fields returned, refer to the Flowlu API documentation.

List Invoice Items

Returns a list of all line items associated with invoices in the Flowlu finance module. Use this endpoint to analyze individual invoice line items for detailed revenue reporting or product-level financial analysis. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all invoice line item records. No additional configuration is required beyond selecting this endpoint template.

List Invoice Contacts

Returns a list of contacts associated with invoices in the Flowlu finance module. Use this endpoint to link invoice data to the corresponding contacts for reporting or billing analysis. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all invoice contact records. No additional configuration is required beyond selecting this endpoint template.

List Estimates

Returns a list of all estimates (quotes) in the Flowlu finance module. Use this endpoint to track the sales quoting process, analyze estimate conversion rates, or sync estimate data with external accounting tools. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all estimate records from the Flowlu finance module. No additional configuration is required beyond selecting this endpoint template.
• Estimate records include estimate number, associated client and opportunity, line items, total amounts, and current status.

List Transactions

Returns a list of all financial transactions in the Flowlu finance module. Use this endpoint for comprehensive financial reporting, cash flow analysis, or syncing transaction data with your accounting or ERP system. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all financial transaction records. No additional configuration is required beyond selecting this endpoint template.
• Transaction records include transaction type, amount, date, associated account, and linked invoice or project.

List Customer Payments

Returns a list of customer payments from the Flowlu finance module. Use this endpoint to track payment activity, reconcile payments against invoices, or analyze payment trends. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all customer payment records from the Flowlu finance module. No additional configuration is required beyond selecting this endpoint template.
• Payment records include payment amount, date, payment method, associated invoice, and client information.

List Products

Returns a list of products in the Flowlu Products module. Use this endpoint to sync your product catalog with other systems, generate product reports, or analyze product usage across invoices and estimates.

• This endpoint retrieves all product records from the Flowlu Products module. No additional configuration is required beyond selecting this endpoint template.
• Product records include product name, description, price, and any associated tax or discount configurations.

List Task Lists

Returns a list of task lists (organizational groupings for tasks) from the Flowlu task module. Use this endpoint to retrieve task list metadata for reporting or to understand how tasks are organized within your workspace. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all task list records. No additional configuration is required beyond selecting this endpoint template.

List Task List Items

Returns a list of task list items (checklist items within tasks) from the Flowlu task module. Use this endpoint to retrieve detailed checklist data associated with tasks for granular task tracking and reporting.

• This endpoint retrieves all task list item records from the Flowlu task module. No additional configuration is required beyond selecting this endpoint template.

List Calendar Events

Returns a list of calendar events from the Flowlu calendar module. Use this endpoint to sync Flowlu calendar events with external calendar systems, analyze scheduling patterns, or track meeting and event activity across your team.

• This endpoint retrieves all calendar event records from the Flowlu calendar module. No additional configuration is required beyond selecting this endpoint template.
• Calendar event records include event title, start and end datetime, participants, and associated records such as tasks or opportunities.

List Agile Stages

Returns a list of agile project stages from the Flowlu agile module. Use this endpoint to retrieve agile board stage definitions for reporting or to synchronize agile workflow configuration with external project management tools. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all agile stage records from the Flowlu agile module. No additional configuration is required beyond selecting this endpoint template.
• Stage records include stage name, order, and associated agile board or project.

List Agile Sprints

Returns a list of agile sprints from the Flowlu agile module. Use this endpoint to analyze sprint performance, track velocity, or sync sprint data with external reporting or project management tools. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all agile sprint records. No additional configuration is required beyond selecting this endpoint template.
• Sprint records include sprint name, start and end dates, goal, status, and associated project or board.

List Agile Issues

Returns a list of agile issues (stories, bugs, or tasks on agile boards) from the Flowlu agile module. Use this endpoint to track agile backlog items, analyze issue resolution trends, or sync agile issue data with other project management or analytics tools. This endpoint uses paginated fetching.

• This endpoint automatically retrieves all agile issue records. No additional configuration is required beyond selecting this endpoint template.
• Issue records include issue title, type, status, assignee, sprint, story points, and associated project or board.

Agile issues in Flowlu encompass user stories, bugs, tasks, and other work items managed on agile boards. For complete information about agile issue fields, refer to the Flowlu API documentation.

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

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

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 Flowlu API from the Method pulldown menu. The most common methods are:

   • GET: For retrieving data from the API
   • POST: For sending data to the API or triggering actions

API Endpoint URL

3. Enter the URL of the Flowlu 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 your account subdomain.

   Flowlu API URLs follow the pattern: https://{'{account_domain}'}.flowlu.com/api/v1/module/{'{module}'}/{'{resource}'}/list

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

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 complete information about available Flowlu API endpoints, refer to the Flowlu API documentation.

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.

Macros are particularly useful for Flowlu API endpoints that support date range filtering, enabling you to ingest only data that falls within a specific time window relative to when the flow runs.

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

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 Flowlu API endpoints that reference specific IDs or values from other data sources in your Nexla environment—for example, fetching tasks for a specific project ID retrieved from a separate source.

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 returned by a Flowlu 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.

For example, many Flowlu API endpoints return data in a nested structure such as $.response.items[*] or $.data[*]. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when Flowlu API responses have nested structures. Without specifying the correct path, Nexla might not properly parse and organize your data into usable records. Common Flowlu response data paths include $.response.items[*] and $.data[*].

• 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[*] to access an array of records within a data object, or $.response.items[*] to access an items array nested inside a response object).
  Path to Data Example:

  If the Flowlu API response contains a top-level response object with an items array, the path to the relevant data would be entered as $.response.items[*]. For endpoints that return data directly in a data array, use $.data[*].

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.

  

Metadata

If metadata is included in the Flowlu API 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.

For example, when a Flowlu API call returns a list of tasks, the response will typically include pagination metadata (such as total count) alongside the items array. If you have specified $.response.items[*] as the path to relevant data but want to preserve the total count or other response-level metadata, you can specify a path to this metadata to include it with each record.

• 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). Additional headers may be required for API versioning or content type specifications.

  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.

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