LAS Export: tasks

Modified on Wed, Sep 2 at 4:37 PM

TABLE OF CONTENTS


Overview

Grain: One row per task per application  |  Primary key: id  |  Foreign key: application_id → loan_applications.id

Tasks represent required actions or document requests tied to an application. System-generated tasks are created automatically by workflow rules; user-created tasks are added manually by staff.

Delivery folders: las_tasks-1-day and las_tasks-30-day

This article covers one table. For delivery options, ingestion guidance, the full table relationship diagram, and the export FAQ, see Data Exports: Clutch Lending LOS (LAS).


Things to Know About This Table

  • participant_id links a task to a specific applicant; it is null for application-level tasks.
  • metadata is a JSON payload whose schema varies by task_type.

Data Dictionary

Field NameDescriptionExampleRequired?
idUUID: unique task record identifier.6f5e4d3c-2b1a-4099-8877-665544332211Yes
application_idUUID: foreign key to loan_applications.a1b2c3d4-e5f6-7890-abcd-ef1234567890Yes
partner_idUUID: your credit union identifier.550e8400-e29b-41d4-a716-446655440000Yes
participant_idUUID: applicant this task is associated with. Null for application-level tasks.9b2d5e12-3c4f-4a8b-9d6e-1f2a3b4c5d6eNo
condition_idUUID: links to an approval condition if applicable. Null for unconditional tasks.8a7b6c5d-4e3f-4211-a099-887766554433No
titleString: human-readable task title as shown in the Clutch platform.Upload proof of incomeYes
descriptionString: optional detailed instructions or context for the task.Most recent pay stub covering 30 daysNo
task_typeEnum: task category: NEEDS_PROOF_OF_INCOME / NEEDS_DRIVER_LICENSE / NEEDS_FRAUD_CHECK / MANUAL_TASK / and othersNEEDS_PROOF_OF_INCOMEYes
stageEnum: workflow stage the task belongs to: ALERT / DECISION / CLOSING / POST_CLOSING / REVIEWDECISIONYes
statusEnum: current status: PENDING / COMPLETED / CANCELLEDCOMPLETEDYes
originEnum: how the task was created: SYSTEM (automated) or USER (staff-created)SYSTEMYes
created_byString: user ID of the staff member who created the task. Null for SYSTEM tasks.usr_3c7d22No
completed_atTimestamp: when the task was completed. Null if PENDING or CANCELLED.2026-06-12T15:45:00ZNo
completed_byString: user ID of whoever completed the task.usr_8f2a91No
reopened_atTimestamp: when the task was most recently reopened. Null if never reopened.2026-06-13T09:20:00ZNo
reopened_byString: user ID of the staff member who reopened the task.usr_3c7d22No
reopened_comment_idUUID: reference to the comment that explains why the task was reopened.1c2d3e4f-5a6b-4788-9900-aabbccddeeffNo
metadataJSON: task-type-specific supplementary data. Schema varies by task_type.{"documentType": "PAY_STUB"}No
created_onTimestamp: when the task was created.2026-06-11T10:20:00ZYes
updated_onTimestamp: when the task record was last modified.2026-06-12T15:45:00ZYes

How This Table Joins to the Others

  • application_id → loan_applications.id.
  • participant_id → participants.id (nullable).
  • comments.entity_id points to this table's id when comments.entity_type is TASK.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article