approve_arrival_date_update
ChatGPTApprove one arrival-date update from list_arrival_date_updates, the same as approving it on Logistify's Open Purchase Orders desk. The QuickBooks purchase order's expected date is replaced by the supplier's promised date; quantity and price stay as they are. Confirm the supplier, purchase order, and date with the person first. The update is queued, not finished: Logistify reads the purchase order back from QuickBooks to confirm it. This needs the person to have allowed changes when they connected Logistify.
approve_payment_match
ChatGPTApprove the suggested invoice match for one bank payment from list_payment_matches, the same as approving it on Logistify's Accounts Receivable page. Logistify then records the payment in QuickBooks Desktop against those invoices. Confirm the payment, customer, invoices, and amounts with the person first. The recording is queued, not finished, and Logistify stops if an invoice changed in QuickBooks. This needs the person to have allowed changes when they connected Logistify.
create_sales_order_in_quickbooks
ChatGPTCreate a new sales order in Logistify and send it to the company's QuickBooks Desktop file, as the Sales Orders screen and its Push button do. First find the customer with list_customers and each product with list_inventory_items, and use their QuickBooks IDs; never guess an ID. Before calling, read the order back to the person (customer, each product and quantity, any prices they gave, and the delivery date) and wait for a clear yes. A line without unit_price uses Logistify's price for that product, and a line with no price anywhere is refused. The customer and products must already be in Logistify. The order is created and its push is queued, not finished: check it later with list_logistify_sales_orders and the order number. Never call this twice for the same order; if the push did not start, use push_sales_order_to_quickbooks. This needs the person to have allowed changes when they connected Logistify.
get_profile
ChatGPTReturn the Logistify person and company this connection is signed in as. The opaque id is unique within this app and stays the same across token refresh, reconnection, and display-metadata changes.
get_purchase_order
ChatGPTRead one purchase order, with its lines and received quantities, by its QuickBooks ID (the id from list_purchase_orders, not the order number). The result is a page holding that one order.
list_arrival_date_updates
ChatGPTList the purchase order arrival-date updates waiting for a person to approve, oldest first. Each one would copy a date a supplier promised into the expected date of a QuickBooks purchase order; quantity and price never change. can_approve is false, with blocked_reason, when the purchase changed and the update can no longer go ahead. This reads Logistify, not QuickBooks.
list_customers
ChatGPTFind customers in the company's QuickBooks Desktop file. When the person names a customer, search with name_contains and let them choose if several match. Use customer_ids for exact QuickBooks IDs, or neither to browse. Returns one page; when next_cursor is set, pass it back with the same other inputs for the next page. One page is not the full customer list.
list_deposit_accounts
ChatGPTList the accounts in the company's QuickBooks Desktop file that a customer payment can be deposited to: active bank accounts, then Undeposited Funds. Each has only its ID, name, and kind; balances and account numbers are not included. The list comes in one page.
list_inventory_items
ChatGPTFind products in the company's QuickBooks Desktop file. Products are QuickBooks inventory items; service and non-inventory items are not included. Search with name_contains, look up exact item_ids, or browse. Stock quantities are as QuickBooks reports them, and a missing quantity is unknown, not zero. Returns one page; pass next_cursor back with the same other inputs for the next page.
list_invoices
ChatGPTList invoices from the company's QuickBooks Desktop file. Use invoice_ids for exact QuickBooks IDs, or filter by customer_ids (from list_customers), invoice_numbers, and a transaction date range; at least one filter is required. payment_status is all (the default), paid, or not_paid. Each invoice shows what is still owed (balance_remaining) and the payments and credits applied to it; lines are included unless include_line_items is false. Returns one page; one page is not a company total. Pass next_cursor back with the same other inputs for the next page.
list_logistify_sales_orders
ChatGPTList sales orders saved in Logistify and whether each one is in QuickBooks yet. With order_numbers (Logistify order numbers, not QuickBooks ones), those orders are shown whatever their state; use this to check on a push. Without them, the newest open orders not yet sent to QuickBooks are listed. quickbooks_status is in_quickbooks, not_sent, last_push_failed, or in_another_system. needs_review lists reviews a person must finish in Logistify before the order can be sent. This reads Logistify, not QuickBooks.
list_payment_matches
ChatGPTList bank payments that Logistify matched to open invoices and that a person could approve, newest first. Each shows the amount, payer, customer, the invoices it would pay, and its status: ready_to_approve, waiting_for_a_person (with the reason, such as a short payment), or approved_waiting_to_record. This reads Logistify, not QuickBooks.
list_purchase_orders
ChatGPTList purchase orders from the company's QuickBooks Desktop file for one or more vendors (vendor_ids from list_vendors), for specific order_numbers, or both; at least one is required. Lines, with received quantities, are included unless include_line_items is false. open_state is open, closed, or unknown; unknown means QuickBooks did not report it, never that the order is open. With open_only, only orders known to be open are kept, so a page can be short while next_cursor still leads to more. Pass next_cursor back with the same other inputs for the next page.
list_quickbooks_connections
ChatGPTList the company's QuickBooks Desktop files that this person can read, with their connection_id values. Use it when another tool says the company has more than one file, then ask the person which one they mean. A listed file is set up in Logistify; that does not prove QuickBooks is open right now.
list_received_payments
ChatGPTList payments customers made, as recorded in the company's QuickBooks Desktop file, with the invoices each one paid. Use payment_ids for exact QuickBooks IDs, or filter by customer_ids, reference_numbers (the payment's reference number), and a transaction date range; at least one filter is required. Card details are never included. Returns one page; pass next_cursor back with the same other inputs for the next page.
list_sales_orders
ChatGPTList sales orders from the company's QuickBooks Desktop file for one or more customers (customer_ids from list_customers), for specific order_numbers, or both; at least one is required. Order lines are included unless include_line_items is false. Status flags are exactly as QuickBooks reports them; a missing flag does not mean an order is complete. Returns one page; pass next_cursor back with the same other inputs for the next page.
list_vendors
ChatGPTFind vendors in the company's QuickBooks Desktop file. QuickBooks calls suppliers vendors. When the person names a supplier, search with name_contains and let them choose if several match. Use vendor_ids for exact QuickBooks IDs, or neither to browse active vendors. Contact details are not included. Returns one page; pass next_cursor back with the same other inputs for the next page.
push_sales_order_to_quickbooks
ChatGPTSend one Logistify sales order to the company's QuickBooks Desktop file as a new sales order, the same as the Push button on Logistify's Sales Orders screen. Find the order with list_logistify_sales_orders first, and confirm its number, customer, and total with the person before you call this. Logistify refuses an order that is already in QuickBooks, still needs a review, or has a customer or product not linked to QuickBooks, and says why. The push is queued, not finished: check it a minute later with list_logistify_sales_orders and this order number. This needs the person to have allowed changes when they connected Logistify.