[Syncro] Search customers for autocomplete UI. Use for quick name-based lookup. Returns a slimmer, faster payload than syncro_list_customers when you only need IDs and display names.

[Syncro] Create a new customer. Provide either business_name (for a company customer) OR both firstname and lastname (for an individual). Additional fields (email, phone, mobile, address, city, state, zip, notes, tax_rate_id, properties) can be supplied via fieldsJson. Returns the created customer with its assigned ID.

[Syncro] Permanently delete a customer by ID. This action cannot be undone and may cascade to related records (contacts, tickets, invoices). Consider updating the customer or marking it disabled instead. Requires a valid customer ID.

[Syncro] Retrieve full customer details by ID. Returns the complete customer record including business info, address, email, phone numbers, notes, and custom properties.

[Syncro] Return the most recently created customer. Useful for confirming a just-created customer or auditing new customer intake.

[Syncro] List customers with optional filters (query, firstname, lastname, business_name, email, include_disabled). Returns paginated list. Use to find customer IDs for tickets, invoices, assets.

[Syncro] Update customer fields by ID. Supply any updatable fields via fieldsJson (business_name, firstname, lastname, email, phone, mobile, address, city, state, zip, notes, tax_rate_id, properties, etc.). Use syncro_get_customer to check current values before updating.

[Syncro] Create a new contact attached to an existing customer. customer_id is required. Provide name, email, phone, and mobile inline or supply additional fields (address1, address2, city, state, zip, notes) via fieldsJson. Returns the created contact with its assigned ID.

[Syncro] Permanently delete a contact by ID. This action cannot be undone. Requires a valid contact ID.

[Syncro] Retrieve full contact details by ID. Returns the complete contact record including name, email, phone numbers, address fields, and notes.

[Syncro] List contacts with optional customer_id filter. Returns paginated list. Use to find contact IDs associated with a customer, or to enumerate all contacts across the tenant.

[Syncro] Update contact fields by ID. Supply any updatable fields (name, email, phone, mobile, address1, city, state, zip, notes, etc.) via fieldsJson. Use syncro_get_contact to check current values before updating.

[Syncro] Add a phone number to a customer. Provide label (e.g. 'Main', 'Mobile', 'Fax'), number, and optional extension. Additional fields may be supplied via fieldsJson. Returns the created phone record with its assigned ID.

[Syncro] Permanently delete a phone number from a customer. This action cannot be undone. Use syncro_list_customer_phones to find the phone ID first.

[Syncro] List all phone numbers for a customer. Returns each phone's ID, label (e.g. 'Main', 'Mobile', 'Fax'), number, and extension. Use to discover phone IDs before updating or deleting.

[Syncro] Update an existing phone number for a customer. Provide label, number, extension inline or supply additional fields via fieldsJson. Use syncro_list_customer_phones to find the phone ID first.

[Syncro] Add a payment profile (stored card reference) to a customer. Typically takes an external_id plus the processor's payment_profile_id, expiration, and last_four. Additional fields may be supplied via fieldsJson. Returns the created payment profile with its assigned ID.

[Syncro] Permanently delete a payment profile from a customer. This action cannot be undone. Requires both the customer ID and the payment profile ID.

[Syncro] Retrieve a specific payment profile by ID. Returns the full payment profile record (external_id, payment_profile_id, expiration, last_four, card metadata). Requires both the customer ID and the payment profile ID.

[Syncro] List payment profiles (stored cards) for a customer. Returns each profile's ID, external_id, payment_profile_id, last_four, and expiration. Use to discover payment profile IDs before charging an invoice or updating a stored card.

[Syncro] Update an existing payment profile for a customer. Supply any updatable fields (external_id, payment_profile_id, expiration, last_four, card_type, default, etc.) via fieldsJson. Use syncro_get_payment_profile to check current values before updating.

[Syncro] Add a new comment to a ticket. Requires subject and body. Set hidden=true to make the comment internal-only (not visible to customers). Set doNotEmail=true to suppress the customer email notification.

[Syncro] Add a line item (product, service, or labor) to a ticket. Pass fieldsJson with the line item properties. Typical fields: product_id (int), quantity (number), price (number), name (string), cost (number), taxable (bool).

[Syncro] Add a timer entry (time log) to a ticket. Supply either start_at + end_at to mark a time range, or duration_minutes for a flat logged duration. Use productId to bill the time as a specific labor product.

[Syncro] Attach one or more files to a ticket by URL. Syncro fetches files asynchronously from the URLs you provide. URLs must be publicly accessible (signed S3 URLs, public CDN, etc.). Expect 'Processing' response; re-fetch the ticket with syncro_get_ticket to confirm attachment.

[Syncro] Mark a timer entry as charged / converted to a billable line item on the ticket. This is a billing action and may create a ticket line item depending on account configuration. Requires ticket ID and the timer entry ID.

[Syncro] Create a new ticket. Requires customer ID and subject. Use syncro_get_ticket_settings to discover valid values for status, priority, problemType, ticketTypeId, and slaId. Returns the created ticket with its assigned ID.

[Syncro] Permanently delete a ticket and all associated comments, line items, and timer entries. This action cannot be undone. Requires a valid ticket ID.

[Syncro] Delete an attachment from a ticket. This action cannot be undone. Requires ticket ID and the attachment ID.

[Syncro] Delete a timer entry from a ticket. This action cannot be undone. Requires ticket ID and the timer entry ID.

[Syncro] Retrieve full details for a single ticket by ID. Returns the ticket with all comments, line items, timer entries, and custom fields. Requires a valid ticket ID -- use syncro_list_tickets to find IDs.

[Syncro] Retrieve the account-wide ticket configuration: ticket types, statuses, problem types, priorities, SLAs, and custom field definitions. Use this to discover valid values for syncro_create_ticket and syncro_update_ticket parameters.

[Syncro] List comments on a single ticket, paginated. This is the recommended way to retrieve ticket comments -- it is faster than fetching the full ticket with allComments=true and supports per_page sizing (unique among Syncro endpoints). Default 10 per page, max 100.

[Syncro] List tickets with optional filters and pagination. Returns ticket summaries including ID, number, subject, status, customer, and assigned user. Use this to discover ticket IDs or browse the ticket queue. For per-ticket comments, prefer syncro_list_ticket_comments (paginated, faster than allComments=true).

[Syncro] Queue a print job for a ticket. This generates a printable ticket document via Syncro's print pipeline. Requires a valid ticket ID.

[Syncro] Remove a line item from a ticket. This action cannot be undone. Requires ticket ID and the ticket line item ID.

[Syncro] Update an existing ticket's fields such as subject, status, priority, assigned user, or custom fields. Returns the updated ticket. Use syncro_get_ticket to check current values before updating.

[Syncro] Update an existing line item on a ticket. The fieldsJson body must include ticket_line_item_id identifying the line item to update, plus any fields to change (quantity, price, name, etc.).

[Syncro] Update an existing timer entry on a ticket. The fieldsJson body must include the timer_entry_id plus any fields to change (start_at, end_at, duration_minutes, notes, etc.).

[Syncro] List standalone ticket timer entries across all tickets with pagination. Returns timer entries including ID, ticket association, user, duration, and billable flag. Use createdAtLt to page backwards through history. For timers on a specific ticket, prefer syncro_get_ticket.

[Syncro] Toggle the billable flag on a ticket timer entry. Set billable=true to mark time as billable to the customer, or false to mark it as non-billable / internal. Returns the updated timer entry.

[Syncro] Attach a new worksheet result (instance of a worksheet template) to a ticket. Requires worksheetTemplateId and title. Optional fieldsJson can include complete (bool) and answers (array/object) to pre-populate the worksheet.

[Syncro] Permanently delete a worksheet result from a ticket. This action cannot be undone. Requires valid ticket and worksheet result IDs.

[Syncro] Retrieve a single worksheet result by ticket ID and worksheet result ID. Returns the full worksheet including template info, title, completion status, and all answers. Requires valid ticket and worksheet result IDs.

[Syncro] List worksheet results (filled-out checklists/templates) for a specific ticket. Returns worksheet results including ID, template, title, completion status, and answers. Requires a valid ticket ID.

[Syncro] Update an existing worksheet result on a ticket. Pass fieldsJson with any fields to change. Typical fields: title (string), complete (bool), answers (array or object of template question answers).

[Syncro] Add a single line item to an existing invoice. At minimum supply a name (or a product_id to copy pricing from the product catalog). Quantity defaults to 1 on Syncro's side if omitted. Use fieldsJson for additional fields (taxable flag overrides, sku, position, custom properties, etc.). Returns the updated invoice including the new line item and its ID, which you can reuse with syncro_update_invoice_line_item.

[Syncro] Create a new invoice for a customer. Requires customer_id, invoice number, and invoice date. Additional fields (due_date, ticket_id, billing/shipping address overrides, tax_rate_id, comment, `line_items` array, etc.) can be supplied via fieldsJson. Returns the created invoice with its assigned ID. Use syncro_list_customers to find customerId; use syncro_add_invoice_line_item afterward to add line items if not supplied here.

[Syncro] Permanently delete an invoice by ID. This action cannot be undone and may affect ledgers and paid/balance reports. Prefer voiding through a syncro_update_invoice call when possible. Requires a valid invoice ID.

[Syncro] Permanently remove a line item from an invoice. This action cannot be undone and will update the invoice totals. Requires both invoice ID and line item ID. Use syncro_get_invoice to find line item IDs.

[Syncro] Email an invoice to the customer at the email address on file. Uses the tenant's configured invoice email template. Verify the customer has a valid email (see syncro_get_customer) before calling -- sending to a missing/invalid address will fail in Syncro.

[Syncro] Retrieve a single invoice by ID with full details including line items, tax breakdown, balance due, billing/shipping addresses, and status. Use syncro_list_invoices to discover invoice IDs.

[Syncro] Return the ticket associated with a given invoice. Useful for reconciling billing against labor/services tracked on the ticket (comments, timer entries, charged line items). Not all invoices have an associated ticket -- invoices created directly (POS, standalone) may return an empty response.

[Syncro] List invoices with optional filters for paid/unpaid status, associated ticket, and last-updated timestamp. Returns a paginated collection of invoice summaries including ID, number, customer, totals, and payment status. Use this to discover invoice IDs before calling syncro_get_invoice, syncro_update_invoice, or payment tools. Combine `paid=false` (or `unpaid=true`) with `sinceUpdatedAt` to pull only recently changed open invoices for syncs.

[Syncro] List line items globally across all invoices and estimates. Requires Global Admin permission on the Syncro account -- standard API users will receive a 403. Filter by `invoiceId` or `estimateId` to scope to a specific document, or use `invoiceIdNotNull` / `estimateIdNotNull` to return only line items attached to any invoice or any estimate respectively. Useful for revenue reporting and reconciliation.

[Syncro] Queue an invoice for printing via the configured Syncro print job workflow. Returns the print job confirmation. Use this when the tenant has a print-to-PDF or physical print pipeline set up in Syncro.

[Syncro] Update fields on an existing invoice. Supply any updatable fields via fieldsJson (due_date, date, number, comment, billing/shipping address, tax_rate_id, etc.). Use syncro_get_invoice to check current values before updating. To change individual line items use syncro_update_invoice_line_item.

[Syncro] Update a single line item on an existing invoice by its line item ID. Supply any updatable fields via fieldsJson (name, quantity, cost, price, discount_percent, taxable, sku, position, properties, etc.). Use syncro_get_invoice to list current line items and their IDs.

[Syncro] Add a single line item to an existing estimate. At minimum supply a name (or a product_id to copy pricing from the product catalog). Quantity defaults to 1 on Syncro's side if omitted. Use fieldsJson for additional fields (taxable flag overrides, sku, position, custom properties, etc.). Returns the updated estimate including the new line item and its ID, which you can reuse with syncro_update_estimate_line_item.

[Syncro] Convert an approved estimate into a real invoice, copying all line items and customer info. Returns the new invoice. This is a high-value action: the generated invoice becomes billable immediately in Syncro. Upstream permission gating requires BOTH `edit:estimates` AND `edit:invoices` -- ensure the caller holds both before using. Once converted, the estimate status moves to 'converted' and cannot be edited further. Use syncro_get_estimate to verify line items and totals beforehand.

[Syncro] Create a new estimate (quote) for a customer. Requires customer_id. Additional fields (date, expires_at, number, comment, `line_items` array, etc.) can be supplied via fieldsJson. Returns the created estimate with its assigned ID. Use syncro_list_customers to find customerId; use syncro_add_estimate_line_item afterward to add line items if not supplied here.

[Syncro] Permanently delete an estimate by ID. This action cannot be undone. Consider marking the estimate declined via syncro_update_estimate instead to preserve the audit trail. Requires a valid estimate ID.

[Syncro] Permanently remove a line item from an estimate. This action cannot be undone and will update the estimate totals. Requires both estimate ID and line item ID. Use syncro_get_estimate to find line item IDs.

[Syncro] Email an estimate to the customer at the email address on file. Uses the tenant's configured estimate email template. Verify the customer has a valid email (see syncro_get_customer) before calling -- sending to a missing/invalid address will fail in Syncro.

[Syncro] Retrieve a single estimate by ID with full details including line items, pricing, status, and customer info. Use syncro_list_estimates to discover estimate IDs.

[Syncro] List estimates (quotes) with pagination and optional filters. Returns a paginated collection of estimate summaries including ID, number, customer, totals, and status (open/approved/converted/declined). Use this to find estimate IDs before calling syncro_get_estimate, syncro_update_estimate, or syncro_convert_estimate_to_invoice.

[Syncro] Queue an estimate for printing via the configured Syncro print job workflow. Returns the print job confirmation. Use this when the tenant has a print-to-PDF or physical print pipeline set up in Syncro.

[Syncro] Update fields on an existing estimate. Supply any updatable fields via fieldsJson (number, date, expires_at, status, comment, etc.). Use syncro_get_estimate to check current values before updating. To change individual line items use syncro_update_estimate_line_item.

[Syncro] Update a single line item on an existing estimate by its line item ID. Supply any updatable fields via fieldsJson (name, quantity, cost, price, discount_percent, taxable, sku, position, properties, etc.). Use syncro_get_estimate to list current line items and their IDs.

[Syncro] Record a new payment from a customer. Requires customer_id, amount_cents (integer CENTS -- e.g. 11000 for $110.00), and payment_method. Optionally link the payment to a single invoice (invoice_id or invoice_number), supply a reference number (ref_num), or split across multiple invoices via applyPayments. IMPORTANT: Syncro's API is inconsistent about units between the two amount fields -- amount_cents is an integer in cents, but apply_payments values are per-invoice DOLLAR AMOUNTS as STRINGS with two decimal places (e.g. "48.00"). The sum of apply_payments values must equal amount_cents / 100 (expressed in dollars). Extra fields go through fieldsJson. Use syncro_list_payment_methods to discover valid payment_method strings.

[Syncro] Retrieve a single payment record by ID including amount, method, reference number, customer, and the invoices the payment was applied to. Use syncro_list_payments to discover payment IDs.

[Syncro] List the payment methods configured on the tenant's Syncro account (e.g. 'Cash', 'Check', 'Credit Card', custom methods). Not paginated -- returns the full set in a single call. Use before syncro_create_payment to ensure the payment_method string matches a valid value.

[Syncro] List payments with pagination and an optional free-text query. Returns a paginated collection of payment records including ID, customer, amount, payment method, associated invoices, and timestamps. Use this to reconcile payments against invoices or find payment IDs for syncro_get_payment.

[Syncro] Create a new contract for a customer. Requires customer_id. Optional scalar fields cover the common contract attributes; use fieldsJson for any additional fields supported by the Syncro API. Use syncro_list_customers to find customerId.

[Syncro] Permanently delete a contract by ID. This action cannot be undone and will unlink the contract from any assets/tickets that referenced it. Consider marking the contract expired via syncro_update_contract to preserve the audit trail. Requires a valid contract ID.

[Syncro] Retrieve a single contract by ID with full details including customer, amount, description, date range, status, associated SLA, and which assets or tickets the contract applies to. Use syncro_list_contracts to discover contract IDs.

[Syncro] List customer contracts (managed-service agreements, prepaid blocks, SLA agreements) with pagination. Returns a paginated collection of contract summaries including ID, customer, name, amount, status, and date range. Use this to find contract IDs for syncro_get_contract, syncro_update_contract, or syncro_delete_contract.

[Syncro] Update fields on an existing contract. Supply any updatable fields via fieldsJson (name, description, contract_amount, start_date, end_date, status, sla_id, etc.). Use syncro_get_contract to check current values before updating.

[Syncro] Add a line item to an existing recurring invoice schedule. Pass the line item payload as JSON via fieldsJson (product_id, quantity, price, name, taxable, etc.). The line item will be included on every future invoice generated from this schedule.

[Syncro] Create a new recurring invoice schedule. Required: customerId, frequency, name, nextRun (ISO date). Optional flags control email delivery, snail mail, charge-on-file (chargeMop), automatic ticket charge invoicing, and paused state. After creation, use syncro_add_schedule_line_item to add billable items.

[Syncro] Permanently delete a recurring invoice schedule and all its line items. This action cannot be undone. If you only want to stop generating invoices temporarily, prefer syncro_update_schedule with paused=true.

[Syncro] Retrieve full details of a single recurring invoice schedule by ID, including customer, frequency, next run date, delivery options, paused state, and line items. Use syncro_list_schedules to find schedule IDs.

[Syncro] List recurring invoice schedules with optional customer filter. Schedules define automated recurring billing (frequency, next run date, line items, delivery options). Returns paginated results. Use to discover schedule IDs for updates, pauses, or line item management.

[Syncro] Remove a line item from a recurring invoice schedule. The line item will no longer appear on future invoices generated from this schedule. This action cannot be undone (you would need to re-add the line item to restore it).

[Syncro] Update a recurring invoice schedule's fields (name, frequency, next_run, email_customer, snail_mail, charge_mop, paused, invoice_unbilled_ticket_charges, notes, etc.). Use syncro_get_schedule to check current values before updating. To change line items, use the schedule line item tools.

[Syncro] Update fields on an existing schedule line item (quantity, price, name, taxable, product_id, etc.). Use syncro_get_schedule to find the line item ID and its current values before updating.

[Syncro] Attach one or more images to a product via publicly reachable URLs. Syncro downloads each URL asynchronously on its side -- the response returns immediately, before the images are fully ingested. Re-read the product with syncro_get_product after a short delay to confirm the images appear. No direct file upload is supported by this endpoint.

[Syncro] Create a new product in the catalog. Required: name and description. Common optional fields are exposed as parameters (priceCost, priceRetail, maintainStock, quantity, taxable, upcCode); supply anything else (category_id, notes, custom properties, location stock, etc.) via fieldsJson.

[Syncro] Permanently delete a single image from a product. Requires both the product ID and the image (photo) ID. This action cannot be undone; the image file will no longer be retrievable. Use syncro_get_product to find photo IDs.

[Syncro] Retrieve full details for a single product by ID, including pricing (cost + retail), stock levels across locations, images, custom properties, and tax settings. Use syncro_list_products to find product IDs.

[Syncro] Look up a product by its barcode (UPC/EAN/custom). Useful for point-of-sale, receiving, and inventory workflows where a scanner provides the barcode. Returns the matching product if found.

[Syncro] List part orders (parts ordered to fulfill specific tickets). Filter by completion state or free-text query. Useful for tracking outstanding customer-specific parts and closing the loop between repair tickets and inventory receiving.

[Syncro] List all product categories. Returns paginated category records with IDs and names. Use category IDs to filter syncro_list_products or to assign a category when creating/updating products.

[Syncro] List products in the catalog with optional filters (sku, name, upc_code, category_id, free-text query). Returns paginated product summaries including ID, name, pricing, and stock. Use to discover product IDs for invoices, estimates, recurring invoices, and purchase orders.

[Syncro] Update fields on an existing product (name, description, price_cost, price_retail, taxable, upc_code, category_id, properties, etc.). Use syncro_get_product to inspect current values first. Stock adjustments go through syncro_update_product_location_quantity, not this tool.

[Syncro] Adjust the on-hand quantity of a product at a specific location (inventory adjustment). Supply location_id and the new quantity via fieldsJson. Use this for cycle counts, damage write-offs, or manual stock corrections -- not for sales or receiving, which post automatically through invoices and purchase orders.

[Syncro] Attach one or more serial numbers to an invoice line item or ticket line item, recording which physical units were sold or assigned. Required: recordType ('LineItem' for invoice line items or 'TicketLineItem' for ticket line items), recordId, and the array of serial IDs to attach.

[Syncro] Create a new serial number record for a product. Typical fields: serial (the serial number string), notes, location_id. Use for receiving new serialized stock or back-filling serial history.

[Syncro] List serial numbers tracked for a specific product. Returns paginated serial records including their current status (in-stock, sold, returned). Use for products that track individual units by serial (e.g. laptops, switches, licenses).

[Syncro] Update fields on an existing product serial (serial string, notes, location_id, etc.). Use syncro_list_product_serials to find the serial ID first. Does not move the serial between customers -- use syncro_attach_product_serials_to_line_item for sale/assignment.

[Syncro] Add an alternate SKU to a product. Useful for mapping vendor part numbers or manufacturer codes to an internal catalog item so scans and lookups against any of them resolve to the same product.

[Syncro] List alternate SKUs registered for a product. A product can have multiple SKUs (e.g. vendor part number, manufacturer code, internal code) that all resolve to the same catalog item. Returns paginated SKU records.

[Syncro] Update fields on an existing product SKU (code, notes, etc.). Use syncro_list_product_skus to find the SKU ID first. To remove a SKU entirely, use the underlying API directly -- this connector does not yet expose a delete operation.

[Syncro] Add a line item to an existing purchase order. productId is required — use syncro_list_products to find valid product IDs. Optional quantity and cost (unit cost in cents) default to product defaults if omitted. Use fieldsJson for any additional line-item attributes.

[Syncro] Create a new purchase order for a vendor. vendorId is required. Optional fields include expected delivery date, shipping (in cents), discount percent, general notes, due/order dates, and delivery tracking info. Use fieldsJson for any additional PO attributes. Returns the created PO with its assigned ID.

[Syncro] Retrieve full purchase order details by ID. Returns the complete PO record including vendor, line items, totals, expected/order/due dates, shipping, discount, and notes.

[Syncro] List purchase orders with pagination. Returns summaries including ID, vendor, status, totals, and key dates. Use to find purchase order IDs for receive or line-item operations.

[Syncro] Mark a purchase order as received and update inventory quantities. This is an inventory action — receiving increments product stock based on the PO's line items. Supply receive-specific details (e.g. received quantities per line item, received date, serial numbers, notes) via fieldsJson. Use syncro_get_purchase_order first to view the PO's current line items and remaining quantities.

[Syncro] Create a new vendor. name is required. Optional fields include rep first/last name, email, phone, account number, and address (address1, address2, city, state, zip). Use fieldsJson for any additional vendor attributes. Returns the created vendor with its assigned ID.

[Syncro] Retrieve full vendor details by ID. Returns the complete vendor record including name, rep contact, email, phone, account number, address, and custom properties.

[Syncro] List vendors with pagination. Returns summaries including ID, name, rep contact, and address. Use to find vendor IDs for purchase orders and product sourcing.

[Syncro] Update vendor fields by ID. Supply any updatable fields (name, rep_firstname, rep_lastname, email, phone, account_number, address_1, city, state, zip, etc.) via fieldsJson. Use syncro_get_vendor to check current values before updating.

[Syncro] Create a new customer asset (non-RMM — RMM agents register themselves automatically when installed). Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. name is required. Optional fields include customer ID, asset type (by ID or name), serial number, and arbitrary properties. Use fieldsJson for any additional attributes.

[Syncro] Retrieve Windows Update patch data for an RMM-managed customer asset. Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. Returns Windows Update patch data — both installed_patches and available_patches arrays with status fields (Missing/Failed/Rejected/Recently Installed). Use this to audit patch compliance on a specific endpoint.

[Syncro] Fetch chat information (Syncro Live Chat agent availability and session state) for one or more customer assets in a single call. Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. Useful for checking which endpoints are available for a live chat session before initiating one.

[Syncro] Retrieve full customer asset details by ID, including RMM data for agent-managed devices. Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. Returns the complete asset record — name, type, serial, customer, properties, and (for RMM-managed assets) OS info, hardware specs, online/offline status, and last checkin time.

[Syncro] List customer assets (RMM-managed devices and other tracked assets) with optional filters. Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. Use filters to narrow by customer, asset type, name/serial query, or SNMP capability. Returns paginated summaries including asset ID, name, type, customer, and basic RMM status.

[Syncro] Update customer asset fields by ID. Syncro's /customer_assets endpoint exposes RMM data for agent-managed devices. Supply any updatable fields (name, asset_type_id, asset_serial, properties, etc.) via fieldsJson. Use syncro_get_customer_asset to check current values before updating.

[Syncro] Create a new RMM alert for a customer asset. customerId, assetId, and description are all required. Optional resolved flag, status string, and propertiesJson (arbitrary alert metadata). Use to record custom alert conditions detected by external monitoring.

[Syncro] Clears (deletes) an RMM alert by ID. Destructive — this action cannot be undone. Prefer muting when you only need to suppress notifications temporarily.

[Syncro] Retrieve full RMM alert details by ID. Returns the complete alert record including customer, asset, description, status, properties, and timestamps.

[Syncro] List RMM alerts with optional status filter. Returns paginated alert summaries including ID, customer, asset, description, status, and timestamps. Use to triage active RMM alerts or audit resolved ones.

[Syncro] Suppresses notifications for this alert for the specified duration. Use 'forever' to mute permanently (must be manually unmuted). Valid durations: '1-hour', '1-day', '2-days', '1-week', '2-weeks', '1-month', 'forever'.

[Syncro] Create a new appointment. Requires summary, startAt, and endAt. Optional customer/ticket links, location, all-day flag, and notification suppression can be supplied. Returns the created appointment with its assigned ID.

[Syncro] Permanently delete an appointment by ID. This action cannot be undone. Requires a valid appointment ID. Use syncro_list_appointments to find valid IDs.

[Syncro] Retrieve full details for a single appointment by ID. Returns the complete appointment record including summary, times, customer, ticket, location, and attendees. Use syncro_list_appointments to discover valid IDs.

[Syncro] List appointments with optional date-range filters and pagination. Use this to find upcoming or past appointments for scheduling, audits, or calendar integration. Use syncro_get_appointment for full details on a single appointment.

[Syncro] Update appointment fields by ID. Supply any updatable fields via fieldsJson (summary, start_at, end_at, description, customer_id, ticket_id, location, all_day, do_not_email, etc.). Date fields use ISO 8601 format (e.g. '2026-04-22T10:00:00Z'). Use syncro_get_appointment to check current values before updating.

[Syncro] Create a new appointment type. Requires name. Optional email instructions and location configuration can be supplied. Returns the created appointment type with its assigned ID. Requires Global Admin permission.

[Syncro] Permanently delete an appointment type by ID. This action cannot be undone and may affect existing appointments that reference this type. Requires a valid appointment type ID. Requires Global Admin permission.

[Syncro] Retrieve full details for a single appointment type by ID. Returns the complete record including name, email instructions, location configuration, and any custom fields.

[Syncro] List all configured appointment types with pagination. Appointment types define the shape of appointments (default duration, location, email instructions). Use this to discover valid appointment_type_id values when creating appointments.

[Syncro] Update appointment type fields by ID. Supply any updatable fields via fieldsJson (name, email_instructions, location_type, location_hard_code, etc.). Use syncro_get_appointment_type to check current values before updating. Requires Global Admin permission.

[Syncro] Create a new lead. All fields are optional -- supply whatever contact info is available (name, business, email, phone, mobile) plus optional ticket subject/description to kick off a new intake. Returns the created lead with its assigned ID.

[Syncro] Retrieve full details for a single lead by ID. Returns the complete lead record including contact info, status, assigned user, and ticket linkage.

[Syncro] List leads with optional status and keyword filters. Returns paginated list of prospective customers captured in the CRM. Use to triage intake or find lead IDs for follow-up.

[Syncro] Update lead fields by ID. Supply any updatable fields via fieldsJson (first_name, last_name, business_name, email, phone, mobile, ticket_subject, ticket_description, status, user_id, etc.). Use syncro_get_lead to check current values before updating.

[Syncro] Retrieve full details for a single new-ticket form by ID, including the configured customer fields, ticket fields, and appointment fields. Use this to discover the exact field names to include in the body of syncro_process_new_ticket_form.

[Syncro] List all configured new-ticket intake forms with pagination. These forms define the fields presented to end-users and techs when creating a new ticket. Use this to discover valid form IDs before calling syncro_process_new_ticket_form.

[Syncro] Use this to submit a new-ticket intake form that creates a customer (if needed) and ticket in one call. The body takes nested customer_details, ticket_details, and appointments objects matching the form's configured fields -- inspect the form shape via syncro_get_new_ticket_form first. Returns the created customer/ticket payload.

[Syncro] Create a new wiki page with the provided name and body content. Optionally attach to a customer or asset and control visibility. Returns the created wiki page with its assigned ID.

[Syncro] Permanently delete a wiki page by ID. This action cannot be undone. Requires a valid wiki page ID.

[Syncro] Retrieve a single wiki page by ID, including the full body/content, slug, visibility, attached customer/asset, and metadata. Use syncro_list_wiki_pages to find valid IDs.

[Syncro] List wiki pages (internal documentation/knowledge base). Returns a paginated list including id, name, slug, visibility, and metadata. Use to discover wiki page IDs before fetching full content with syncro_get_wiki_page.

[Syncro] Update an existing wiki page by ID. Supply any updatable fields (name, body, slug, visibility, customer_id, asset_id, tag_list, etc.) via fieldsJson. Use syncro_get_wiki_page to inspect current values before updating.

[Syncro] Create a new canned response template. title and body are required. Optionally attach a default subject line and canned response category. Returns the created record with its ID.

[Syncro] Permanently delete a canned response by ID. This action cannot be undone. Requires a valid canned response ID.

[Syncro] List canned responses (pre-written reply templates used on tickets). Supports optional free-text search. Returns id, title, subject, body, category, and metadata.

[Syncro] Update an existing canned response by ID via PATCH. Supply any updatable fields (title, body, subject, canned_response_category_id, etc.) via fieldsJson. Use syncro_list_canned_responses to find IDs.

[Syncro] Retrieve information about the user backing the current API token (the `/me` endpoint). Returns the user profile plus a permissions map with boolean capabilities for asset, customer, ticket, invoice, payment, worksheet, and script. Use this first to detect what actions the configured token is actually allowed to perform before attempting privileged operations.

[Syncro] Retrieve full details for a single internal user by ID, including email, role, and profile fields. Use syncro_list_users to find valid IDs (note that the list endpoint returns [id, full_name] tuples).

[Syncro] List internal Syncro users (technicians/staff, NOT portal/customer users). IMPORTANT QUIRK: this endpoint returns a non-standard shape `{users: [[id, full_name], [id, full_name], ...]}` where each user is a two-element ARRAY (tuple) of [id, full_name] rather than an object with named fields. To get full user details use syncro_get_user with one of the returned IDs.

[Syncro] Create a new portal user (customer-facing client portal login). contact_id, customer_id, email, and password are required. Optionally provide password_confirmation and a portal_group_id. Requires Global Admin permission on the API token.

[Syncro] Permanently delete a portal user by ID, revoking their ability to sign into the client portal. This action cannot be undone. Requires Global Admin permission on the API token.

[Syncro] Send an invitation email to an existing portal user. The request body is simply {"id": <portal_user_id>}. Requires Global Admin permission on the API token. Use syncro_list_portal_users to find the portal user ID.

[Syncro] List portal users (customer-facing logins for the client portal, NOT internal Syncro staff). Supports optional customer_id and email filters. Requires Global Admin permission on the API token.

[Syncro] Update an existing portal user by ID. Supply any updatable fields (email, password, password_confirmation, contact_id, portal_group_id, etc.) via fieldsJson. Requires Global Admin permission on the API token.