Connect Claude & ChatGPT to Assignar

30 tools for Assignar

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_order_taskChanges dataAdd a task to an order: `order_id`, the `task_id` (from list_tasks) and `task_quantity` (number of resources needed); optional start/end times and dates.
• approve_leave_requestVisible to othersApprove a leave request by `leave_request_id`, with optional comments. The worker's leave becomes approved.
• create_clientChanges dataCreate a client. Requires `name` and `company_name`; optional email, phone, address and ABN.
• create_leave_requestChanges dataCreate leave requests for one or more workers: `user_ids`, `leave_type_id` and `leave_dates` (each with `start_at` and `end_at`). Optionally create them already approved.
• create_orderChanges dataCreate an order. Requires `client_id`, `order_owner` (user ID), `start_date` and `end_date` (YYYY-MM-DD); optional project, status, job number and description.
• create_projectChanges dataCreate a project with a `name`, and optionally its `client_id`, address and tags.
• decline_leave_requestVisible to othersDecline a leave request by `leave_request_id`, with optional comments.
• get_assetGet one asset by `asset_id`, with make, model, serial and registration numbers.
• get_clientGet one client by `customer_id`.
• get_orderGet one order by `order_id`, with its client, project, dates and status.
• get_projectGet one project by `project_id`, with its address, client and status.
• get_timesheetGet one timesheet with full details by `timesheets_expanded_id`.
• get_workerGet one worker or staff user by `user_id`, with contact details, employment type and tags.
• list_allocationsList allocations: which workers and assets are scheduled to which orders and shifts.
• list_assetsList assets (plant, vehicles and equipment).
• list_clientsList clients (customers). Use to find a `client_id` for projects and orders.
• list_form_resultsList submitted form results (e.g. safety checks and inspections filled in by workers).
• list_leave_requestsList worker leave requests and their status.
• list_leave_typesList leave types and their IDs, for creating leave requests.
• list_order_statusesList the possible order statuses and their IDs.
• list_order_tasksList the tasks on an order by `order_id`, i.e. what work and how many resources need scheduling.
• list_ordersList orders (jobs that need people and equipment scheduled).
• list_projectsList projects (job sites).
• list_site_diariesList site diaries, optionally for one `site_diary_date`.
• list_tasksList the task types defined in Assignar. Use to find a `task_id` for adding tasks to orders.
• list_timesheetsList timesheets with full details (worker, order, hours).
• list_workersList the users (workers and staff) in Assignar. Use to find a worker's ID.
• update_clientChanges dataUpdate a client by `customer_id`. `name` and `company_name` must be sent again with any changed fields.
• update_orderChanges dataUpdate an order by `order_id`. `client_id`, `order_owner`, `start_date` and `end_date` must be sent with any changed fields.
• update_projectChanges dataUpdate a project by `project_id`, e.g. name, address, client or active status.

Questions