Actions and tasks
Tasks, follow-up actions from visits and trials, and dated project steps in a single to-do list.
A sales rep's to-dos come from four different kinds of records. The CRM shows them in a single list on the Actions (Aksiyonlar) page; in the API, GET /api/v1/actions returns the same list.
Kind (kind) |
Source | Example |
|---|---|---|
task |
Task — created manually, by a workflow, from a form, or by a hook. | "Send the price list" |
visit |
The next action of a visit / phone call. | "Send quote · October 5" entered during the call |
demo |
The next action of a trial (product trial). | "Get the trial result" |
step |
A dated checklist step on an opportunity. | "Schedule a line trial" |
Each row's key field has the form kind:id (e.g. task:26). The complete, postpone, and close endpoints use the path /api/v1/actions/{kind}/{rid}/…, so you can handle every action with the same code, whatever its kind.
Status
state |
Meaning |
|---|---|
overdue |
Past its due date. |
soon |
Due in 7 days or less. |
open |
Due later. |
done |
Completed. |
Chain
When you close an action, you can open the next one (Close and open next). This way, the work for a company forms a chain; the single-record endpoint returns the chain in the chain_before and chain_after fields. Logging an activity (Log an activity) automatically closes matching open actions at the same company.
Actions page
Each item is a single line: circle (complete) · title · company · project · due date · the assignee's initials. No coloured icon boxes or badges; the type icon sits before the title, and priority only shows as a small flag for High / Urgent.
- Tabs: Open · Today · Upcoming · Completed. Overdue items are grouped at the top of Open; Overdue, Call list and Assigned by me live in the ⋯ menu on the right.
- Mine / Team sits next to the title; the Filter button picks type, priority, assignee and company (the number of active filters shows on the button).
- Due date: one line — Today · Tomorrow 14:30 · 12 Oct; overdue items are red, the number of days late shows on hover.
- In Completed, items are grouped by the day they were completed (Today · Yesterday · Last 7 days · Last 30 days · Earlier) and each row shows the completion date and time; the due date and how many days late it was are in the tooltip.
- The ⋯ menu holds sorting, grouping (due date, assignee, company, project, type, priority, creator), show completed and the morning e-mail settings; the old column view is Classic view (
/tasks?klasik=1). - Clicking a row opens the task window; selection boxes and the bulk bar (complete, postpone, assign, delete) work as before. On phones the row wraps to two lines (title, then company · due date).
Task fields
| Field | Type | Description |
|---|---|---|
id, rid |
integer, string | ID and permanent record ID (00T…). |
title, detail |
string | Title and details. |
due_date, due_time |
date, string | Due date and optional time (HH:MM). Tasks with a time appear at that time in the calendar. |
status |
string | Açık (open), Devam Ediyor (in progress), Tamamlandı (done). |
priority |
string | Düşük (low), Normal, Yüksek (high), Acil (urgent). |
assignee |
user | Assigned user. |
customer_id, opp_id |
integer | Linked company and project (both optional). |
result, completed_at |
string, datetime | Result note and completion time. |
source_key |
string | The source that created the task (e.g. form:3, a workflow). |
Completion date
Completion endpoints accept a past date in done_on: when a user marks a task done today that they actually did yesterday, reports count it on the correct day. If you omit it, the current time is used.
Notifications
The assigned user gets an in-app notification and, depending on their preferences, an email as well. A digest email of overdue items goes out every morning; users choose which events trigger email or in-app notifications under Settings → Notifications (Ayarlar → Bildirimler).