Fareeqy | فريقي

Restores an archived project to active, so it can be edited again. Does not apply to demo projects, which cannot be restored once archived.

unarchive_project

Creates a calendar event (meeting) owned by the user. Attendees are invited by email and must be members of the same company; they are notified. Times are ISO 8601 and are interpreted in the company's time zone when no offset is given.

create_event

Creates several tasks in an existing task list, in one call.

create_tasks

Creates a team in the company, optionally with its members. A team on its own grants nothing: use assign_team_to_project afterwards to give every member access to a project. Team names are unique within the company; list_teams shows what already exists. The company owner cannot be put in a team: they already reach every project.

create_team

Creates a task list within a project, optionally with its initial tasks in the same call. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files. Attachments go on the LIST's notes, not on its tasks.

create_task_list

Creates a task list in a project from one of the company's ready-made templates, with all of the template's tasks, in one call. Call list_task_templates first to find the template. Prefer this over inventing a checklist with create_task_list: a template is the shape the company itself decided on. The new list takes the template's title and description unless `title` or `notes` say otherwise; its title must be unique within the project, so pass `title` when applying the same template twice. The tasks are created with no assignee and no due date, the way the template stores them - assign them afterwards with update_task.

apply_task_template

Creates a folder in a project's files section. Nest it by passing parent_folder_id, or omit that for a top-level folder. Names must be unique among siblings. Requires the upload_files permission.

create_folder

Creates a new project. The caller becomes its owner and admin member.

create_project

Creates a single task within a task list. To create several tasks, use create_tasks (or the tasks argument of create_task_list) instead of calling this repeatedly. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files.

create_task

Creates a personal task for the caller — a private to-do with no project or task list ("remind me to…"). Use this for the caller's own list; use create_task for work inside a project's task list. Returns the created task (its project_slug and task_list_slug are null). To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files.

create_personal_task

Creates a majlis topic (discussion) in a project. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files.

create_discussion

Returns the authenticated user, their company, role, the current access token scopes, and the company time zone with today's date in that zone (use these to resolve relative dates like "tomorrow").

whoami

Replies to a majlis topic (discussion). To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files.

reply_to_discussion

Finds records by name across projects, task lists, tasks, folders, files and majlis topics, within what the caller can access; Arabic spelling variants match. Use it to turn a name into the `id` (ref) every other tool takes, instead of walking the hierarchy. A kind in `truncated` had more than `per_type` matches: narrow the query or raise per_type. A kind in `widened` had no record carrying every word, so its results are only candidates: confirm with the user before acting on one.

search

Reorders the tasks inside one task list — the board order that list_tasks and get_task_list answer in. Send `task_slugs` with the list's COMPLETE new order (every task in it, exactly once, first to last) to re-sort the whole list, or `task_slug` with `position` to move one task to a 1-based place and push the rest down. Read the current order first with list_tasks (raise its `limit` when it reports truncated) or with get_task_list, which returns every task whatever the length. To move a task to a DIFFERENT list, use move_task instead.

sort_tasks

Records how long a task took. Send `time_spent` as "1:30" (hours:minutes), "1.5" (decimal HOURS) or "90" (whole minutes) — all three mean ninety minutes. Send an empty string to clear it back to unmeasured. This REPLACES the task's total rather than adding to it, so read time_spent_minutes first if you mean to accumulate. Works for personal tasks too. Requires a plan that carries time tracking.

set_time_spent

Updates a calendar event. Only the organizer can edit it. Only the fields you pass change, EXCEPT attendee_emails, which replaces the whole guest list when given — pass the full list, not just the additions. Attendees are notified of additions, removals and time changes.

update_event

Renames a team or changes its description or colour. Does not change who is in the team: use add_team_member and remove_team_member for that. Only the fields you send are changed.

update_team

Edits the text of an existing comment. Pass task_slug to reach a comment on a task; omit it for a comment on the task list itself. You can only edit your own comments unless you hold the delete_any_comment permission, and a deleted comment cannot be edited. The new content REPLACES the old text rather than being appended to it, which also drops any files that were attached to it. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files.

update_comment

Updates a task list. Only the provided fields change. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files. Attachments REPLACE the notes' existing files, so send `notes` alongside them.

update_task_list

Updates a project. Only the provided fields change.

update_project

Updates a task. Only the provided fields change. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files. Attachments REPLACE the notes' existing files, so send `notes` alongside them.

update_task

Updates a majlis topic. Only the provided fields change. To attach a file, pass `attachments` with {name, content} for text you wrote or {name, content_base64} for bytes; it is embedded in the text itself, not published to the project's files. Attachments REPLACE the body's existing files, so send `body` alongside them.

update_discussion

Marks the caller's own notifications as read. Pass notification_ids (from list_notifications) to mark specific ones, or omit it to mark ALL unread notifications as read. Nothing is deleted: they stay readable with status 'seen'. At most 100 ids per call.

mark_notification_read

Creates a file in a project's files section from content you provide. Use `content` for text you wrote (notes, specs, summaries) — a .md name renders as markdown in Fareeqy, and a .pdf name renders your markdown into a real PDF document (max 256 KB of markdown). Any other plain-text extension (.txt, .csv, .json, .yml, .sql, .rb, .py, .sh, …) stores your text verbatim. `content` is refused for a binary container format such as .docx or .xlsx, because storing text under that name produces a file no viewer can open — send genuine bytes as `content_base64` instead. Exactly one of the two is required. Max 5 MB; larger files must be uploaded through the browser. Requires the upload_files permission. The file is virus-scanned after upload and is not downloadable until the scan clears — check scan_state in the response.

create_file

Lists the company's roles with their Arabic names, whether each is a built-in role (owner/manager/team_member) or a custom one, and how many people hold it. Use it to find a valid role handle for invite_user or set_user_role. Callers who may manage roles also get each role's permission keys. The owner role grants everything and can never be assigned.

list_roles

Lists the people in the caller's company with their emails, roles and teams. Use this to find the email address that create_task/update_task (assignee_email) and create_event (attendee_emails) require, or to check whether someone is already here before inviting them. Each person carries a status: 'active' means they can be assigned work; 'pending' means they were invited and have not accepted yet, so they cannot be assigned work and re-inviting them will be refused. For who can be assigned work on a SPECIFIC project, use list_project_members. Returns at most `limit` people (default 100); check total_count and truncated.

list_people

Lists the caller's own notifications, newest first, with a link to the page each one points at. Defaults to UNSEEN only, which is the answer to "is anything waiting for me"; pass status 'all' or 'seen' for the rest. Reading them here does not mark them read, use mark_notification_read for that. Returns at most `limit` (default 30); check total_count and truncated.

list_notifications

Lists the people who can be assigned work on a project, with their emails. Use this to find the assignee_email that create_task/update_task take (attendees for create_event come from the same company roster). An email returned here is guaranteed assignable on this project.

list_project_members

Lists calendar events (meetings) the user organizes or was invited to. Defaults to upcoming events only; pass from/to to look at a specific window, or include_past to reach back. Use this to find the event_id the other event tools need. Returns at most `limit` events (default 50); check total_count and truncated.

list_events

Lists the comments on a task list, or on a task when task_slug is given. Oldest first. Returns at most `limit` comments (default 100); check total_count and truncated. To read only what is new, pass `since`: the created_at of the last comment you saw.

list_comments

Lists the company's teams with their members and the projects each team is assigned to. A team has no id: its NAME is the handle every other team tool takes. Read this before naming a team anywhere else. Assigning a team to a project grants every member of that team full access to it, so the projects listed here are what a team membership is worth. Returns at most `limit` teams (default 50); check total_count and truncated.

list_teams

Lists the ready-made task lists (templates) the company has saved, each with the tasks it contains. Read this BEFORE inventing a checklist of your own: if a template already covers what the user asked for, apply it with apply_task_template instead, so the work comes out in the shape the company decided rather than one you made up. Templates are company-wide, not per-project. Returns at most `limit` templates (default 50); check total_count and truncated.

list_task_templates

Lists the projects the caller can access. Archived projects are excluded unless requested. Each project carries `id`, its ref (prj-8f3kd): send it back as project_slug. Returns at most `limit` projects (default 100); if truncated, pass next_offset as offset.

list_projects

Lists the files and folders directly inside a project folder (or the project root if folder_id is omitted). Not recursive — pass a folder's id back as folder_id to look inside it. Use this to find the file_id and folder_id that the other file tools need. Returns at most `limit` files (default 100); check total_count and truncated.

list_files

Lists the tasks within a task list, in board order. Each task carries `id`, its ref (tsk-9wb7t): send it back as task_slug, on its own, to read or change that task. Returns at most `limit` tasks (default 100); if truncated, pass next_offset as offset.

list_tasks

Lists tasks assigned to the caller, across all projects plus their personal tasks. filter: 'in_progress' (default) = every open task; 'overdue' = past its due date; 'today' = due today in the company's timezone; 'focus' = only the tasks the caller has hand-picked into their focus list, in the order they arranged them; 'completed_this_week' = tasks the caller FINISHED since the start of the current week (weeks start Saturday, in the company's timezone), newest first, with the window's start returned as `since`. The first four return open tasks only and never a completed one, so to report progress — what was done AND what is still open — call this tool twice. Overdue and today can overlap — a task due earlier today is both, and both exclude tasks with no due date. Every task carries focus_order: its position in the focus list, or null if the caller has not put it there. Returns at most `limit` tasks (default 50); if truncated, pass next_offset as offset.

list_my_tasks

Returns a single calendar event, including its attendees. Find event ids with list_events.

get_event

Fetches a single task list by its ref (the `id` list_task_lists and search return), including its tasks and its most recent comments (oldest first, at most 100). Check comments_total and comments_truncated; when truncated, read the rest with list_comments.

get_task_list

Fetches a single project by its ref (the `id` list_projects and search return), including its task lists.

get_project