awork

· #337 most-used

Project management that runs itself

ProductivityProjectsAnalyticsSchedulingAutomation

awork is a project management and team collaboration platform built for agencies, consultancies, and service teams — tracking tasks, time, and capacity in one place. Connect it to Actionist and your agents create tasks the moment work arrives, log time automatically, route assignments by workload, and surface blockers before they become misses.

Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents automate the inbox-to-project loop in awork — intake that used to require hand-crafting tasks, routing assignments, and chasing time logs now happens without anyone opening the awork UI.

Schedule

What your awork agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
WedFri
Wed
Thu
Fri
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

awork × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~51 hrsSaved / week
6Personas served
For customer success
Featured4 apps

Support email → awork task → Slack alert

When a client emails about a project issue, the agent reads the thread, creates a scoped awork task in the client project with full context already filled in, then posts a Slack alert to the support lead with the task link and a one-line summary. The client gets a receipt email within 90 seconds. Your team stops triaging manually and starts resolving immediately.

~15 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new email arrives in the support inbox with a client project name in the subject
Result
Create task with email content and priority tagPost task alert to #support-team channelBlock 30-minute triage slot on support lead's calendar
The win
Saved per run
45 min
Runs / week
~20×
Zero dropped client issues
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual project setup

    Sales rep hand-creates an awork project, task list, and assigns CSM after each deal closes — 18 minutes of copy-paste every time.

    Sales Agent
    0 min
    Agent kicks off delivery instantly

    Agent creates the project, populates milestone tasks, and assigns the CSM the moment the deal closes — delivery starts before the contract is countersigned.

  • Marketing
    13 min / week
    Campaign task scaffolding

    Campaign manager manually creates awork tasks for each content, design, and launch deliverable at the start of every campaign — 13 minutes per campaign.

    Marketing Agent
    0 min
    Agent scaffolds every campaign

    Agent creates and assigns all campaign tasks the moment a proposal is sent, so the team is moving before the brief is even shared.

  • Customer Support
    18 min / week
    Email-to-task triaging

    Support rep reads each client email, decides priority, manually creates a task in the right awork project, and notifies the team — 18 minutes per day on intake alone.

    Customer Support Agent
    0 min
    Agent routes every issue

    Agent creates the awork task, sets priority from email tone, and alerts the support lead in Slack — client acknowledged in under 2 minutes.

  • Human Resources
    7 min / week
    Onboarding task setup

    HR manually creates an awork task list for each new hire, adds subtasks for each onboarding step, and assigns them one by one — 7 minutes per hire.

    Human Resources Agent
    0 min
    Agent builds the onboarding plan

    Agent creates the onboarding project, adds all standard tasks, and assigns them to the right departments the moment a new hire is confirmed.

  • Finance
    13 min / week
    Weekly time entry export

    Finance team manually exports time entries from awork, reconciles billable hours per project, and formats invoice line items every Friday — 13 minutes per week.

    Finance Agent
    0 min
    Agent prepares invoices automatically

    Agent pulls billable time entries, organises them by project and client, and creates a draft invoice in HubSpot — ready to send, not ready to start building.

  • Operations
    25 min / week
    Capacity-based task assignment

    Ops manager manually checks each team member's awork task list before every assignment to avoid overloading anyone — 25 minutes of detective work each week.

    Operations Agent
    0 min
    Agent assigns by live workload

    Agent checks each person's open task count before every assignment and routes the task to whoever has capacity — balanced without a single meeting.

  • Legal
    6 min / week
    Compliance task tagging

    Legal team member manually reviews new awork tasks weekly, identifies those with regulatory implications, and applies compliance tags — 6 minutes every Monday.

    Legal Agent
    0 min
    Agent tags compliance tasks instantly

    Agent scans every new task description for regulatory keywords and applies the compliance tag immediately — legal's filtered view is always current.

+ 100s of other awork automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 person
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on awork's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug awork into Actionist

Pick the connection method that suits your environment.

The fastest path to full awork access. Install the awork MCP server in one click and your agent reaches projects, tasks, and time entries through a permissioned OAuth handshake — no API tokens to rotate, no credentials to store.

1
Open the Apps tab

Find awork in the Apps library and click Connect. MCP is selected by default.

2
Authorise in awork

You'll be redirected to awork's OAuth screen. Log in with your awork account and grant Actionist access to the workspaces you want the agent to manage.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

20 action your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 event your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with awork

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with awork

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about awork + Actionist

How does Actionist connect to my awork workspace?
Use MCP for the fastest setup — click Connect in the Apps tab, complete the awork OAuth flow, and your agent has access to your workspace's projects, tasks, and time entries within 60 seconds. If you prefer credential-based access, generate an API token in awork's Profile → Integrations → API Tokens and paste it in.
Which awork objects can the agent read and write?
Your agent can create, update, and query projects, tasks, subtasks, task lists, time entries, comments, and assignments. It can also tag tasks, set due dates, and search across the whole workspace. Workspace-level metadata is read-only. The agent cannot delete projects — only tasks and task lists, and only when explicitly instructed.
How do I avoid the agent creating duplicate tasks?
Use the 'Search tasks' action before any 'Create task' call — the agent can search by title and return any existing match. If a match is found, it updates the existing task instead of creating a new one. For trigger-based workflows, add a deduplication check: store a task ID in memory or a Google Sheet, and skip creation if that ID already exists.
Can the agent read and write time entries, and are they billable?
Yes — the agent can log time entries against any task, mark them billable or non-billable, and add a description note. When listing time entries, it returns the billable flag, duration, and the associated task and project. Use the billable filter in 'List time entries' to pull only invoiceable hours when building weekly billing summaries.
Will the agent update tasks in the right project when working across multiple clients?
The agent always scopes actions to the project you specify or resolves the project by name before writing. When creating tasks from email or Slack, instruct the agent to extract the project name from the message and call 'List projects' first to confirm the match before creating or updating. Ambiguous project names should be clarified by the agent with a disambiguation prompt rather than guessing.
Can I trigger the agent when a task status changes in awork?
Yes — awork exposes a 'Task status changed' trigger. Connect it in the Triggers tab and optionally filter to a specific target status such as 'Done' or 'Blocked'. The payload includes the task ID, old status, new status, and assignee, so the agent has full context to decide what to do next — whether that's a Slack message, a calendar block, or an update in another system.
What permissions does the OAuth connection need?
The MCP OAuth flow requests read and write access to projects, tasks, time entries, and team members in the workspaces you select during authorisation. It does not request billing details, payment information, or admin-level workspace settings. You choose which workspaces to expose at connection time — Actionist only sees what you grant.
How does the agent handle awork's rate limits?
awork's API applies rate limits per workspace, typically 100 requests per minute on standard plans. Actionist's agent queues burst operations automatically and retries with exponential backoff on 429 responses. For bulk operations — such as creating tasks for an entire sprint — the agent batches requests and pauses between batches to stay within limits. You'll see a log of retry events in the run history.