Skip to main content
Flowlu is a comprehensive business management platform that combines CRM, project management, invoicing, and collaboration tools into a single suite. It helps businesses streamline operations, manage customer relationships, and track financial performance.

​
Configuring Flowlu as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Flowlu option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need your Flowlu API Key and Subdomain for this connection. You can generate an API key in your Flowlu account under Portal Settings > API Settings > Create. Once you have it, add the account access and the connector configuration. The following configurations are available:
  • API Key: Your Flowlu API Key.
  • Subdomain: The subdomain of your Flowlu account (e.g., ‘my-company’ for my-company.flowlu.com).
  • Start Date: The earliest date from which records will be synced.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Flowlu and their corresponding fields:
Stream for managing CRM leads.Key Fields:
  • id: Unique identifier for the opportunity.
  • name: Opportunity name.
  • budget: Estimated opportunity value.
  • customer_id: Identifier of the associated customer.
  • contact_id: Identifier of the associated contact.
  • source_id: Identifier of the opportunity source.
  • assignee_id: Identifier of the current owner.
  • pipeline_id: Identifier of the related pipeline.
  • pipeline_stage_id: Identifier of the pipeline stage.
  • active: Indicates whether the opportunity is active.
  • closing_status_id: Identifier of the closing status.
  • start_date: Timestamp when the opportunity started.
  • deadline: Deadline for closing the opportunity.
  • closing_date: Timestamp when the opportunity was closed.
  • created_date: Timestamp when the opportunity was created.
  • updated_date: Timestamp of the most recent update.
Contact Information:
  • contact_name: Primary contact name.
  • contact_phone: Primary contact phone number.
  • contact_mobile: Primary contact mobile number.
  • contact_email: Primary contact email address.
  • contact_web: Primary contact website.
  • contact_position: Primary contact job title.
  • contact_company: Primary contact company name.
Additional Fields:
  • description: Opportunity description.
  • merged_to_id: Identifier of the opportunity into which this record was merged.
  • closing_comment: Closing notes provided by the user.
  • ref: External reference code.
  • ref_id: External reference identifier.
  • created_by: User who created the opportunity.
  • updated_by: User who last updated the opportunity.
  • last_activity_id: Identifier of the last recorded activity.
  • last_activity_time: Timestamp of the last activity.
  • last_activity_model: Entity type of the last activity.
  • ordering: Ordering index among opportunities.
  • auto_calc: Indicates whether totals are calculated automatically.
  • shipping_charge: Shipping amount associated with the opportunity.
  • adjustment: Additional adjustment amount.
  • adjustment_description: Description of applied adjustments.
  • pricelist_id: Identifier of the price list in use.
  • deleted_at: Timestamp when the opportunity was soft-deleted.
  • extra_fields: Custom fields returned for the opportunity as a JSON string.
Stream for managing CRM accounts.Key Fields:
  • id: Unique identifier for the CRM account.
  • type: Account type code.
  • name: Name of the account.
  • first_name: First name when the account represents a person.
  • last_name: Last name.
  • active: Indicates whether the account is active.
  • created_date: Timestamp when the account was created.
  • updated_date: Timestamp of the most recent update.
  • owner_id: Identifier of the account owner.
  • industry_id: Identifier of the related industry.
  • account_category_id: Identifier of the account category.
Contact Information:
  • phone: Primary phone number.
  • phone2: Secondary phone number.
  • phone3: Tertiary phone number.
  • email: Primary email address.
  • email_personal: Personal email address.
  • web: Account website URL.
  • telegram: Telegram contact handle.
  • social_network_link_1: Social network link 1.
  • social_network_link_2: Social network link 2.
  • social_network_link_3: Social network link 3.
  • social_network_link_4: Social network link 4.
  • social_network_link_5: Social network link 5.
  • social_network_link_6: Social network link 6.
Address Information:
  • shipping_country: Shipping country.
  • shipping_state: Shipping state or region.
  • shipping_city: Shipping city.
  • shipping_zip: Shipping postal code.
  • shipping_address_line_1: Shipping address line 1.
  • shipping_address_line_2: Shipping address line 2.
  • shipping_address_line_3: Shipping address line 3.
  • billing_country: Billing country.
  • billing_state: Billing state or region.
  • billing_city: Billing city.
  • billing_zip: Billing postal code.
  • billing_address_line_1: Billing address line 1.
  • billing_address_line_2: Billing address line 2.
  • billing_address_line_3: Billing address line 3.
  • address: Primary address string.
  • address_legal: Legal address of the organization.
Legal & Financial Information:
  • name_legal: Short legal name.
  • name_legal_full: Full legal name.
  • VAT: Primary VAT/tax identifier.
  • VAT1: Secondary VAT/tax identifier 1.
  • VAT2: Secondary VAT/tax identifier 2.
  • bank_details: Banking details for the account.
  • organization_revenue: Reported organization revenue.
  • organization_expenses: Reported organization expenses.
  • organization_registration_date: Organization registration date.
Additional Fields:
  • honorific_title_id: Identifier of the honorific title.
  • middle_name: Middle name.
  • description: Account description or notes.
  • deleted_at: Timestamp when the account was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
  • cf_1: Custom field cf_1 value.
  • cf_4: Custom field cf_4 value.
  • merged_to: Identifier of the account this record merged into.
  • ref: External reference code.
  • ref_id: External reference identifier.
  • guid_1c: 1C integration GUID.
  • timezone: Account time zone.
  • organization_employee_count: Number of employees in the organization.
  • last_activity_id: Identifier of the last recorded activity.
  • last_activity_time: Timestamp of the last recorded activity.
  • last_activity_model: Entity type of the last activity.
Stream for managing CRM account categories.Key Fields:
  • id: Unique identifier for the account category.
  • name: Account category name.
  • ordering: Display ordering for the category.
  • created_by: User who created the category.
  • created_date: Timestamp when the category was created.
  • updated_by: User who last updated the category.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the category was soft-deleted.
  • active: Indicates whether the category is active.
Stream for managing company absence types.Key Fields:
  • id: Unique identifier for the absence type.
  • title: Name of the absence type.
  • color: Color associated with the absence type.
  • default_absence_duration: Default duration in days.
  • count_holidays: Indicates whether holidays are included when computing the absence duration.
  • created_by: User who created the absence type.
  • created_date: Timestamp when the type was created.
  • updated_by: User who last updated the type.
  • updated_date: Timestamp of the most recent update.
Stream for managing company absences.Key Fields:
  • id: Unique identifier for the absence record.
  • user_id: Identifier of the employee who is absent.
  • start_date: Timestamp when the absence starts.
  • end_date: Timestamp when the absence ends.
  • original_end_date: Original absence end timestamp before later adjustments.
  • absence_type_id: Identifier of the absence type.
  • comment: Comment provided for the absence.
  • created_by: User who created the absence record.
  • created_date: Timestamp when the record was created.
  • updated_by: User who last updated the record.
  • updated_date: Timestamp of the last update.
Stream for managing CRM emails.Key Fields:
  • id: Unique identifier for the email record.
  • email: Email address associated with the account.
  • type: Email type (for example, primary or alternate).
  • comment: Comment added to the email record.
  • account_id: Identifier of the CRM account linked to the email.
  • deleted_at: Timestamp when the email record was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing CRM honorific titles.Key Fields:
  • id: Unique identifier for the honorific title.
  • name: Name of the honorific title.
  • ordering: Ordering index for display.
  • created_by: User who created the honorific title.
  • created_date: Timestamp when the honorific title was created.
  • updated_by: User who last updated the honorific title.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the honorific title was soft-deleted.
  • active: Indicates whether the honorific title is active.
Stream for managing CRM industries.Key Fields:
  • id: Unique identifier for the industry.
  • name: Industry name.
  • ordering: Display ordering for the industry.
  • created_by: User who created the industry.
  • created_date: Timestamp when the industry record was created.
  • updated_by: User who last updated the industry.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the industry was soft-deleted.
  • active: Indicates whether the industry is active.
Stream for managing CRM lead followers.Key Fields:
  • id: Unique identifier for the opportunity follower.
  • lead_id: Identifier of the opportunity.
  • user_id: Identifier of the user following the opportunity.
  • created_by: User who created the follower record.
  • created_date: Timestamp when the follower record was created.
  • updated_by: User who last updated the follower record.
  • updated_date: Timestamp of the most recent update.
  • extrafields: Serialized extra fields returned by Flowlu.
Stream for managing CRM lead items.Key Fields:
  • id: Unique identifier for the opportunity item.
  • lead_id: Identifier of the opportunity associated with the item.
  • item_id: Identifier of the referenced product or service.
  • name: Name of the product or service.
  • unit_price: Unit price for the item.
  • quantity: Quantity of the item.
  • total: Total amount after taxes and discounts.
Additional Fields:
  • ordering: Ordering index of the item within the opportunity.
  • description: Description of the product or service.
  • unit: Unit of measure for the item.
  • unit_id: Identifier of the unit of measure.
  • tax1: Tax 1 applied to the item.
  • tax1_included: Indicates whether Tax 1 is included in the price.
  • tax1_amount: Amount charged for Tax 1.
  • tax2: Tax 2 applied to the item.
  • tax2_included: Indicates whether Tax 2 is included in the price.
  • tax2_amount: Amount charged for Tax 2.
  • discount_amount: Absolute discount amount applied.
  • discount: Discount value or percentage representation.
  • discount_is_percent: Indicates whether the discount is a percentage.
  • sub_total: Subtotal amount for the item.
  • tax_total: Total tax amount applied to the item.
  • tax_displayed: Tax label displayed on the item.
  • ref: External reference for the item.
  • ref_id: External identifier for the item.
  • type: Item type code.
  • deleted_at: Timestamp when the item was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing CRM loss reasons.Key Fields:
  • id: Unique identifier for the loss reason.
  • name: Name of the loss reason.
  • ordering: Display ordering for the reason.
  • created_by: User who created the loss reason.
  • created_date: Timestamp when the loss reason was created.
  • updated_by: User who last updated the loss reason.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the reason was soft-deleted.
  • active: Indicates whether the loss reason is active.
Stream for managing CRM phones.Key Fields:
  • id: Unique identifier for the phone record.
  • phone: Phone number associated with the account.
  • phone_masked: Masked representation of the phone number.
  • type: Phone type (for example, primary or alternate).
  • old_phone: Previously used phone number.
  • comment: Comment associated with the phone record.
  • account_id: Identifier of the CRM account linked to the phone.
  • deleted_at: Timestamp when the phone record was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing CRM pipeline stages.Key Fields:
  • id: Unique identifier for the stage.
  • name: Name of the stage.
  • pipeline_id: Identifier of the pipeline associated with the stage.
  • color: Highlight color used for the stage.
  • ordering: Ordering index within the pipeline.
  • created_by: User who created the stage.
  • created_date: Timestamp when the stage was created.
  • updated_by: User who last updated the stage.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the stage was soft-deleted.
  • active: Indicates whether the stage is active.
Stream for managing CRM pipelines.Key Fields:
  • id: Unique identifier for the pipeline.
  • name: Pipeline name.
  • description: Pipeline description.
  • type_access: Access type for the pipeline.
  • ordering: Ordering index for display.
  • created_by: User who created the pipeline.
  • created_date: Timestamp when the pipeline was created.
  • updated_by: User who last updated the pipeline.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the pipeline was soft-deleted.
  • active: Indicates whether the pipeline is active.
Stream for managing CRM relations.Key Fields:
  • id: Unique identifier for the CRM relation.
  • parent_acc_id: Identifier of the parent account.
  • child_acc_id: Identifier of the child account.
  • relation_name: Name of the relationship.
  • type: Relationship type code.
  • created_by: User who created the relationship.
  • created_date: Timestamp when the relationship was created.
  • updated_by: User who last updated the relationship.
  • updated_date: Timestamp of the most recent update.
Stream for managing CRM sources.Key Fields:
  • id: Unique identifier for the opportunity source.
  • name: Name of the opportunity source.
  • description: Description of the source.
  • ordering: Display order of the source.
  • created_by: User who created the source.
  • created_date: Timestamp when the source was created.
  • updated_by: User who last updated the source.
  • updated_date: Timestamp of the most recent update.
  • deleted_at: Timestamp when the source was soft-deleted.
  • active: Indicates whether the source is active.
Stream for managing project expenses.Key Fields:
  • id: Unique identifier for the projected expense.
  • project_id: Identifier of the project associated with the expense.
  • name: Name of the projected expense stage.
  • total: Projected amount for the expense.
  • status_paid: Payment status flag (0=unpaid, 1=partially paid, etc.).
  • org_id: Identifier of the associated organization.
  • category_id: Identifier of the expense category.
  • manager_id: Identifier of the manager responsible for the expense.
  • project_stage_id: Identifier of the related project stage.
  • created_by: User who created the expense record.
  • created_date: Timestamp when the record was created.
  • updated_by: User who last updated the record.
  • updated_date: Timestamp of the most recent update.
  • date: Planned date for realizing the expense.
Additional Fields:
  • description: Additional description for the expense.
  • org_account_id: Identifier of the organization’s financial account.
  • currency_id: Identifier of the currency used.
  • ordering: Display order of the projected expense.
  • crm_company_id: Identifier of the CRM company related to the expense.
Stream for managing project money stages.Key Fields:
  • id: Unique identifier for the projected revenue stage.
  • project_id: Identifier of the project associated with the forecast.
  • name: Name of the projected revenue stage.
  • total: Projected amount for this stage.
  • status_paid: Payment status flag (0=unpaid, 1=partially paid, etc.).
  • paid_date: Date on which the amount was paid.
  • plan_paid_date: Planned payment date.
  • org_id: Identifier of the related organization.
  • category_id: Identifier of the financial category.
  • manager_id: Identifier of the manager responsible for the forecast.
  • project_stage_id: Identifier of the related project stage.
  • created_by: User who created the revenue stage record.
  • created_date: Timestamp when the record was created.
  • updated_by: User who last updated the record.
  • updated_date: Timestamp of the most recent update.
Additional Fields:
  • description: Additional description for the forecast.
  • org_account_id: Identifier of the organization’s bank account.
  • currency_id: Identifier of the currency used.
  • ordering: Display order of the revenue stage.
  • crm_company_id: Identifier of the linked CRM company.
  • invoice_id: Identifier of the invoice linked to the stage.
Stream for managing project portfolios.Key Fields:
  • id: Unique identifier for the project portfolio.
  • name: Name of the project portfolio.
  • description: Portfolio description.
  • active: Indicates whether the portfolio is active.
  • status: Portfolio status code.
  • created_by: User who created the portfolio.
  • created_date: Timestamp when the portfolio was created.
  • updated_by: User who last updated the portfolio.
  • updated_date: Timestamp of the most recent update.
Additional Fields:
  • archive_date: Timestamp when the portfolio was archived.
  • archive_description: Reason or details for archiving.
  • ordering: Ordering index of the portfolio in lists.
  • deleted_at: Timestamp when the portfolio was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing project stage checkitems.Key Fields:
  • id: Unique identifier for the stage check item.
  • active: Indicates whether the check item is active.
  • name: Name of the check item.
  • ordering: Ordering index of the check item within the stage.
  • stage_id: Identifier of the associated project stage.
  • project_id: Identifier of the associated project, when applicable.
  • checked: Indicates whether the check item has been completed.
  • enddate: Deadline for completing the check item.
  • responsible_id: Identifier of the user responsible for the check item.
  • created_by: User who created the check item.
  • created_date: Timestamp when the check item was created.
  • updated_by: User who performed the last update.
  • updated_date: Timestamp of the most recent update.
Additional Fields:
  • description: Detailed description of the check item.
  • report: Default report content linked to the check item.
  • from_checkitem_id: Identifier of the originating check item when duplicated.
  • deleted_at: Timestamp when the check item was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing project stages.Key Fields:
  • id: Unique identifier for the project stage.
  • name: Short name for the stage.
  • fullname: Full descriptive name for the stage.
  • project_type_id: Identifier of the associated project type.
  • ordering: Ordering index of the stage inside the workflow.
  • color_class: CSS color class applied in the interface.
  • description: Detailed description of the project stage.
  • project_id: Identifier of the specific project when applicable.
Additional Fields:
  • ref: External reference for the stage.
  • ref_id: External identifier for the stage.
  • color: Color assigned to the stage.
  • deleted_at: Timestamp when the stage was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing project types.Key Fields:
  • id: Unique identifier for the project type.
  • name: Name of the project type.
  • description: Description of the project template.
  • ordering: Ordering index among available templates.
  • is_active: Indicates whether the template is active.
  • tasks_workflow_id: Identifier of the default task workflow for projects of this type.
Additional Fields:
  • report: Default report template for the project type.
  • auto_startdate_plus_days: Number of days automatically added to the start date.
  • auto_enddate_plus_days: Number of days automatically added to the end date.
  • ref: External reference for the project type.
  • ref_id: External identifier for the project type.
  • create_tasks_next_stage: Indicates whether tasks for the next stage are created automatically.
  • manual_close_checkitems: Indicates whether check items must be closed manually.
  • description_project: Default description applied to projects created from this template.
  • deleted_at: Timestamp when the project type was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing projects.Key Fields:
  • id: Unique identifier for the project.
  • name: Project name.
  • estimated_revenue: Estimated revenue for the project.
  • estimated_expenses: Estimated expenses for the project.
  • startdate: Actual start timestamp for the project.
  • enddate: Actual end timestamp for the project.
  • manager_id: Identifier of the project manager.
  • stage_id: Identifier of the current project stage.
  • project_type_id: Identifier of the project template/type.
  • briefcase_id: Identifier of the associated portfolio.
  • is_archive: Indicates whether the project is archived.
  • priority: Project priority level.
  • customer_id: Identifier of the customer associated with the project.
  • created_by: User who created the project.
  • created_date: Timestamp when the project was created.
  • updated_by: User who last updated the project.
  • updated_date: Timestamp of the most recent project update.
Billing Information:
  • billing_type: Billing type used for the project.
  • default_billing_rate: Default billing rate configured for the project.
  • default_employee_cost_rate: Default internal cost rate per employee.
  • default_bill_time_type: Default billable time category.
  • default_time_cost_type: Default time cost category.
  • use_default_invoice_split_type: Indicates whether the default invoice split type is used.
  • default_only_completed_task: Default setting controlling whether only completed tasks are billed.
  • bill_taxes: Indicates whether taxes are billed for the project.
  • default_invoice_split_type_in_project: Default invoice split type configured for the project.
  • default_invoice_item_format: Default format for invoice line items.
  • use_billing_tasks: Indicates whether dedicated billing tasks are used.
  • use_expenditure_part_tasks: Indicates whether expenditure part tasks are enabled.
Additional Fields:
  • description: Detailed project description.
  • ordering: Display order for the project.
  • customer_crm_contact_id: Identifier of the customer’s CRM contact.
  • archive_date: Timestamp when the project was archived.
  • workspace_id: Identifier of the workspace that owns the project.
  • archive_description: Explanation for why the project was archived.
  • crm_lead_id: Identifier of the associated CRM lead.
  • uuid: UUID that uniquely identifies the project.
  • ref: External reference code for the project.
  • ref_id: External reference identifier for the project.
  • tasks_workflow_id: Identifier of the default workflow applied to tasks.
  • deleted_at: Timestamp when the project was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.
Stream for managing task collaborators.Key Fields:
  • id: Unique identifier for the collaborator record.
  • task_id: Identifier of the related task.
  • user_id: Identifier of the collaborating user.
  • group_id: Identifier of the collaborator group.
  • created_by: User who added the collaborator to the task.
  • created_date: Timestamp when the collaborator was added.
  • updated_by: User who last updated the collaborator record.
  • updated_date: Timestamp of the most recent update.
Stream for managing task invoicing logs.Key Fields:
  • id: Unique identifier for the invoicing log entry.
  • task_id: Identifier of the related task.
  • invoice_id: Identifier of the associated invoice.
  • amount: Amount captured in the invoicing log.
  • created_by: User who created the invoicing log entry.
  • created_date: Timestamp when the entry was created.
  • updated_by: User who last updated the entry.
  • updated_date: Timestamp of the most recent update.
Stream for managing task lists.Key Fields:
  • id: Unique identifier for the task list.
  • name: Name of the task list.
  • user_id: Identifier of the user responsible for the list.
  • created_date: Timestamp when the list was created.
  • created_by: User who created the list.
  • updated_by: User who last updated the list.
  • updated_date: Timestamp of the most recent update.
  • active: Whether the list is currently active.
Additional Fields:
  • deleted_at: Timestamp when the task list was soft-deleted.
  • color: Color configured for the list.
  • icon: Icon associated with the list.
  • ordering: List position used for ordering.
Stream for managing task stages.Key Fields:
  • id: Unique identifier for the task stage.
  • name: Name of the stage.
  • description: Detailed description of the stage.
  • ordering: Ordering index for the stage.
  • created_date: Timestamp when the stage was created.
  • created_by: User who created the stage.
  • updated_by: User who last updated the stage.
  • updated_date: Timestamp of the most recent update.
  • workflow_id: Identifier of the associated workflow.
Additional Fields:
  • color: Color configured for the stage.
  • task_status: Task status linked to this stage.
  • deleted_at: Timestamp when the stage was soft-deleted.
Stream for managing task-to-list links.Key Fields:
  • id: Unique identifier for the task-to-list link.
  • task_id: Identifier of the linked task.
  • list_id: Identifier of the linked list.
  • created_date: Timestamp when the link was created.
  • created_by: User who created the link.
  • updated_by: User who last updated the link.
  • updated_date: Timestamp of the most recent update.
Stream for managing task workflows.Key Fields:
  • id: Unique identifier of the workflow.
  • name: Name of the workflow.
  • description: Detailed workflow description.
  • ordering: Display order within the workspace.
  • created_date: Timestamp when the workflow was created.
  • created_by: User who created the workflow.
  • updated_by: User who last updated the workflow.
  • updated_date: Timestamp of the last update to the workflow.
  • active: Whether the workflow is currently active.
Additional Fields:
  • deleted_at: Timestamp when the workflow was soft-deleted.
Stream for managing tasks.Key Fields:
  • id: Unique identifier for the task.
  • name: Task name.
  • description: Detailed task description.
  • parent_id: Identifier of the parent task.
  • deadline: Due timestamp for the task.
  • plan_start_date: Planned start timestamp.
  • plan_end_date: Planned end timestamp.
  • priority: Task priority level.
  • responsible_id: Identifier of the user responsible for the task.
  • time_estimate: Estimated effort in minutes.
  • time_spent: Time already spent in minutes.
  • created_date: Timestamp when the task was created.
  • owner_id: Identifier of the user who created the task.
  • updated_date: Timestamp of the last update.
  • status: Current task status code.
  • start_date: Actual start timestamp.
  • closed_date: Final closure timestamp.
  • project_stage_id: Identifier of the related project stage.
  • crm_account_id: Identifier of the linked CRM account.
  • workflow_id: Identifier of the workflow associated with the task.
  • workflow_stage_id: Identifier of the workflow stage.
Additional Fields:
  • report: Task report text.
  • prev_task_id: Identifier of the previous task in the sequence.
  • deadline_allowchange: Indicates whether the due date can be changed.
  • task_checkbyowner: Indicates whether the owner must review the task.
  • cost: Cost associated with the task.
  • price: Price associated with the task.
  • cost_type: Cost type code.
  • price_type: Price type code.
  • updated_by: Identifier of the user who last updated the task.
  • status_firstviewdate: Timestamp when the status was first viewed.
  • first_closed_date: Timestamp of the first closure event.
  • closed_by: Identifier of the user who closed the task.
  • return_count: Number of returns or reopenings.
  • rating: Task rating score.
  • status_updated_by: Identifier of the user who updated the status.
  • status_updated_date: Timestamp when the status was updated.
  • ref: External reference code.
  • ref_id: Identifier of the external reference.
  • module: Associated Flowlu module.
  • model: Associated Flowlu model.
  • model_id: Identifier of the associated model.
  • project_checkitem_id: Identifier of the related checklist item.
  • type: Task type code.
  • report_complete: Completion report text.
  • ordering: Ordering index for presentation.
  • all_day: Indicates whether the task spans the entire day.
  • uuid: UUID that uniquely identifies the task.
  • public_template: Indicates whether the task is a public template.
  • template_id: Identifier of the associated template.
  • is_repeat: Indicates whether the task is part of a repeat schedule.
  • is_recurrence: Indicates whether the task is a recurrence instance.
  • recurrence_id: Identifier of the recurrence series.
  • recurrence_parent_id: Identifier of the parent task in the recurrence.
  • recurrence_original_start_date: Original start timestamp for the recurrence series.
  • event_location: Location string for the related calendar event.
  • event_color: Color assigned to the calendar event.
  • event_busy_status: Busy status value for the event.
  • event_access_type: Access type setting for the event.
  • event_calendar_id: Identifier of the calendar that holds the event.
  • event_type: Event type code.
  • event_etag: Event ETag used for synchronization.
  • event_sync_type: Event synchronization type.
  • archive_status: Archive status code for the task.
  • is_archive: Indicates whether the task has been archived.
  • is_hidden: Indicates whether the task is hidden.
  • deleted_at: Timestamp when the task was soft-deleted.
  • extra_fields: Additional custom fields as a JSON string.