Short answer: An overview of Aamu.app Tasks for project work, assignments, dates, reminders, comments, linked context, AI-assisted follow-up, and the Tasks API.

Aamu Tasks tracks assigned work, deadlines, recurring responsibilities and follow-ups from support requests or form submissions. Tasks belong to projects and can link to Docs, Databases, Emails and Helpdesk conversations.

Projects and task lists

Tasks belong to projects. You can work inside one project, or use the combined all-projects view when you want to see work across the whole team.

The task header gives you the main controls:

  • search inside the selected project or across projects,

  • create a new task,

  • sort the current list,

  • filter by user, tag, or custom status field,

  • switch between task views, and

  • move between active, overdue, running, completed, and archived work.

Task views

Aamu has multiple ways to look at the same tasks.

  • List is the dense view for scanning, sorting, filtering, and batch work.

  • Taskboard is the kanban-style view for moving work visually.

  • Calendar shows scheduled tasks and events by time.

The same task can appear in different views depending on how you work. A task with a due date is still the same task when you see it in the list, board, or calendar.

Sorting and filtering

The list view can be sorted by useful operational signals such as updated time, created time, starting date, due date, star count, comment count, completed time, and total time used.

Filtering is where project structure becomes useful. You can filter by assignee, tags, and project custom status fields. For example, a project can have a custom status field for "Stage" or "Priority", and that field can be used to filter the task list.

Search also supports structured queries such as assignee and status-style filters, so larger task lists do not need to become messy.

What a task contains

A task can contain much more than a title. A typical Aamu task can have:

  • a rich-text description,

  • comments,

  • assignees,

  • tags,

  • files and attachments,

  • todos inside the task,

  • start and due dates,

  • reminders,

  • repetition,

  • custom fields, and

  • internal links to other Aamu content.

Task relationships

Connect tasks with Blocked by, Blocking and Duplicate relationships. Aamu maintains the inverse relationship so both tasks show the connection.

Dates, events, and recurring work

A task can be a simple due-date item, or it can behave more like an event with both a start and an end date. Aamu shows due tasks, upcoming events, overdue tasks, and running work separately so time-sensitive work is easier to notice.

Tasks can also repeat daily, weekly, monthly, or yearly. This is useful for recurring operational responsibilities: weekly reporting, monthly checks, renewal reviews, bookkeeping reminders, and regular customer follow-ups.

When a task has a due date, Aamu can also produce an iCalendar file for it. Projects can additionally be connected to Google Calendar in project settings.

Custom task fields

Project custom fields make Tasks adapt to the way a team works. Current custom field types include:

  • Text,

  • Long Text,

  • Number,

  • Status,

  • Time & Date,

  • User, and

  • Location.

Status fields are especially useful because they can become filters and lightweight process stages. For example, a project can track work by "New", "Waiting", "In progress", and "Done", or by a custom sales/support/production stage.

Custom fields can also be shown in task cards, which makes the list and board views easier to scan.

Bulk actions

When you select multiple tasks, Aamu can handle common batch operations. You can assign users, set due dates, close or reopen tasks, and archive or unarchive tasks depending on the current view.

Tasks connected to Forms and Databases

Tasks connect naturally to Aamu Forms and Databases. A form submission can create a database row, and a database automation can create a task from that row.

For example:

  • a contact form can create a sales follow-up task,

  • a bug report form can create a triage task,

  • a survey response can create a review task, and

  • an onboarding request can create an implementation task.

The database keeps the structured response data. The task carries the work forward.

Tasks connected to Helpdesk and Emails

Support and email work often turns into tasks. A customer asks for something, a support ticket reveals follow-up work, or an email thread needs a concrete next step. In Aamu, those actions can stay inside the same workspace instead of being copied into a separate task tool.

Tasks and AI

Aamu AI can draft a task title and description from a conversation, Doc, email or support ticket.

As with the rest of Aamu, the safer pattern is to use AI to prepare work and let a person decide what should be saved, assigned, or acted on.

Tasks API

Aamu exposes Tasks through the Team API for integrations, agents, and external workflows. The core endpoints are:

GET   /api/v1/tasks/
POST  /api/v1/tasks/
GET   /api/v1/tasks/TASK_ID
PATCH /api/v1/tasks/TASK_ID
POST  /api/v1/tasks/TASK_ID/comments
GET   /api/v1/users/
GET   /api/v1/users/USER_ID_OR_USERNAME

Send the Team API key in x-api-key and the project in x-project-id. Write calls can set x-aamu-actor to a project member username or user id. Use the Users API to resolve stable user ids before assigning tasks.

Create and update requests support title, HTML, status, assignees, dates, repetition, reminders, tags, priority, custom fields and todo checklists. Read project statuses and field definitions at GET /api/v1/tasks/metadata. Separate endpoints manage blocking and duplicate relationships and paginated comments. Task mutations support Idempotency-Key for retries and If-Match for conditional updates.

POST /api/v1/tasks/
x-api-key: YOUR_API_KEY
x-project-id: YOUR_PROJECT_ID
x-aamu-actor: ai
Content-Type: application/json

{
  "title": "Review onboarding request",
  "html": "<p>Check the submitted details and choose the next step.</p>",
  "users": ["USER_ID"],
  "end_at": "2026-06-19T12:00:00.000Z",
  "reminders": [{ "minutes_before": 30 }]
}

Use Tasks read permission for listing and fetching, write permission for creation and updates, and comment permission for comments. Tasks can also be created by database automations when a form or GraphQL mutation inserts or updates a matching row.

Related articles