MCP/API Feedback

Ability for the MCP/API to create, modify, and delete recurring visits.

as part of the request for scheduling recuring visits, it should also be able to create the level billing and tie the recuring series to it

Right now the Calls/Notes log on a customer record (calls notes, follow ups with author and date) isn’t available through the GraphQL API. We can read and write customer description and job dispatch notes, but not this log. Request: add API support to 1. Read existing call notes for a customer for AI context. 2. Add a new call note entry for history for command centre (say emailing externally) This would let us log customer interactions and other communications (like emails handled outside the CRM) automatically instead of manual entry, so reps always have a full accurate history in one place.

Details: Homeworks currently exposes visit media through the MCP/API, including the media ID, filename, content type, thumbnail URL, and file URL. However, connected AI agents such as ChatGPT cannot directly retrieve the underlying image or video file for visual analysis. Use case: our field technicians upload photos and videos to customer visits. I want the connected AI agent to be able to review those files directly from the visit, analyze job-site conditions, compare before/after photos, review completed work, identify potential damage or quality issues, and analyze videos without having to manually download each file from Homeworks and upload it into ChatGPT. Requested capability: expose visit media as a downloadable MCP resource/file, authenticated binary download action, or another mechanism that allows the connected AI client to ingest the actual photo/video file rather than only receiving its URL and metadata. The existing event.media and beforeAndAfters media data already exposes the records, so the missing piece appears to be authenticated file retrieval through MCP. This would make field photos and videos significantly more useful for QA, estimating, damage review, job documentation, and AI-assisted field operations.

Currently we can move an event but not its future events in the recurring series. This will make bulk moving events forward a week (like during a Christmas week off) a lot easier and faster, rather then having to move each event one by one.

currently the MCP/API can create proposals but it can not assign budgeted hours onto them. AI using browser control to add the budgeted hours after after the fact is less reliable & is causing errors in the process

Allow mcp / api agents to review and approve/send or reject upsells that have been submitted to the upsell section for review.

This would be useful for phone agents to understand things like service areas, service offered, and other granular systems for that specific location.