Notes & Attachments
Ticket Notes
Section titled “Ticket Notes”Search notes on a ticket
Section titled “Search notes on a ticket”Prompt:
“Show me the notes on ticket 48231”
What happens: The server calls autotask_search_ticket_notes with ticketId: 48231.
Expected output:
{ "summary": "Found 3 ticket notes (showing 1-3)", "items": [ { "id": 55001, "title": "Initial Contact", "description": "Called the client to confirm the issue. Email server shows high CPU usage.", "noteType": 1, "createDateTime": "2024-01-15T09:45:00Z", "creatorResourceID": 12345, "_enhanced": { "creatorName": "John Smith" } }, { "id": 55002, "title": "Vendor Escalation", "description": "Opened case #12345 with the email hosting vendor. ETA 2 hours.", "noteType": 1, "createDateTime": "2024-01-15T11:00:00Z", "creatorResourceID": 12345, "_enhanced": { "creatorName": "John Smith" } } ], "total": 3}Add a note to a ticket
Section titled “Add a note to a ticket”Prompt:
“Add a note to ticket 48231 titled ‘Resolution’ with description ‘Restarted the email service. Issue resolved. Monitoring for recurrence.’”
What happens: The server calls autotask_create_ticket_note with ticketId: 48231, title: "Resolution", and description: "Restarted the email service. Issue resolved. Monitoring for recurrence.".
Expected output:
{ "message": "Created ticket note with ID: 55003", "data": 55003}Get a specific note
Section titled “Get a specific note”Prompt:
“Get note 55001 from ticket 48231”
What happens: The server calls autotask_get_ticket_note with ticketId: 48231 and noteId: 55001.
Project Notes
Section titled “Project Notes”Search project notes
Section titled “Search project notes”Prompt:
“Show notes for project 5021”
What happens: The server calls autotask_search_project_notes with projectId: 5021.
Expected output:
{ "summary": "Found 2 project notes (showing 1-2)", "items": [ { "id": 56001, "title": "Kickoff Meeting Notes", "description": "Discussed timeline, resources, and milestones. Client approved Phase 1 scope.", "createDateTime": "2024-02-01T10:00:00Z" } ], "total": 2}Add a note to a project
Section titled “Add a note to a project”Prompt:
“Add a note to project 5021 titled ‘Status Update’ with description ‘Phase 1 complete. Moving to Phase 2 next week.’”
What happens: The server calls autotask_create_project_note with projectId: 5021, title: "Status Update", and description: "Phase 1 complete. Moving to Phase 2 next week.".
Company Notes
Section titled “Company Notes”Search company notes
Section titled “Search company notes”Prompt:
“Show notes for company 29683451”
What happens: The server calls autotask_search_company_notes with companyId: 29683451.
Add a note to a company
Section titled “Add a note to a company”Prompt:
“Add a company note for 29683451 titled ‘Account Review’ with description ‘Quarterly review scheduled for March 15. Contract renewal discussion needed.’”
What happens: The server calls autotask_create_company_note with companyId: 29683451, title: "Account Review", and description: "Quarterly review scheduled for March 15. Contract renewal discussion needed.".
Ticket Attachments
Section titled “Ticket Attachments”Search attachments on a ticket
Section titled “Search attachments on a ticket”Prompt:
“Show me attachments on ticket 48231”
What happens: The server calls autotask_search_ticket_attachments with ticketId: 48231.
Expected output:
{ "summary": "Found 2 ticket attachments (showing 1-2)", "items": [ { "id": 60001, "attachmentType": "FILE_ATTACHMENT", "fullPath": "screenshot_error.png", "title": "Error Screenshot", "contentType": "image/png", "attachDate": "2024-01-15T09:35:00Z" }, { "id": 60002, "attachmentType": "FILE_ATTACHMENT", "fullPath": "server_logs.txt", "title": "Server Logs", "contentType": "text/plain", "attachDate": "2024-01-15T10:15:00Z" } ], "total": 2}Get a specific attachment
Section titled “Get a specific attachment”Prompt:
“Get attachment 60001 from ticket 48231”
What happens: The server calls autotask_get_ticket_attachment with ticketId: 48231 and attachmentId: 60001.
Project & Task Attachments
Section titled “Project & Task Attachments”Projects and tasks support the same binary attachment flow as tickets — upload a base64-encoded file, list metadata, and download the bytes. Useful for SOWs, drawings, as-builts, and closeout documents.
Upload a file to a project
Section titled “Upload a file to a project”Prompt:
“Attach the SOW PDF to project 152”
What happens: The server calls autotask_create_project_attachment with projectId: 152, title: "SOW.pdf", and data set to the base64-encoded file bytes. Autotask enforces a 3 MB limit, validated before upload. The task equivalent is autotask_create_task_attachment with a taskId.
List attachments on a project or task
Section titled “List attachments on a project or task”Prompt:
“Show attachments on project 152”
What happens: The server calls autotask_search_project_attachments (metadata only — name, type, size, attach date). Use autotask_search_task_attachments for a task.
Download a project or task attachment
Section titled “Download a project or task attachment”Prompt:
“Download attachment 60050 from project 152”
What happens: The server calls autotask_get_project_attachment with projectId: 152, attachmentId: 60050, and includeData: true to return the base64 file bytes (verified to belong to that project). Without includeData it returns metadata only. Oversized binaries are stripped with a dataOmittedReason since base64 payloads can exceed the MCP client’s ~1 MB tool-result limit. autotask_get_task_attachment does the same for a task.