Actions35
- Adjustments Actions
- Assemblies Actions
- Batches Actions
- Companies Actions
- Contacts Actions
- Custom Fields Actions
- File Attachments Actions
- Inventory Actions
- Invoices Actions
- Locations Actions
- Orders Actions
- Packages Actions
- Payment Methods Actions
- Product POS Mappings Actions
- Products Actions
- Purchases Actions
- Strains Actions
- Test Results Actions
- Users Actions
Assemblies → Get Many
AI-generatedOverview
This node operation retrieves multiple assembly records from the Distru API. It supports filtering and pagination to manage large datasets effectively. Typical use cases include fetching a list of assemblies for inventory management, reporting, or integration with other systems.
Use Case Examples
- Fetch all assemblies created manually within a specific date range.
- Retrieve a paginated list of assemblies filtered by license number or creation source.
Properties
| Name | Meaning |
|---|---|
| Page Number | Specifies the page number for paginated results, allowing navigation through multiple pages of assemblies. |
| Page Size | Defines the number of assembly items to return per page, controlling the size of each paginated response. |
| Inserted Datetime | Filters assemblies by their creation datetime using a comma-separated range (e.g., '2024-01-01T00:00:00Z,2024-06-01T00:00:00Z'). |
| Updated Datetime | Filters assemblies by their last modified datetime using a comma-separated range. |
| Completion Datetime | Filters assemblies by their completion datetime range. |
| Creation Source | Filters assemblies based on their creation source, such as manually created, split package, sales order, or lab testing. |
| License Number | Filters assemblies by the license number associated with them. |
Output
JSON
data- The main array of assembly objects returned by the API, each representing an assembly record with its details.
Dependencies
- Distru API with an API token credential
Troubleshooting
- Ensure the Distru API token is set correctly; otherwise, the node will throw an error indicating the token is missing.
- If the 'Resource ID' parameter is required for other operations but missing, the node will throw an error.
- For GET operations, ensure that the additional fields for filtering are correctly formatted, especially datetime ranges as comma-separated strings.
- If the API returns an error, the node will throw it unless 'Continue On Fail' is enabled, in which case the error message will be included in the output JSON.